Crash to Desktop - SteamVR/Oculus2
System Specs: CPU: AMD Ryzen 7 5800x3D GPU: RX 6590XT (XFX Merc 319) RAM: 32GB DDR4 3200MHZ MOBO: ROG Strix B450-F Gaming Headset: Oculus Quest 2, using cabled Meta Quest Link. Game .exe version: 1.0.125.9504 Game crashes to desktop with no error when trying to load into any F1 World event/race in VR. I have been able to load into 1 or 2 races, but normally it always, consistently crashes during the loading screen. Game crashes with no error message, no logs that I can see, no errors in Event Viewer. Some offline features work perfectly in VR, I completed braking point with zero issues. Non-VR gameplay seems to work with no issues. I am launching the game through SteamVR, using SteamVR runtimes, with lowest graphics settings. I have no undervolt of overclock on any components. I have tried: -Updating to latest BIOS.-Used latest AMD Drivers, and clean install of 24.6.1, and other versions. -Launching the game in DX11. -Disabling all overlays. -Disabling all AMD Adrenalin features (Chill, Anti-lag, Boost etc). -Resetting SteamVR as default runtime. -Setting all graphic settings to minimum. -Deleting hardware_settings_config.xml between attempts to load an event. -Setting the game .exe to high performance. -Uninstalling/Disabling iCUE, JoyToKey, AutoHotKey -Reinstalling and updating all Meta Quest services. -Moved game files to NVME/SSD. -Reinstalled Game, verified file integrity. -Reinstalled DX12/11. Any support here or troubleshooting I can do? I've seen this reported a lot in the community, are the team aware of any issues with VR support? Let me know if you need any further information to clarify the issue.
VR Wobble / jitter when in Car
This issue has persisted since 23 /24 and makes the game unplayable. When in game, there is a head tracking problem which gives the feeling of "wobbling", and it seems to be that the tracking is delayed or out of sync, causing stutter when moving your head. This causes instant sickness and makes it unplayable. I'm yet to find a post in the community with a fix and it seems to be a very common issue. My specs: 5700x3d 32GB Ram Nvidia 5070TI Quest 3 via SteamVR (Link cable and virtual desktop) running at 90hz Tried a wide range of settings, including dropping everything to the minimum. No avail.VR Crashing with SteamVR
Ok so my game crashes in VR mode as the title says. It's usually when I'm going from a big screen view to actual VR mode. Also sometimes on startup it will crash as well. What usually happens is that the game will freeze and SteamVR will have a critical error and ask to restart or quit, after a few seconds it closes the game. Usually right before the crash there is a loading SteamVR icon at the bottom right corner of the screen before it crashes. PC Specs: Ryzen 7 5700X, RTX 4060, 32GB RAM, Standard link cable, medium graphics settings I know that I am not the only one with this issue as I have seen people on other platforms (Reddit) with this exact issue. I also have F1 22 and when i tired using that in VR mode it does the exact same thing as F1 25. What I tried: Different GPU drivers Different Games (F1 22) Reinstall Meta, Steam, SteamVR and F1 25 I also noted that my usage is only around 75-80% (GPU). Please help as this error makes it demotivating to race longer races or to even play the game at all (don't have a monitor for my sim rig yet so stuck with VR). If you know a fix please leave a comment because this is becoming very annoying.Wheel not able to access Session info
Bug Title: Time Trial Garage – Session Info Not Accessible via Wheel Input Platform: PC (Windows 11) Thrustmaster T300 F1 Advanced Wheel Game Version: [e.g. v1.8 / Season 2 Patch] Issue: In Time Trial mode, session info in the garage is only accessible using keyboard input. - Wheel input (Button 4 or others) does not trigger or retain session info. - Switching to keyboard allows session info to open (e.g. using F1), but it collapses when wheel input resumes. - Session info action is not remappable in control settings. - Editing actionmaps XML to assign a wheel button to session info has no effect. Steps to Reproduce: 1. Enter Time Trial and stay in the garage. 2. Try to open session info using wheel buttons — nothing happens. 3. Press F1 on keyboard — session info opens. 4. Touch wheel input — session info collapses. Workaround: AutoHotkey script to convert wheel button to F1 keystroke works — confirming the game only listens to keyboard events for this menu. Suggested Fix: - Add “Session Info” as a remappable control action. - Allow wheel input to retain garage menu context instead of locking it to drive-only mode.
Game Crash Randomly while using VR Steam/EA
My Game keeps crashing. This could be in Menu, Loadingscreen, Pit or while driving. The Game just freeze for few seconds, after that it's crashing without any error. This happens mostly at the first round on track. 1-2 times i could drive 4-5 Rounds No Overheating or max usage somewhere else. VR Runs with HP Reverb G2 on 100% resolution smoothly like never else (90fps constantly) I tried without Vr as Well, maybe i was "lucky" but i did not run into a crash after ~20 Minutes of playing. Launcher: Ea and Steam Launcher Hardware: 9900x RTX 5080 Astral 32GB RAM 850W Powersupply (No OC until "XMP" Profile selected in Bios) What i did: - Update any Driver (GPU, Mainboard) Bios MB, Bios GPU, VC++, Windows 10 incl. optional - Reinstall: SteamVr (with deleting the Files in Appdata), Windows Mixed Reality, WMR for Steam, VR Headset (manually uninstalled drivers) - lower steamvr resolution to 70% - Lower ingame Resolution and turned off any "special" Settings - Run with VSync (normally without) - Run in Fullscreen / Windows Mode - Start everything as Administrator - Start with Compatiblity mode (win 7 and 8) - Used different Ports for VR Headset, replugged every cable. - probably alot more i dont remeber right now. What i gonna try: - DDU for uninstall GPU driver + reinstall (already did after changing GPU from 3080 ti to 5080 - deactivate Steam VR Home - Gonna try F1 23 as well, i did not play it for a while. If a NVIDIA driver or something else causing the Issue, i could have some Problems in other Games as well. I dont think so, because i played other VR Games without problems (1-2 Weeks ago) - Maybe i gonna try again in non-VR Mode for a longer duration. Optional Information: I do have an old Oculus Rift (with sensors) as well. Depending of what happens after "what i gonna try", i will try this headset as well. -> this would be only for sharing more information for fixing the problem. Thanks in advance.
[Improvement - Not a bug] Rain drops in VR
Rain drops in VR are ... ugly. Big drops at 15 cm of your face. Who has a helmet with a visor at 15 cm of his face ???? I can't play with this, it ruins completely the immersion. Yes, you can disable them in graphics settings by disabling particles but you lose all other particles too (like water spray effect from tires, etc...) Please Codemasters, fix this in a later patch. Thank you !
jittering in VR after Pach 1.06
Hello, since patch 1.06 (with a fix for VR) the game is totally unplayable. Stutters 100% of the races. My hardware: PIMAX CRYSTAL LIGHT on 0.67 in render quality. Steam VR on 80%. All graphics on low. With an RTX 4080 rog strix OC. Everything was perfect except for a little stuttering in the pits. But worth it. After patch 1.06 just unplayable. You should have the option to be able to go back to a previous patch. That would avoid you getting yelled at.I was waiting for my vacation to play. I'll have to wait for a patch again, perhaps with some fixes.Thank you for doing your best for the players.Pimax Crystal (OG): Graphical anomalies at HMD FULL resolution
When the HMD is set to use High resolution within Pimax Play, running under steam VR, the game will eventually, and most often during loading screens shows graphical artifacts (distortions, blurring etc) and given enough time fail to run entirely, forcing me to crash out. However if I change the resolution on the HMD in Pimax Play to 'Medium' it does run successfully, with no additional changes to the game itself. I've tried running the game in 'windowed' mode and 'full screen', with full screen being worse (as in the issue occurs sooner). Rig Info: HMD: OG Pimax Crystal CPU: Intel Core Ultra 9 285K GPU: 5080 OC RAM: 64GB