VR Discussions, Questions & Feedback

Your PC is a laptop? If so, the specs in your signature are misleading. Is it actually a 13900H and 4080 mobile? If so, you probably need to dial down any suggestions you got on the basis of it being a desktop 4080. Power budgets change from laptop to laptop, but a 4080 mobile would usually be considered equivalent to a desktop 3080.

You should probably look for signs of thermal throttling or power limiting, especially if the performance seems to be variable. Something like HwInfo may help you monitor that sort of thing.

 

Was it bad performance from the moment you started or was it fluctuating? If you get bad performance overall for something that was previously performing OK a quick thing you can check is nvcontainer in task manager. It should probably be running at 1ish percent CPU utilisation. If is running at 4,5,6 percent its bugged out. I get this occasionally and my rock solid 90fps will be struggling to hit 60. A reboot normally solves it.

If its random stutters that don’t seeme to be tied to GPU/CPU load as I mentioned previously try turning off HAGs see if that helps. Then look at the root enumerator issue I posted the video for.

 

I just received a Pimax Crystal Light a couple days ago. It took me a while to find a decent setup to start with (after disabling two of three monitors) but, can now run it fairly well (Using OpenXR / Open Composite). It's not running as smooth as my Index (on Steam VR), though.

Now I need to optimize game performance for better FPS, and I still get a little bit of jitter now and again (even though FPS is constant), especially in open cockpit cars. GPU seems to be underutilized though, as it doesn't make heat like my triple setup does.

If anyone can offer some tips to optimize AMS2 VR performance, I'll happily give them a try. It almost seems like the Left / Right displays are not totally in sync, as the AI cars sometimes look like I have double-vision.

BTW: Default Pimax speakers leave a lot to be desired, a major difference from the Index HMD. I was just about to remove them to accommodate headphones but, Dmas speakers just came back in stock so, already on order.

 

When I ran a Crystal with a 4090 :
3820x4324 or something similar
MSAA - LOW
Cars - 10-15
All sun settings etc off
Bloom off
Crep rays off
Car and track detail set high
Low on everything else

Night time/rain, didn't bother.

 

Yeah, those are some things I can do to gain some FPS. Thanks for sharing info.

First, I need to solve the intermittent jitter, could be frame drops or something like that. It's not that bad but, should be smoother than it is. I'll keep trying device settings for now to see if I can find a cause.

 

have you ran FPSVR? if you're running 90hz lower your resolution and settings so it never go over 9ms.
The jitter is probably you being borderline 90fps and dipping on occasion.

 

I'll try monitoring for a bit and see where it lands. I did try running lower resolution and half-rate but, the jitter was there in every case. That's why I think there may be a conflict somewhere and I'm new to OpenXR so, might be using it wrong.

Initially, I couldn't get the Pimax to work without running it through SteamVR and that was anything but smooth. So, at least I've made some headway now.

 

If you are using the latest OpenComposite, try using the 64 bit dll from the last one on this list. It's known to work well.

Commit 43e551a4506880ab1a71b8b9fec2fd7fbb27372f - OpenComposite Builds

 

I used to like OpenXR/OpenComposite with my Reverb, but I didn't think it brought anything to Crystal/Aero. I felt it altered something in the rendering or IPD, made things appear less 3D. I tried it a few times with fresh installs etc and something just felt wrong and each time I uninstalled it after 5 minutes . Very strange.

 

After a long journey, I discovered the Holy Grail for Madness Engine and VR:

Go for higher pixel density in headset and disable any anti aliasing.

I do not know why, but this engine appears to render in VR in a lower resolution, and If you don't use a lot of post sharpening and massive MSAA, It looks like a mess, and with all these "post workarounds", things flickers like hell with a lot of fidelity degradation.

Higher pixel density solve ALL the problems with even better performance.

 

But what gpu are you using? Supersampling is very taxing on the gpu

 

Just a 3060ti. In a normal game, in VR, yes, it's taxing. But Madness Engine have a lot of strange things in VR. With 1.4 pixel density in Quest 2 Max resolution, I have better performance and MUCH better visuals than using sharpening in AMS2 files with MSAA medium.

Only in Madness Engine this happens. Strange, but works.

Without recording, solid 90 FPS daylight in Daytona.

Give a try.

 

The most strange thing: when I go up pixel density, better mirrors for free FPS.

What the hell runs inside Madness Engine, hope Reiza someday can fully undestand. I give up.

 

So I tried PimaxXR yesterday and managed to reduce much of the jitters (fast moving objects) by reducing refresh to 90/45Hz (using half-rate feature) and reducing most AMS2 graphics settings to medium or lower.

UPDATE: Solved my AMS2 Launch crash issues (OpenComposite mode / PimaxXR).

• Disabled OpenXR toolkit
• Uninstalled SteamVR
• Cleared AMS2 Graphics XML files (all)

OpenXR toolkit doesn't work any longer but, at least AMS2 will launch again.

 

I supect that Madness Engine in default headset pixel density - and I don't know why - render the image in some kind of lower resolution objects far distant. It's like you play with more than one resolution - great in cockpit and crap more than 50m ahead or behind. The workarounds other than more pixel density in headset, like agressive sharpening editing config settings, only apply a post processing filter in this far crap resolution (and near objects too), and this creates more aliasing and degradation in raw visual. Add this to crap MSAA performance, and It is a disaster. And this causes the massive flickering in shadows - that goes away with more pixels density, even in lower shadows settings.

With more pixel density, it's like finally this game is running in the same resolution and quality 1m away from driver to 2 or more kilometers. It's almost a new game in VR.

I believe it's a bug or a coded "feature" to improve VR performance, causing the well know bluriness of Madness Engine in distance in VR.

 

Hello. I'm a newbie to VR. How do I increase pixel density for my Quest 3?

Thank you!

 

Start the game in VR and in the main menu open the "Virtual Reality" submenu, it is there.

 

I found these videos helpful for Meta Quest3, I found quite good settings as a result

and

 

Are you using Oculus Link (USB or WiFi) or Virtual Desktop?

 

Not true at all with my headset(Pimax Crystal). The opposite is true here; MSAA is mandatory to get rid of the shimmering/aliasing, even the difference between 2x and 4x MSAA is very visible and worth the tweaking to get it stable at 90fps.

Without MSAA the aliasing/shimmering is so bad that AMS2 is not even playable to my standards, so you must be doing something completely wrong.

Yes I also tried higher pixel density instead of MSAA, it doesn't fix the shimmering/aliasing at all, only MSAA does. SMAA doesn't fix it, maybe you used that instead of MSAA?