VR Discussions, Questions & Feedback

With Oculus, open OculusDebugTool.exe and use "FOV - Tangent Multiplier" option. Not sure about other headsets, but a similar method should be available.

 

Thanks, but i have Pimax Crystal Light

 

SteamVR per app video settings > reduce FOV slider > Advanced > set upper and lower to 50 to 60%, outer to 80 to 100%, leave inner at 100% > reduce render resolution slider until you have stable performance. Restart game.
If not using SteamVR, there is an OpenXR Toolkit fork that can do it called crop2fov but don't know how to use that or recommend it

 

I noticed the first problem too with Quest 3 and VD if I was using open composite + VDXR. Tried changing the dll back to original and used SteamVR and it was all good.

 

If you use Virtual Desktop then it is here.

 

Here I found in internet that after start logoff and login in Windows do the trick too.

But I still can't play in 120Hz PCVR after v76. Encode/decode have spikes in any Link refresh rate if I set 120Hz in headset.

 

I have fps drop after 20-25 mins of race..goes down to 35-30 fps, and not going back up, theres no issue before 1.6, is there a solution for this ? (Rift S user)

 

Anyone ?

 

Not got a solution but does the same thing happen if you are just hotlapping? Are you running Simhub, Crewchief etc? If so try running with no background apps to eliminate them as an issue.

In general 1.6 seems less stable in VR, I’m running a Quest 3 with a 5090 and a 9800x3d and microstutters are worse in this build. I did have a race at the weekend when I had similar issues to you where on the cooldown lap the framerate completely tanked. Not played much recently but will see if it happens again.

 

Have you turned on ASW ?

 

nope, its compeletly off, im only running crewchief, no other programs

 

Anyone on Quest 3 having an issue right now where in SteamVR and virtual desktop, you can't use the touch input when in the main menu or wheel depending on which one you used second .

I boot the game up (Virtual Desktop by the way), while loading i switch to desktop view and use my touch controller to navigate to "Create server" and when i click on Host Settings to write the name and password, i do that and then get back to the menu my wheel no longer works !

If i went into that Create Server menu with the Gaze Control and using just my wheel, then the touch controller mouse cursor no logner works and i cannot use the SteamVR keyboard to write the name or password, or click on ANY menu in that server hosting screen !

If i go to my PC and use the keyboard while the game is back on my full VR screen it works there, but i cannot go through my SteamVR desktop view to use the VR keyboard anymore when previously it worked !

Once i get into the actual Practice / Qualifying / Race both wheel and SteamVR mouse cursor and keyboard all work again, but i have to resort now to - Start game in SteamVR, be in FullScreen VR mode and get into the host settings using the Gaze Control, go to my PC with the keyboard away from me to write server name and password, sit back in my rig and start the server up. It became very annoying .

 

Did some testing this afternoon. Performance seems to be deteriorating over time when in game.

System, RTX 5090, 9800x3d, 32Gb of 6000MTS CL30 memory. Quest 3. Windows 11 Pro. Using Wired Oculus Link and the Oculus VR option in Steam.

Daytona road course, full grid of LMP2 cars. First 2 or 3 laps mainly OK a few stutters, after that they gradually get worse until it's essentially unplayable.

Rebooted, started a race with the same scenario then paused the game by hitting the escape key on lap 1 on the back straight before the bus stop. The game is essentially running fine at that point. GPU utilisation is in the mid 40s to mid 50s. CPU in the 30's (I wasn't monitoring individual core performance) I'm locked at 90fps with most things maxed out

Went away for 20 minutes came back, resumed and I'm down in the 50fps range and the GPU is at 95% (I have ASW off). This is a thing I've done quite often in the past and the game has been fine,

I haven't played AMS2 much recently, but I have played since 1.6 mainly on my old PC, as the current PC is a new build (I was on a 4080super with a 5800x3d and was running very similar settings) but back then I would barely get a stutter.

I think something may have happened in the last couple of post 1.6 incremental builds but it's not necessarily impacting everyone.

I've tried a bunch of the usual stutter fixes with no luck, I'm tempted to wait for the next release before I spend a bunch of time on it.

Bit of a first world problem, It's just annoying that my old PC which was far less powerful running an AMS2 build with a ton of mods and skins was working far better than my fresh install on new kit.

 

A little bit late, but I'm using PSVR2 with SteamVR and I have zero problems with AMS2.

 

I'm new to Virtual Desktop, coming from Quest 3 + link and my question is: does it works with OC or just SteamVR? As Quest3 user, OC was the obvious chose but if I start AMS2 with VD runtime I got only 2D-theatre mode, not real VR. If I start VD with SteamVR, here "normal" VR.

 

Yes it works with OC. You also need this
https://github.com/rodolZ80/bypass-oculus-detector

 

For the G2 users, don't throw your headset away just yet.

 

what resolution and what MSAA settings are you using?
Have you looked at FPSVR to see what your frame timings are, I usually aim to get it averaging 9ms.

 

Having same issues in VR. Performance on a fresh launch of the game is as normal, can just run the game with no issues. Then after a period of time in race stutters begin then after further time beyond that it just becomes a VR slideshow. Unplayable and quite nausea inducing. Such a shame because AMS2 has been my go to VR sim pretty much since it's release, and as I only race that way it sucks that it's not working the same way. Hopefully it's a memory leak in the game or something that they can patch in the next update but in the meantime I can't really play 1st world problems but still.