VR Discussions, Questions & Feedback

Good to know. I guess newer tracks might have more detail and might still need some further optimization in the future

 

Does anyone here run a Pimax Crystal Light (PCL) with OpenXR Toolkit?

If so does NIS upscaling work for you? Just got my PCL so I'm trying a heap of different settings to test how it goes.

Running Pimax Play at native resolution I had slight CPU bound instances with my 13700k/4090 system so I tried upscaling in OpenXR. FSR upscaling works perfectly but if I enable NIS upscaling it loads the game but crashes to desktop right after the first load screen (Reiza logo).

No real biggie because it works great with other settings but just curious why this was the case. There's a guy on Reddit with the exact same issue so it's not an isolated issue just on my system.

 

hopefully, also azure struggles a little bit

 

Hey guy, I made a VR guide on steam recently that can be found HERE . It is with a quest 3 but there might be things you could find helpful there in general

 

That is a lengthy read. Nice article for AMS new VR users.

 

I have exactly the same system as you and run AMS2 at native with no issues. I do use pimax ffr and used to use openxr toolkit but with CAS and FFR at quality. Moving to just the pimax solution has been fine - only hiccups with some tracks at night. Most settings are on mid/high.

 

"MFAA is meant to work with MSAA but in my tests did not improve VR antialiasing."

Change this to ON. It's about better MSAA performance without losing quality. Works the same in 2D and VR.

 

What i meant was that it actually made it worse in game. Ill change the wording. I do get better perfor,ance but only because it downgrades the anttialiasing somehow.
Acctually, you just gave me an idea to try

 

Apologies if this has been covered 1000 times before . . . I'm trying to switch from Quest Link to Virtual Desktop but can't get the game to launch, it crashes before the splash screen with the bugsplat report. I'm trying to start the game from the virtual desktop menu, and I've tried all the different launch methods (SteamVR, OculusVR, No VR with -vr in the special instructions) I know of and can't get this to work.

Anyone with settings that work that'll share would be appreciated.

Thanks in advance.

 

Make sure you are using the original openvr_api.dll file in case you at some point swapped it with something else.

If you haven’t touched that file check your graphics driver against what VD recommends.

SteamVR is the right mode to start AMS2 in.

I’m using VD myself, and had bugsplats exactly like yours when I had swapped the openvr_api.dll to try OpenComposite.

 

Install this and see if you can get it running. Just drop the file in the root folder of AMS2 and try to open from VD game menu. Should start right up.

GitHub - rodolZ80/bypass-oculus-detector: Windows Library that simulates not having the Oculus service running and having the VR Headset disconnected.

 

Very useful. I'll try some of those suggestions.

MSAA on high is very heavy though and while adding more antialiasing indeed reduces jaggies it also reduces sharpness of the image. I've found I prefer to run on medium and instead use the extra headroom to increase super sampling. Higher resolution is of course very gpu heavy also, but gives a better balance of AA and image sharpness in my opinion. This is on a 3080 card

 

Doing some more testing and msaa on medium is not as bad as i remember. Already have somethings id like to update but going to wait for 1.6 . Aiming to fina a blend of settings that work in all conditions, including storm weather if possible and rain at night

 

Aliasing is bad in AMS2
It’s inherent to the madness engine

I am lucky enough to push msaa to high and set high supersampling in VR with my 4080s

but even so running cars at night hurt my eyes

it’s a pity though because other than that it’s a superb graphic engine

 

NVidia card? Last driver does wonders here. Can run with more supersampling and less MSAA too with better visuals and better performance.

 

yes. Whats your driver version?

 

Hell, anyone who uses Virtual Desktop, what drivers are you using ?
I am still on the recommended 552.44 but want to upgrade them already, anyone using newest ?

 

Im always using the latest drivers but i dont race in vr, i play other stuff in vr.
Didnt notice any issues personally

 

Yep, although running at night is quite atmospheric it's just doesn't look great.

I'm on a Quest 3 (wired. Oculus VR mode), 5800x3d and a 4080 super and for a race when you're running at night for me the best compromise I've found is to pretty much max everything (no shadows) but then do 120hz with fixed Asynchronous Space Warp at 60fps. That at least is tolerable and looks OK but its not great.

For daylight running I max everything out (apart from shadows because the tree shadows are terrible) and go with 90hz. PC then runs fine with plenty of headroom so it's not running hotter than it needs to.

Although I can run the FoV at 1.0 / 1.0 I do trim it to .78 / .88 in Oculus Tray tool as it saves rendering stuff that you can't really notice.

 

Last one, 566.14,, paired with a 4070 Super and a R7 5800X.

Now I can go .675/.375 90Hz without headlights in thuderstorm, night, full grid locked 90 FPS with MSAA medium and 1.2 or 1.3 supersampling.