VR crashing issues
I've been experiencing issues in VR where both the timing and the type of crash vary from day to day. The most common crash occurs mid-race: the game freezes for a couple of frames, and my Moza R12 suddenly increases the force feedback (FFB) in the direction I'm steering. Sometimes it recovers for approximately 10 seconds before repeating the cycle; then, the entire system hangs and goes to a gray screen with no error codes. The other type of crash happens at the end of a race. When I hit the 'advance' option to go back to the home page in Driver Career mode, the system freezes completely, forcing me to do a hard restart. steps I've taken to resolve the issues include: restarting the whole system closing out of steam vr and restarting application closing out of pimax play and restarting steam vr changing open xr implementation between pimax xr and steam xr verifying game files through steam setting my system settings to defaults in bios turning off amd upscaling and antilag features changing vr headset to meta quest 3 through virtual desktop (still the same issues) reducing in game visual settings as well as in pimax play and steam vr to lowest settings System Hardware 9800x3d rx 7900xtx 2tb nvme ssd pimax crystal super UW Meta quest 3 Moza r12 Moza GSV2P steering wheel Srp Lite pedals Any help would be appreciated
F1 RPM LEDs BUG
Why do the RPM LEDs in player-controlled cars light up differently than in the original cars? In F1, F1 World, and Konnerspor cars, the RPM LEDs start from the beginning (green, red, purple). The original cars don't have these green RPM LEDs. They start with red. Instead of the green RPM LEDs, there is (should be) information about the DRS zone and activity. Fix this so that the player's car has the same RPM LEDs as the original car. This only applies to F1 cars, as F2 is fine. Green RPM LEDs can be used there.
MOZA FSR V2 Wheel MyTeam Telemetry Glitch
In my MyTeam career mode, I have ancountered a glitch with my MOZA FSR V2 Dash display regarding the Telemetry sent from the game to the wheel. The telemetry being sent to my MOZA wheel is not from my car but rather from the AI car of Lando Norris. This is extremely off-putting as I am getting given information relevant to Lando Norris' AI rather than myself such as laptimes, gear, brake bias etc. This glitch only occurs in MyTeam mode. All other modes my dash is displaying the correct information. I am wondering if it is to do with the fact there is now 24 cars and not 22 with the 2026 Season DLC. I am not sure if this is a game issue or a MOZA issue. Report Code: BXBB-XKZR-BJHX-XSB EDIT: I have attached a video so you can clearly see I am spectating Lando Norris and getting his telemetry through my wheel.
UNREALISTIC CAR PERFORMANCES.
Ok so I know the DLC has only been out for a week and you are planning a future updates. But the car performances in the new 2026 DLC are so unrealistic particularly from the Aston Martin who are getting into Q3, as well as Williams who in real life have an overweight car so they should not be challenging for podiums. And also most of all Mercedes who have dominated the season since the start as well as Antonelli who has gone on an insane 5 win streak surely this is not a fluke. Just wanted to get the word out as quickly as possible
Online Lobby Sprint Full Race Qualifier Starting Position not in the Race
Hello EA/Codemasters Support Team, I would like to report a bug in F1 25 regarding online lobbies during Sprint weekends. Platform: [PC / PlayStation / Xbox] Game mode: Online Lobby / Multiplayer Weekend format: Sprint Weekend Bug description: In online lobbies during a Sprint weekend, the qualifying results are correctly used as the starting grid for the Sprint race. However, after the Sprint race is finished, the Sprint race result is then incorrectly used as the starting grid for the main Grand Prix. This happens even though a normal qualifying session for the main race has been completed. We have tested this multiple times in our league racing environment, and the issue occurred repeatedly. Expected behaviour: The starting grid for the main Grand Prix should be based on the results of the Grand Prix qualifying session. Actual behaviour: The game uses the Sprint race finishing order as the starting grid for the main Grand Prix, ignoring the qualifying results for the main race. Steps to reproduce: Create or join an online lobby. Select a Sprint weekend format. Complete the qualifying session for the Sprint race. Complete the Sprint race. Complete the qualifying session for the main Grand Prix. Start the main Grand Prix. The starting grid is based on the Sprint race results instead of the Grand Prix qualifying results. This can cause unfair starting positions in online races, especially in league racing, because the qualifying session for the main race does not seem to affect the grid correctly. Thank you for looking into this issue. Best regards, RomitHH
F1 25 crashes after EA Javelin AntiCheat - black screen on launch, then crash
Hello, I am creating this report because I have found several users experiencing the exact same issue and EA Support informed me that similar cases are currently being reported. Problem: F1 25 worked perfectly for approximately 55 hours of gameplay. Around 1-2 weeks ago the game suddenly stopped launching. When I press Play: EA Javelin AntiCheat starts normally. The splash screen appears. A black screen is shown for 1-2 seconds. The game closes instantly without any error message. System: - Windows 11 Pro 24H2 - Intel i7-14700K - NVIDIA RTX 5070 - Steam version of F1 25 What I have already tried: - Reinstalled F1 25 - Reinstalled EA App - Reinstalled EA Javelin AntiCheat - Verified game files through Steam - Updated Windows - Updated GPU drivers - Tested with peripherals disconnected - Disabled Intel integrated graphics - Ran system integrity checks Nothing changes the behaviour. Event Viewer has shown different modules during testing, including Intel graphics related modules and Logitech TrueForce SDK modules, which suggests the crash may occur during initialization rather than being caused by a specific device. Important: The game previously worked correctly on the same hardware and software configuration. No major hardware changes were made before the issue started. I would like to know: - Is EA aware of this issue? - Is there an active investigation? - Can affected users provide additional information to help identify the cause? If other users are experiencing the same behaviour (EA Javelin AntiCheat -> black screen -> instant crash without error), please comment below with your system specifications. Thank you.Driver ratings all wrong in 2025 MyTeam after season update
Kimi is back to 72, Ollie back to 74 etc. All ratings changed back to what they were at launch post update, meaning the field is heavily imbalanced at this point. Applies to all new saves, and applies to both PC and PS5. Would love a fix, as this completely breaks the immersion.
Possible memory leak
My PC SPECS: RTX 4060TI (8GB of VRAM) RYZEN 5 5600 ASUS TUF GAMING B550M PLUS WIFI II 32GB DDR4 3600MHZ RAM 2TB SSD 1080p165hz monitor running at 1080p 120hz GAME VIDEO SETTINGS- Ultra Low preset, with 16x anisotropic filtering, with TAA and FidelityFX Sharpening. No DLSS or Frame Generation Explanation: I say it's a possible memory leak, but in reality I have no clue why this happens. My issue is, sometimes, when I finish a race and the podium sequence starts, my game drops to 1FPS. I have tried leaving it like that for a minute, to see if it would eventually go back to normal. But no. So I pressed ALT+F4, and closed the game. After a solid 30 seconds of the game closing, I was back in my desktop. The mouse was moving like normal, but the rest of the PC was stuck on 1 FPS. I'd press something, and it would only happen a second after I press it. Everything was lagging. After pressing shutdown, even the spinning wheel that says "Shutting down" was stuck on 1 FPS. This behaviour only happens in F1 25. I have played EA FC for hours straight, I've played LMU, I've played GTA 5, etc. this behaviour only happens in the F1 25 game, and it started specifically after the 2026 season pack update. This has happened more than once. Actually, it happens multiple times in a day, it's random. It doesn't happen every race, but it happens every day.
Braking pressure doesn't match brake input
This doesn't matter which mode I'm in, multiplayer, time trial, career, you name it. I hit the brakes and need to apply significant pressure in order to get any input reading. I hop onto other games and there is no issue, applies the same way as it always has. The weirdest part is that when I go into calibration it will read that I'm hitting the brake, however it registers "0" until I apply significant pressure like in the game. So, it is registering my input, but still doesn't apply brake pressure until roughly 30% force is applied. I'm using simjack UT's and they have worked for every F1 game I have played until F1 25. And it clearly works fine as it sees I'm hitting the brake, but it will not apply the brake input until roughly that 30% force is applied. Please help!
