VR Discussions, Questions & Feedback

Since 1.6 I experience worse performance, with a peculiar behaviour. Generally, things run well: I got experience with VR in several sim and a decent system (7800x3d+4080+64gb+q3) and I find Ams2 quite easy to run if you don't exceed in res.

Since 1.6 I got several stuttering, here and there, that don't seems related to particular track/situation. This stuttering are also quite peculiar, because the are of about 1-2 second, with a slight ghosting (and I don't use ASW/retroprojection), than the sim come back tò normal performance.
Did you experience something similar?

 

I had some stuttering for a while but, in my case, it was solved by enabling HAGS (Hardware Accelerated Graphics Scheduling). It's often suggested to leave HAGS off but, it seems to work well on my system. In either case, it's probably worth a try.

 

Leaving HAGS off is one of those old time remedies that really no longer applies. Today's high end systems work well with it on.

For anyone getting stutters I recommend adding an exception to Control Flow Guard and turn it off for the AMS2AVX.exe

What is Control Flow Guard in Windows 11/10; How to turn it On or Off

 

hi so I don’t play at 90 fps. I’d have to test it out. But it’s going to depend on time of day too. As my stats show even with a 5090 you’re not going to get a good FPS unless it’s clear weather and midday. We need more lighting options to tone down the impact, which is the biggest fps killer.

 

yeah but here’s the odd thing, I just sold my 4090, for only £200 less then I paid for in October 2022. GPU prices are very wrong

 

sorry for my tardy reply. I’m playing at 72hz. So I was using a stock tracker and good timing. Tbh if you are tight for money, I would not get a 5090. There is a real trade off of your wallet and just reducing the resolution. For 2D games, it’s not a huge bump.

I would like to see Reiza add DLSS, the new transformer model is great, even ACC looks good. But I think others have said DLSS can’t be added. Also as I state above, Reiza need to optimise night racing or allow users reduce the lighting effects. A Crystal at native resolution using a 5090 should not be getting such poor FPS.

 

Hi, thanks for the tip, it helped a little bit for me, but i still get microstutters. Never had them before. Now regularly. Must say it is pretty annoying and i have no clue what is causing it.

 

VR is complicated when it comes to micro-stutters. Aside from the typical recommendations (resolution and settings), there are other measures that can help.

It's always a good idea to restart the Quest 3 before connecting to the PC.

Leave some memory space free on the Quest 3. If the Quest 3 is full, it sometimes lags even natively.

When using Bass Shaker, the vibration in VR can cause a shaky image, which is often perceived as unpleasant or stuttering.

The Quest 3 cameras should be clean, the lighting should be sufficient, and ideally, they shouldn't focus on shiny or reflective surfaces. Even such trivial things can lead to hiccups.

 

Good deal indeed. The GPU market is really rotten. I’ll stick to my 4080 super for a while.

 

The best I can record and still be able to drive is daylight in 4K. I record this clip with some hud gadgets on with the settings I use to play at 80Hz:

This is the closest I can replicate how It looks in headset and get rid a bit of YouTube compression. But my 4070Ti Super suffers to record at 4K and compress for Quest 2 at same time.

 

This is just astonishing!

Equivalent to 32 1080p screens

 

The flickering tree shadows continue to detract from a great experience (even on ultra) so I have now turned them off. Actually the Core Lighting is very good and overall I think gives a more realistic image than the flicker.

imencourage you to turn exposure down to 0.7 and shadows to off and see what you think

 

Since neither recording shows a live image, I find it easier to benchmark with PC recordings. I enjoy watching your videos because, just like me, you like to experiment until you get better and better.

PS: Have you ever experimented with an Ethernet-to-USB dongle in Virtual Desktop? I've been doing it for two days and I'm very impressed. No problems at 500 Mbps/OpenXR OpenComposite/ with a latency of 26 ms. With Wi-Fi (200 Mbps), I easily get 46 ms and with the Oculus Link cable, I get 39 ms (at 500 Mbps). The FOV tangent can be adjusted even more precisely with the new OpenXR Toolkit mod than with the debug tool. I always thought the Link connection was the best way. But then Virtual Desktop enabled mixed reality with an update. This lets you use the Q3 cameras to overlay yourself and your steering wheel into the game. This trick completely obscures the lower cutoff FOV tangent. Instead of a black bar, you now see yourself with your own steering wheel and other features. Since I've improved the latency with Virtual Desktop compared to every other connection option, I now believe Meta's Link USB connection can easily be improved.

https://amzn.eu/d/9itvAmw

This dongle costs only €18, and my 4070Rtx suddenly feels like a 5080Rtx. It's incredible how easy it is. Just turn off Wi-Fi on the Q3, connect all the cables, and get better performance with Virtual Desktop. There's also VDXR, OpenXRToolkit, OpenCompsite, and a custom steering wheel via Mixed Reality. The dies has fallen for me. Virtual Desktop & Ethernet cable

Virtual Desktop per Kabelverbindung

 

Post processing OFF (create a lot of contrast in shadows) and 1.4 supersampling with MSAA medium/high and I get rid of this flickering.

 

I only tried Virtual Desktop with WiFi, but after some NVIDIA driver update, I don't know what happens, and I can run at 800 bitrate with not noticeable latency and without any glitches with Link, and I stopped my settings madness at this specific variable.

I use Quest 2, so I think not mixed reality for me...

 

I've been experimenting with VD and Ethernet for about two weeks now. Honestly, I always thought Link USB was the best. Now I think differently. Faster and better with the same system (with charging function). The advantages of OpenXR, OpenComposote, Snapdragon SS, percentage filter settings, foveated rendering (15% headroom), etc etc ect. In the end, I had gained almost 25% more performance with the same image . With Game Optimizer, you can significantly improve the Quest's recording quality. Even in 3d is possible! (Wow!)
And Mixed Reality... well... is actually the new VR.

( recorded with the quest3)

 

If anyone is chasing DMAS New Zealand, $183 AUD delivered, the owner on the business seems very nice. I will update when they arrive. I ordered at 2pm and by 3pm they were with the post office.
Here if your interested in grabbing them while he has stock Actiontech
I think he has 4 pairs left.
On the site it doesn't have delivery to Australia but i spoke with the owner and he is able to do it via invoice through email and use credit card.

 

What's with the graphic engine on this game in VR. It doesn't seem to scale very well with resolution, it's as if it's being limited or downscaled. It's as if the internal rendering resolution is much lower than the headset rendering resolution.
I'm running a MeganeX headset at 4.5k x 4.5k per eye, yet it still looks around the same or maybe a little lower than my Aero running 3500x4000 per eye. No other game is like this, even Project Cars 2? I don't get it. It should be much sharper than I'm seeing.

 

There is a bug in meganex compositor and a fix that is explaned in this video of MRTV:

 

Yeah, I've been using the fix. That's how I noticed it running less resolution than other games. Certain things are high resolution like the chicken wire fence , while others like cars don't seem to be as high. Very strange. I might start messing with the .ini sharpening. see if it's that.