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.