of interest perhaps is that a complete reinstall of the game itself DID fix why the game didnt appear to be any better graphically than it was before the pbr update. (or maybe because I just reset all graphics to ultra after reinstall?) Anyway regular DX9 looks great, dxvk looks worse and no offers no perfomance increase with both of them set to ultra fwiw.. even recording all three screens with OBStudio the GPU never went over 45% in DX9 so pretty sure once solved this system should be able to play VR on ultra settings as well. For reference it runs at ~25% GPU when not recording. Pretty happy with how it looks in DX9 on triples now though so for me thats enough till you guys drag it forward into DX12.
Vulcan performance was much better around September on my PC, but then after some major update it’s not really usable for me anymore, because for some reason there are no shadows , like literally none. Also performance is not better than DX9 either. On the other hand I think the same update improved DX9 graphics quality( at cost of GPU utilization/, but I’ll gladly take that). I’m waiting for DX12 as they promised it should allow decent support for other VR headsets than Oculus/Meta . My Varjo Aero doesn’t work neither in SteamVR nor OpenComposite.
In process lasso I have found that the vrcompositor.exe was running in real time GPU priority, after I have set it to normal the microstutters went away. (in both of my systems the same)
Windows updates, NVIDIA and even more saccades. 5 painful months. Is there a solution from the dev considered for the future? To avoid wasting my time on this game
Hey all, does anyone have the issue where using quest 3 with cable link, you have App Render GPU time 0.0* while CPU is spiking hard? Is there an issue with my PC or does this bottleneck the CPU?
This is normal. Those stats are unable to separate the actual GPU time and CPU time, my understanding is that the CPU time shown is actually CPU and GPU time combined.
Many thanks for the quick replies. The game has 40% headroom while alone on track, and in races, with max 11 cars it goes to -5%... I am using VR Optimised settings, and even if I lower the high impact stuff, the performance doesn't change at all. My specs are: CPU: AMD Ryzen 7 7800X3D Motherboard: MSI MAG B650 Tomahawk WiFi (AM5) GPU: Sapphire Nitro+ Radeon RX 7900 XTX (24 GB) RAM: 32 GB DDR5 @ 6000 MT/s (30-36-36-76, dual channel) I am posting all this with the hope that maybe I am missing something, I tried yesterday to make it work properly in races... to no avail. Additionally, with this same system, at 72Hz I play mostly on Ultra details in LMU, 16 cars grid and the following settings in Link and debug tool: PS: I also skipped SteamVR and have installed Open composite per app.
I would check what the CPU is doing: core parking, boost modes, etc. Also process lasso can help managing what cores are used for certain processes. In my case it helped smooth out the frametime graph by separating rr from other procersses.
I have the same experience on a Ryzen 5 5600X and an Nvidia RTX 4080 Super. What you will find is that some tracks are worse than others - eg any Nürburgring variant gives quite bad stuttering in a multiplayer race no matter how low I get the CPU time. Smooth in solo practice but stutters in multiplayer. Some other tracks you can get quite a smooth experience. I'm using Process Lasso, Oculus Tray Tool (I see you are already using OculusDebug which does a lot of the same thing) and OpenComposite to get massive performance improvement, but unfortunately stutter is something you may have to live with. There's a good guide for Process Lasso on the forum here somewhere, it shows which processes to move to which cores.
Anyone getting opencomposite failed to initialize libovr 3001 error when launching the game? I have followed the instructions and ended up doing: 1. Re-install RRRE 2. Re-install Meta quest link app 3. Copy opencomposite dll and ini 4. launch game with -vr 2.0 paramater Any help or suggestions are appreciated. Thanks
Are you using the (older) opencomposite dll linked in the first post of this thread? Later versions will not work.
Hi Robert Thanks for the reply, yes I am. This might not be the answer for others seeking a solution but it worked for me. In my case, I had a fresh windows install. During troubleshooting, I noticed that even steam vr is not starting up correctly - error 301. I read somewhere that you should start steam as Administrator (I'm always skeptical of this - as I am a damn Admin on my own pc lol) - but nevertheless this started steam VR successfully. Only after I opened RRRE in steam VR, I tried the opencomposite way again and it worked perfectly. No idea why - but here we are..
I have disabled the Hyper-Threading of the CPU in Process Lasso I no longer have saccades, I even increased the resolution of the headset. :yes: Well, it’s still ch.... to go through this software
Just tried it on my new setup with Quest3 and seems to skip steamvr! Dont see a difference in performance, but starting 1 less openruntime is always better
I get perfect performance, i can run constant 90hz on decent settings, but I notice every 20 to 30 seconds a small micro stutter.
"False alarm, the lag is still back. It varies by car and track, and some days it's impossible to play."
Nürburgring Grand Prix (and variants) is a good track to test on, it stutters more than most tracks. Test in an online session, that makes a big difference too (in my experience even an empty online server will stutter, but an offline practice session will be smooth).