VR Discussions, Questions & Feedback

I

The higher the resolution the headset the better it is it seems.
With a crystal light I get a much cleaner image and better performance.

 

Adding to this as I am going to win this battle (so I think)

Been working on this and feel like I narrowed it down to what I was worried it would be.

It's got to be VDS. I can get some instances where I'll get after a fresh reboot or startup(not always) a good 5-10 minutes where framerate stays locked in at 72fps. If I end that session and start AMS 2 up again, or leave track and go back is usually when it starts up. It does start after a certain amount of time as well and happens on every track. What is certain, when this starts it is a 20 second stutter. I can sit in one spot and every 20 seconds it will stutter and drop 1-3 frames.
I installed and ran PC2 and it does the exact same 20 second stutter.

I've tried closing out of simhub and end all processes - still get 20 second stutter

I've set AMS 2, Simhub, VDS all to high priority. - still get 20 second stutter.

I have run low in medium and still get 20 second stutter.

I thought perhaps it was SimHub and AMS 2 but I think this is a Virtual Desktop issue. I get the best graphics and performance (minus this stutter) from VDS, not sure where one goes from here but I'm committed on trying to resolve this and hope it helps others.

 

which super sampling? The in-game Super Sampling? Snapdragon Super Sampling? Increasing VD render resolution? Please clarify. just a bit confused.

I had this problem in LMU and it went away when I used Process Lasso to forbid LMU from using the efficiency cores of my i7. And it was happening for awhile in AMS2...and then ...it just went away and I wish I knew exactly why.

 

Nope I tried different things (Nvidia driver settings, Virtual Desktop settings, higher framerates) to clear the rendering pipeline between processor and GPU as TAA needs consitent frames to be able to work properly. But the effect 'fast head movement = no antialising for 0,5 sec' still persists. So I am back to MSAA medium and hope that maybe Reiza will optimize TAA in the future as described in this message by @Cas.

Fingers crossed! Personally I prefer a slightly blurry image if it gets rid of the jagged edges so TAA would basically be a match made in heaven for me.

 

I tried 60% vertical FOV yesterday and you are right, it could be argued that this even enhances the immersion. And as it also reduces GPU load I think I will leave it at 60%. So thank you for the suggestion!

 

So regarding TAA the general consensus appears to be;

• Higher resolution headsets/higher super sampling works better with TAA
• Config sharpening increase works better than in game UI TAA sharpening
• Wait and see if Reiza do more internal work to the code to further improve TAA

I'm too low on power to be able to achieve higher super sampling, plus everything's working just fine in MSAA on LOW for now but I'm keeping a close eye on this subject for future reference

 

Im using TAA in Pimax super.

Like others have said, its soft / blurry at mid to long distance.

Ive over come this a little bit by running 110% resolution with sharpening. But of course the performance hit is huge. Its not really a solution, but ok for someone who doesnt need high FPS to enjoy the sim.

 

could you please tell me which Hz mode you use? 72Hz, 72Hz upscale odee 90Hz? 110% Renderresolution on super is quite much, so I guess you use 72Hz upscale mode right?

 

72HZ
I also crop with OXRTK to try and claw back some performance.

 

I tried a whole bunch of TAA options, but no matter what I do, on my Quest 3 it looks muddy, like someone has smeared vaseline on my headset lenses. I went back to MSAA Medium with 115% render resolution on Ultra in VD and 12x anisotropic and I get a HIGHER frame rate and sharp graphics. I don't know why TAA is just slower and worse looking for me, but it is.

 

Taa is working great for me after some fiddling.
Not sure why but the original openvr api dll 238kb has been working for a while now without having to run steamvr whereas before I had to use a different one, and it's working well.

These are my settings if anyone's interested.

vr Trilinear
Render frames ahead 2
Taa on
Sharpening 0
Shadows high
Track reflections ultra
Vehicle detail ultra
Track detail ultra
Grass off (sorry gm)
Both particles high

Oculus sharpening strength in documents to 3.0

Using oculus link (iniu (inui?)cable is awesome)
Oculus tray tool ss 2.0
Horizontal fov 100
Vertical fov 0.50
Oculus tray tool encode bitrate 300, was 700, that made most difference in fluidity with no noticeable loss in visuals and it looks great especially in the dark and rain.
Quest pro set to 72hz and 4090

 

Quoting myself in case anyone runs into the same problem.

Found the cause, and it was a strange one:
I'm using AMD's Radeon Chill feature to limit the framerate to match my screen when not using VR. Radeon Chill has two FPS settings, Idle and Peak. I set Idle to 60 and Peak to 120 (my screen's max refresh rate). Idle is frame rate when not much happens on screen, when paused, in menus and so on, while Peak acts a max framerate limiter. My settings:


Idle is described like this:


But it turns out that in VR no motion is detected, why I don't know as the VR image is mirrored to the screen, so when in VR the Idle FPS value in fact acts as the FPS limiter...
So when I turned Idle FPS up to 120, the frame rate in VR was no longer capped. Took a while to figure that one out, especially as turning Radeon Chill off didn't do anything...

What's strange is that in the beta this doesn't happen, even though I use the same settings for the beta .EXE file...

 

I think I solved it. By chance did you find different channels on your routers? I changes my main 5G routers 2.4 and 5G channels to lower used ones and disabled on the wifi 6 router the 2.4 and 5G option. I think that solved it. Thanks for your help!