Jump to content

ts437

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

4 New Car Smell
  1. @BarryBL Do i need to submit a new bug report for each version? I don't know if this is on your radar at all.
  2. Still no fix or acknowledgement of this issue, now on v1.06
  3. Note this is still an issue on Stadia v1.05
  4. Can we get any acknowledgement from Codemasters on this issue please - would like to know that it's on your radar.
  5. So I just tested now, and the leaderboards were there very briefly (after i did a lap of Bahrain). But then they disappeared again just as fast! See the clip attached. F1®_2020_(1).mp4
  6. They're more likely to acknowledge and fix your issue if you make your own post with a bug report. This one is specifically for the Stadia leaderboards issue.
  7. Am guessing you're not on the stadia version as you mention installing the game - recommend you file a separate bug for your platform
  8. Forgot to mention, not only are the leaderboards blank but if you complete a lap, the time will not be added to the leaderboard.
  9. 1. A detailed description of the issue. Please include any error codes here. Leaderboards appear blank on stadia for time trial, every circuit ( they were full yesterday!) 2. What version of the game you are using (Shown on the start screen in the bottom left corner of the screen) 1.03 3. Game-mode? Time trial 4. What are your replication numbers? Minimum test attempts are 4. Please also add EXACT replication steps for us to try too. Tried 5 times today. Simply open team time trial, select any car, select any track, hit Y for leaderboards and it will be blank. 5. What troubleshooting have you attempted? Please always try to attempt to fix the issue No troubleshooting, not possible 6. What peripherals are you are using (gamepad, wheel make & model etc) Stadia controller, on both chrome tab and chromecast 7. Any screenshots or video of the issue? If the video is long, please include a timestamp for when the issue appears.
  10. I'm getting the identical error to everyone else here, just tested now at 18:01 GMT 8th July (after the maintainance has finished)
×