⚠ Before reporting a bug, please always check to see if your bug has already been reported.
You can use the keyword search for this to possibly find your bug. Then, add your report to the post created for it and click the "Like" button to indicate that you are experiencing the same issues.
We've also got a list of Community-Raised Issues, which doesn't include every bug we are tracking, but at least gives you an overview of what's already being investigated or awaiting a patch.
We thank you in advance for your help and reports about problems that you face in F1® 25!
What doesn't belong in the bug forum?
Please use the General Discussion board to discuss account problems, changes to e-mails, passwords, security settings, etc.
Bug Statuses: What are they? What do they mean?
The new EA Forums platform allows us to categorise all the Bugs that you report. Below, you can find an image with the mean statuses (these statuses aren't the only ones, but the ones we will use the most):
- New: This is the status by default. When a bug report is created, it will be marked as NEW.
- Investigating: Once we escalate your bug to the team for investigation, we will change your bug status to INVESTIGATING.
- Fixed: This status will only appear when a bug is FIXED.
- Not a bug: Sometimes, players report things that are not bugs, such as account issues or features that work as intended. If that is the situation, your thread will be marked as NOT A BUG.
- Needs Info: We may contact you directly to get more details on the experience. If that is the case, we will mark the Discussion as NEEDS INFO.
It's critical to be as specific as possible when submitting a bug report.
We're looking for the following details:
- Fill in all requested fields in the new thread report form
- Please include the Report Code (you can get it from the Pause menu, bottom left of the screen; it looks like ABCD-EFGH-IJKL-MNOP). Codes are always letters, so if you think something is a "2," it might be a "Z," or if you think it might be a "0," then it will be an "O."
- If you are on a PC, the DxDiag and hardware settings XMLs for the machine are helpful, particularly when you experience crashes. A Dxdiag will give you a picture of your machine setup with respect to installed drivers, the number of monitors, and other features that might indicate what is causing the issue.
- You can save out DxDiag as a text file from the dxdiag.exe that you can launch via WinKey+R
- You can also attach your Hardware Settings.:
- user > documents > my games > F1 25 > hardwaresettings
- right-click the game in Steam > Manage > Browse local files > F1_25.exe.[number].running (please, rename this last file as .txt to be able to upload it)
- Let us know if you tried restarting your console/PC to fix it (or other technical troubleshooting steps you may have tried)
- If you have made any changes to the defaults on your operating system or hardware (e.g. overclocking, changes to game-affecting things like shader caching, tuning of graphics drivers...), please let us know to help understand any reports.
- It can also help us if you can upload a screenshot or video clip of your issue.
- These can often give us a quick insight into what is happening or has happened in your game to better understand and reproduce the reported bug.
- Consider that we have some restrictions on clip creation on the EA Forums. If we ask you to make a video, we will give you further guidance on how to include it in your Bug report, but YouTube links would be recommended.
Thanks, everyone, for reading this guide and helping us to make F1® 25 a better experience for everyone!
-Groguet
Community Manager