VR Discussions, Questions & Feedback

I had a Reverb G2 about 2 years ago and experienced the same strange behavior. I never got it solved, that's why I quit with VR. Now I am back with Quest 3 and until now all works fine.

 

Hi guys,
I am very happy mit my VR Look & Performance in AMS2 using a 5800X3D CPU and RTX4080 GPU with a Quest 3.
I have set OpenXR as default runtime and starting the Game in Steam via Oculus option.
I tried to deal with OpenXR Toolkit & Open Composite as well, but for whatever reason its not working. I am not able to open the Open XR Toolkit HUD in the game. I have installed the OpenXR Tools for WMR as well, but get a communication issue when opening. I can't fix the issues, so I am thinking about reinstalling Win11, but the questions is, is it worth the effort. Is there a significant performance boost using Open XR Toolkit over Oculus Open XR?

 

Did you try and clean environment data in WMR settings? This often helps, but sometimes you need to redo the room scanning thing again

 

I can confirm this. ALWAYS when the G2 started drifing in AMS2, it was the environment data in WMR settings, cleaning them always fixed it.

 

My Quest3 would work now with 120 hz but I still use 72hz because it’s the only refresh rate where I get constant fluid framerate in every situation (night, rain, replays) @ultra settings. Every higher refresh rate brings occasional stutters in demanding situations and this is a no go for me.
But I’m happy with my “only” 72 FPS…

 

Hello, anyone here using the Virtual Desktop app with the Quest 3 ? I am trying to figure out why the bitrate is limited to only 100 mb, while with Steam Link it can go beyond 250. And while Virtual Desktop runs better for me, it looks just flat-out worse with the lower bitrate than Steam Link. Anyone else can share their experience ?

 

Which codec are you using and what's the maximum bit rate you can select under the streaming tab in VD?

 

I was just about to go back to this forum and write that i found the solution: Codec was set to "automatic" but i found that for more you need to select this one:

 

I have a quest 3. I find that codecs like HEVC and AV1 @ 200Mbs work fantastically well in other titles when using VD, but in AMS2, some tracks tarmac textures get crushed and look pretty awful at that bit rate with those codecs. Link Cable on the other hand using 940mbs H264 looks great.

A good example of this is Azure Circuit. I find even at H264+/400Mbs I can see compression artifacts in the tarmac. 400Mbs is about the max my dedicated Access Point (WAX202) can reliably handle. But even testing at 500Mbs I could still notice artifacts that I just don't when using Link Cable.

If you don't notice them in VD, don't go looking for them because once you notice them, you cannot "unsee" them.

As a result, I use Link Cable for AMS2 typically now. Funny enough, not all circuits exhibit the same level of tarmac texture crush and AV1 is good enough for those, but it's a mixed bag for me. The problem I have with link cable is that the battery drains a lot faster when using it and now after v63 update, I sometimes (emphasis on sometimes) get the "dirty/moisture in USB" warning. Clicking OK on it doesn't seem to affect anything, but it's annoying nevertheless. Hope they fix this in the next version but the way they deal with software rollout and issues is flat out weird.

You never seem to be able to win with VR... There's always some compromise no matter what solution you choose.. at least for me.

 

Hi guys, I love this game, I play in VR mode but there is a thing to bother me a little. The cars slides too much and it feels unrealistic. I saw a lot people complain about it too. I think its about the game physics. There is a way or trick to adjust the car before race to stops slides too much?

 

For that non-VR type of topic you need to write here:
Automobilista 2 V1.5.5.0, Le Mans & Endurance Pack Pt1 RELEASED - Now Updated to V1.5.5.6

 

Thank you for taking the time to write recommendations and tips.

I got a 3060 Ti, now did 30 minutes of tests using "HEVC", full 200 mb bitrate, Sharpening at 50%, Snapdragon Super Resolution ON, ASW disabled, 72 hz, tried the HIGH image quality but there was no real visual difference but it increased latency above 13.9, so i went back to medium and have it at a low 11 all the time with a full grid running graphics relatively low but Track and Car detail set to medium, smooth experience all the way !

And even though there is a tiny bit of compression visible at some points (Silverstone 1991 was the worst offender), it is so tiny that i cannot notice it anymore with these settings and the extra sharpening definitely improved the image quality for me too. What is also odd that in the 30 minutes of testing my battery reduced only by 5%, i am pretty sure it is because i am running some lower settings especially with the 72hz mode, but my eyes don't see any difference between 72 or 90 so might as well save on battery life.

 

you got few "disagree" but I can understand your perception if what you mean is like driving car on ice.

I had also this feeling continuously in AMS2 until I started to test the Custom FFB files flying around on this thread
Automobilista 2 Custom Force Feedback - Overview & Recommendations

I am a MOZA R9 DD owner and the work from this guy @Joaquim Pereira did wonder for me to eliminate this feeling and get really to enjoy the various car physics in the Game and obviously the FFB on my wheel.

I can also agree that this "car sliding too much" perception was higher in VR than playing on my 4k TV so using such a Custom FFB really helped me to enjoy the VR experience fully now

 

Where can I change those codecs? I use Link cable with my Quest3 too at 72 hz, everything at ultra settings and highest resolution in Oculus PC app. I get constant fluid 72 FPS in all scenarios but in Monaco I see the bad tarmac textures you described. So you mean I could get rid of those compression artifacts by changing the codec and/or the Mbs? Where/how?

 

I had something very similar and my set up is almost identical - tracking loss but also regular heavy frame drops.
I narrowed it down to iCue v5 as I spotted it was taking too much focus in PerfMon. I sent logs to Corsair and they could see a USB issue but no resolution. Rolling back to v4 resolved it for the most part. I went back to v5 recently and it did seem to have resolved itself but would recommend a completely clean install of iCue (how to do that is on the Corsair Support forums). Worth a look.

 

I am a Q2 owner but should be the same for you, you do this in ODT

 

Thank you, will try. So this is some kind of “hack”, as the settings are not inside the Quest headset menu nor in the Oculus PC app settings?
Are there negative side effects when changing those settings? And should I only change the two settings you circled and leave “Link Sharpening” for example as it is?

 

you need to experiment. you have a Q3 so AV1 codec will be available I believe, I have only access to H264/H265
my settings that gives me the least compression is what you see in the screenshot, including Sharpening on Quality

 

I get those in Virtual Desktop not Link Cable. I changed my Link Cable settings to be H264/940Mbs. I make these changes using the OculusDebugTool.

Here's a link that describes what settings to use for OculusDebugTool (8 minutes in)

EDIT: Ah, I see Nolive721 already responded. OculusDebugTool has not been updated to have AV1 yet (at least mine hasn't), but doesn't matter because I think its max bit rate decode is 200Mbs anyway which is half the problem with Monaco tarmac.

 

So AV1 would be better than H26x?