Force feedback disabled or violently throwing the wheel on new update
Everything was completely fine yesterday, but today on v1.25 at random times (seemingly after retrying/resetting a session or a session change) the force feedback breaks and starts violently throwing the wheel from one side to another. Turning the wheelbase off and on sometimes fixes it or just disables the force feedback. The wheelbase is a Fanatec CSL DD. No similar problems on any other game.F1 25 – 2026 Season Update Crashes When Accessing Car Setup Menu
Platform: PC Launcher: EA App Hardware: Intel i9-14900K, NVIDIA RTX 4080 ROG STRIX, 32GB DDR5 RAM. I'm experiencing a consistent crash in the F1 25 – 2026 Season Update. Whenever I try to access the Save/Load Car Setup menu with the 2026 cars, the game freezes for approximately 3 seconds and then closes completely, without displaying any error message. This happens whether I try to load a previously saved setup or save a new one. The game crashes before the saved setups are even displayed. Interestingly, this issue does NOT happen with the 2025 cars. I can access, save, and load setups normally when playing with the original F1 25 content. Troubleshooting steps I've already tried: Uninstalled and reinstalled the game. Repaired the game through the EA App. Updated my NVIDIA graphics drivers. Unfortunately, none of these steps solved the problem. Since the issue only occurs with the 2026 Season Update cars, I suspect there may be a bug related to the 2026 content or its setup management system. Is anyone else experiencing this issue? Has EA acknowledged this problem or provided a workaround? Thank you!Random FFB loss and sudden force spikes to left and right
Bug Description: While playing F1 25 on PC, my Logitech G920 wheel randomly experiences severe Force Feedback issues. Out of nowhere, the wheel suddenly applies strong force pushing hard to either the left or right side on its own. These spontaneous force spikes last for about 2 seconds before returning to normal. Additionally, I occasionally experience brief, complete losses of Force Feedback during gameplay. Troubleshooting / Isolation Tests Performed: - Repaired Game Files: Verified game files via Steam to rule out corrupted game installation files. - Tested on Xbox Series S (F1 23): Works perfectly with no FFB drops or sudden force spikes. - Tested on PC (Assetto Corsa): Works completely fine with normal FFB behavior. This issue is isolated specifically to F1 25 on PC and is not caused by faulty hardware or corrupted base game files. I have attached a video clip demonstrating this issue. In the clip, the unexpected steering input causes the car to turn sharply off-track involuntarily. Report Code: TGVS-SPHP-BVGL-JTCDF1 25 VR: no input after using the Steam menu
Product: F1 25 (2026 Season Pack) Platform: PC (Steam, app 3059520) Date/time: November 16, 2026, ~1:25 PM CET Gamertag/ID: Steam - display name: benhemvergeten Which area is the bug in: VR mode, any game mode (menus and on track) Summary: Whenever I open the Steam menu on my Steam Frame headset while playing F1 25 in VR and then close it again (even just to press "Resume Game"), the game stops responding to my wheel and keyboard completely. Rendering and head tracking keep working, but every input is ignored, in menus as well as on track. The only fix is quitting and restarting the game, which throws away the current race/quali/career session. This is 100% reproducible for me. A detailed investigation of this same bug (steps, event capture, logs) was already posted by another player here: https://forums.ea.com/discussions/f1-25-general-discussion-en/pcvr-steam-frame-all-input-lost-after-opening-steam-menu-restart-needed/13830384 My report confirms it also happens on different hardware, so it is not wheel-specific. My setup: PC: Windows 11, AMD Ryzen 7 9850X3D, NVIDIA RTX 5070 Ti 16 GB, 32 GB DDR5 All drivers fully up to date (NVIDIA, chipset, Windows 11, SteamVR) as of November 2026 Headset: Valve Steam Frame, streamed wirelessly through the Valve 6 GHz adapter F1 25: latest build, fully patched, VR mode (-vr), OpenVR Inputs: Thrustmaster T150 wheel and keyboard The original reporter hits the same bug with a MOZA R5 wheel Steps to reproduce: 1. Start F1 25 in VR on a Steam Frame and confirm wheel/keyboard work. 2. Press the Steam button on the Steam Frame to open the Steam menu. 3. Select "Resume Game" (or close the menu any other way). What happens: The game keeps rendering and head tracking still works, but from that moment it ignores all wheel and keyboard input. A full game restart is required, losing the current session. Alt+Tab, clicking the game window, re-opening the menu, or headset standby do NOT restore input. What I expect: Input should work again as soon as the menu closes. Technical cause (from the event capture in the linked thread): While the Steam menu is open, the Steam Frame's SteamVR driver sets Prop_DriverRequestsApplicationPause_Bool (plus DriverRequestsReducedRendering). When the menu closes, the events arrive within the same millisecond, in this order: 1. VREvent_DashboardDeactivated 2. VREvent_PropertyChanged Prop_DriverRequestsApplicationPause_Bool (~26 microseconds later, now false) The game apparently handles VREvent_DashboardDeactivated, checks IVRSystem::ShouldApplicationPause() (or that property) at that moment, still sees "paused" (the flag clears a few microseconds later), disables input, and then never re-checks when the flag clears. That is why input stays dead forever. Workaround (proves the game can recover): Sending one extra VREvent_DashboardDeactivated about 1 second after the menu closes, with SteamVR's own tool, immediately restores input, every time: "C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrcmd.exe" --send-vrevent 503 Sending it while the game is not stuck does no harm. This shows the game's input system is fully intact; it just never re-checks the pause state on its own. Request to EA / Codemasters: Please make the game recover when the driver pause request clears, instead of checking it once at dashboard deactivation and latching the "paused" state forever. For example: re-check IVRSystem::ShouldApplicationPause() on VREvent_PropertyChanged for that property (or poll it for a short window after the dashboard closes) and re-enable input when it returns false.Game crashing to desktop with no error URGENT!
For the last 2 months in league racing we are dealing with the same issue - game crashing to desktop randomly during the race. This is happening mostly at the start of the race but for some it is happening also during the race. It is ruining everything and game is mostly unplayable because of it.BUG using [Custom Car Setup]
When playing F2 Career and changing the car's setup in any way BEFORE qualifying (manually in the car setup menu, by loading a setting, or on the track, for example, by adjusting the brake balance), we have MUCH more fuel in qualifying. If we skip practice or don't change the settings in practice, we have less fuel. In Monaco, we can have fuel for 15.8 laps (when changing the settings) or 6.9 laps (when not changing the settings, i.e., when using one of the 5 preset settings). For comparison, the AI has a fuel level of 3.5 laps. At different tracks, the fuel level in our car varies, but the AI always has the same 3.5 laps. This problem ONLY affects F2 QUALIFYING! (because in F1 we can adjust the fuel level). I noticed the same thing in F1 24! F1 23 also has this problem, but the difference is SMALLER when we change the settings in practice. To achieve better lap times, we need to change the car's settings, and if we do, we're penalized in qualifying (with a heavier car)! Similarly, if we try different settings in practice (or load them), we're penalized with a heavy car in qualifying! This makes the game difficult, especially in Monaco, where it's difficult to make up ground from the back of the grid. This requires a quick fix! Besides, the AI's fuel levels and ours should be equal in qualifying! Fix this in F1 25 and F1 24.[PC][VR] Steam Frame: all input lost after opening Steam menu, restart needed
Every time I open the Steam menu on my Steam Frame while playing F1 25 in VR (even just to press "Resume Game"), the game stops responding to my wheel and keyboard completely. The only way to get them back is to quit and restart the game, which means the current game is lost: whatever race, qualifying or career session I was in is gone. This is very frustrating, because one accidental button press is enough to throw away the whole session. Below are the details for the dev team: steps to reproduce, what I found, and a suggested fix. I investigated this with the help of Claude, which captured the SteamVR events, found the cause and built the workaround described below. SETUP Platform: PC, Steam (app 3059520, build 25251167, F1_25.exe 1.0.141.7865) Mode: VR (-vr), OpenVR (openvr_api.dll 2.7.1) Headset: Valve Steam Frame (SteamOS 0.4.5), streamed wirelessly through the Valve 6 GHz adapter SteamVR 2.18.4 beta (Steam build 25998080) Windows 11 Pro (build 26200), RTX 4070 Ti, NVIDIA driver 617.14 Inputs: MOZA R5 wheel base and keyboard STEPS TO REPRODUCE (happens every time) Start F1 25 in VR on a Steam Frame. Check that the wheel and keyboard work (in a menu or on track). Press the Steam button on the Frame (or a controller button that opens the Steam menu). The Steam menu opens. Select "Resume Game". Actual result: the game keeps rendering and head tracking still works, but from then on it ignores all keyboard and wheel input, both in menus and on track. Only restarting the game brings input back. Expected result: input works again as soon as the menu closes. These do NOT bring input back: Alt+Tab or clicking the game window Opening and closing the menu again Taking the headset off until it goes to standby Opening and closing the SteamVR dashboard from the PC (vrcmd --showdashboard / --hidedashboard) Restarting the Steam overlay process WHAT WE FOUND While its menu is open, the Steam Frame's SteamVR driver sets Prop_DriverRequestsApplicationPause_Bool (plus DriverRequestsReducedRendering), and it clears them when the menu closes. A capture with "vrcmd --showevents" shows the close events arriving in this order, within the same millisecond: VREvent_DashboardDeactivated VREvent_PropertyChanged Prop_DriverRequestsApplicationPause_Bool (~26 microseconds later, now false) So when F1 25 handles DashboardDeactivated, the driver's pause request is still set. Our best guess is that the game checks IVRSystem::ShouldApplicationPause() (or that property) at that moment, sees "still paused", keeps input disabled, and never checks again when the flag clears a few microseconds later. Other headsets probably don't set this driver flag, which would explain why this only happens on the Steam Frame. Confirmation: sending one extra VREvent_DashboardDeactivated about 1 second after the menu closes, using SteamVR's own tool ("vrcmd.exe --send-vrevent 503"), brings input back immediately, every time we tried. Sending it while the game is not stuck does no harm. WORKAROUND (for other players hitting this) After the Frame menu closes, run this once (with F1 25 focused afterwards): "C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrcmd.exe" --send-vrevent 503 I use a small script that does this automatically about 1 second after every Frame menu close. I can share the SteamVR logs (vrserver.txt, vrclient_vrcompositor.txt, vrclient_F1_25.txt) and the event capture if that helps. Thanks!