From observing the cpu activity in Process Lasoo you can see that RaceRoom is saturating 16 threads. If you limit the multi-threading to 8 threads RaceRoom immediately runs more efficiently, cpu frame times drop and the game is free to run at 90fps. So the frame drops, low fps and stuttering is due to the cpu overload. You can also change the allocation of threads in Task Manager. However a few other things must have been modified in the current version since the update, and unfortunately that has negatively impacted vr performance significantly in the Pimax Super 57ppd. Other vr headsets might not have been hit so hard. Previously I was running 8xSSAA at a higher res than I am able to now. EDIT - I was using SGSSAA but just tested 4xmsaa + FXAA ingame setting plus 8x SuperSample and it is very good still maintains solid 90fps. The new lighting, whilst very nice in flatscreen, is over exposed in vr. A toggle to switch that off would be great as the auto exposure adjustment in the game graphics settings does not change this new lighting effect.
Framedrops is the only issue I can get rid of. I had this issue before the update too, but different. Now sometimes it starts doing this continous frame dropping and it goes like this for a lap or two, then it goes back to normal. I provide a screenshot from an empty practice session with the continous framedrops happening. Multithreading disabled, System forced to run on the 8 efficiency cores, pimax runtime runs on 3 performance cores and Raceroom runs on the remaining 5, using less than 5% of total cpu usage, evenly distributed load on 5 cores without using any of them on full capacity. The total CPU load is around 16% (10% pimax, 5%RR, 1%system) GPU load is also just around 70% maintaining a healthy 9ms frametime, due to lowered graphics settings and empty track. p.s. It only happens in Raceroom, on 2 different operating systems with different driver versions.
Couple of queries; - Anyone getting slight flickering in the clouds? (both eyes) it's not bad but it's "there" so can be a little bit of a nuisance. - The VR Optimized Settings, does that change anything in the background? or is it purely a Preset like the regular Low/Medium/High etc etc? thanks
Yes, I do. I meant to post it tomorrow in this thread https://forum.kw-studios.com/index.php?threads/graphics-bugs-in-vr.20739/ I opened for VR graphics bugs. As far as I found out until now, flickering is heaviest with 'Scattered Clouds', less with 'Few Clouds' and almost not noticeable with 'Clear' or 'Overcast'. I cancelled the feature race at Road America because I couldn't concentrate on driving, so in some cases, it is bad.
Have this too. And - don´t know if VR only - RPM lights fail to work correctly, weather related too. RPM lights are on constantly. Experiencing this since the last graphics update.
Yeah I've been getting that too, it comes and goes though. Restarting the game fixes it for a while. For clarity these are the in-game lights in the cockpit view, not the ones on our real-life wheels.
Before the update, I could still open the Open XR menu, but unfortunately, it doesn't work with any other openvr_api.dll or composite.ini files. Anyone have any ideas?
I had this today online, did Qualifying laps and it was just fine, got in the race and all the RPM lights were on (Mazda MX-5)
Which files exactly do I need? I've tried various ones, but unfortunately, the menu won't open anymore. I'd like to use foveated rendering again. It worked perfectly before the update.
I can not get Opencomposite to work with a new Pimax. Crystal light, to be fair I could never get it to work with the Quest 3 it just replaced, I've done as instructed but no joy, I get the error 'libOVR session 1007 '.
Well I succeed. The openvr.dll is a version from July 24 and this is my ini: "supersampleRatio=1.3 enableLayers=true enableCubemap=false threePartSubmit=true useViewportStencil=true dx10Mode=true"
What Pimax headset are you using ? The Opencomposite files linked in this thread are for Oculus / Meta headsets. No other known Opencomposite dll will work on Pimax. Please provide a link for that version you have that works on a Pimax headset.
Hi, can you tell me where did you get the file? The version i have is from July 7th and it does not work Or if anyone has any help on how to run in in Quest 2 using Virtual Desktop, the help will be greatly appreciated. I just got the game yesterday and i can not have it running in VR.
At last I could run RR decently. For me the problem was that X3D mode was disabled in BIOS. I enabled it together with PBO, Curve Optimizer and now it looks and runs well. I am using VD 90Hz/Godlike and pretty high in-game settings. I have7800X3D/7900XTX. Those who have X3D CPU check the BIOS settings that X3D mode is not disabled.