VR Discussions, Questions & Feedback

TAA at 400 sharpening with above 1.5 supersampling in Quest 2 looks almost like MSAA high with 1.3 Supersampling, more blurry but zero flickering and aliasing.

But I'm now running at 1.3 Supersampling and 100 sharpening, because I get used of the blur and can set mirrors less detailed, because TAA works in mirrors too, so they look nice at lower resolution (was terrible with MSAA, zero antialiasing).

 

I spent about 2 hours last night painstakingly trying many combinations of settings to get the best result. For reference my setup is an i7-13700kf + RTX 4070 (plain) + Quest 3 + Virtual Desktop + Wired-Ethernet-to-USB-C for 1ms networking. (And of course using OpenComposite/OpenXR).

I finally landed on: Virtual Desktop: HEVC 10-bit, VDXR, manual bitrate. Horizontal FOV: 85%, Vertical: 60%, VDXR Render Resolution: 115%, Additional Sharpening 50%. Streaming settings are Ultra (not Godlike), 200mbps bitrate, 70% sharpening (in the streaming box in VD), No SSW, no Snapdragon Super Sampling, and Checked Increase color Vibrance.

In game: Graphics (just the important ones: Texture Resolution: high, Anisotropic filtering 16x, MSAA: Medium, Reflections: Medium, Details all Ultra (vehicle, track) , Shadows low, grass off particle details off. FX: Sunflares at minimum, Rays on, Post processing off, bloom off, rain and dirt yes.

This combination is getting me 90fps, and I think the magic combination was the high anisotropic filtering and the msaa medium. It keeps the GPU load under control while getting rid of aliasing and shimmer. I did hours of AI racing last night in all kinds of conditions and was very very happy with this balance. I hope it helps someone else...

 

If you want to have more stable performance when it get's rainy/dark, use reflections (both) on low, I have found that makes the biggest difference (not much of a difference to performance on dry or when it's not dark). I'm able to keep the performance very similar no matter the conditions by doing this, even with higher msaa and I don't even have that beefy computer on today's standards (I do use VD, ethernet cable with adapter and have limited by fov a bit),.

 

Using TAA in VR, I set no TAA sharpening ingame and use sharpening in config files.

MUCH BETTER RESULTS! AND I DON'T KNOW WHY! LOL!

VR configuration is fun as hell! Will build a bigger room and buy triples...

 

Not a "bug", but increase sharpening in AMS2 config files, for VR, is great with TAA sharpening ingame set to zero.

TAA sharpening ingame looks like sharpening the blur, really strange: an undefined blob with more defined thick edges. With config files sharpening, it's really nice

EDIT: after changing one time sharpening in config files, using ingame setting works in the same way now.

 

For some strange reason my VR frame rate is capped at 60 fps in the release version...
Using Virtual Desktop on a Quest 3, plain SteamVR, no OpenComposite or other tweaks.

Tried both 72 FPS and 80 FPS in VD, framerate capped at 60 fps in release version, normal behaviour in the beta...

Even copied the settings from the graphicsconfigopenvrdx11.xml fil from beta to release to make sure the setup was identical.

 

Anyone figure out how to get rid of VR stutter once and for all?

System:
Asrock B760 Pro RS WiFi
Intel Core i7-14700K
Zotac GeForce RTX 5080
G.SKILL TZ/RJ/FX DDR5 6400 C32 2x16GB
NVME install 2TB
SimHub with two bass shakers
Moza Wheel
Quest 3

Virtual Desktop Streamer Settings:
Ultra
72FPS
200 Bitrate
H.264 Codec

I will get solid 72fps with an occasional stutter and then drop to 70, 69 fps then right back to 72fps. The best I have found to eliminate this is by changing the following settings but then I am unable to have rumble effects through SimHub.

Any suggestions is greatly appreciated.

 

I just wanted to ask how possible it would be to implement Quad Views rendering together with Tobii eye tracking.

I know that eye tracking is already supported in flat mode, but would it be possible to bring Quad Views into the old Madness Engine?

iRacing recently added this feature, and it gives a huge performance boost — just like in MSFS2024 and DCS.

It would be amazing if something similar could be done for AMS2!

I also noticed that with TAA now in the game, you might already have the first step toward DLAA, modern DLSS, or FSR, which is really exciting.

Thanks a lot for all your hard work and for taking VR users’ needs into account — it really means a lot to us!

 

With a 5080, you should be able to get 90 frames per second. That should reduce the stuttering and lower the latency. Use OpenComposite/OpenXR and VDXR in VD. To avoid network latency, you can use an Ethernet-to-USB dongle (around €15).

 

Have you tested cropping the vertical FOV to get more performance headroom?

 

Why? I assumed this was an advantage of the Quest 3 processing the super sampling and improving image quality without taxing the PC GPU.

BTW 60% vertical FOV is brutal. I am at 80% so I barely see the black bars which always seem too unnatural for me.

 

I have been using Snapdragon super sampling for quite some time, but once I found that I could use render resolutions that I showed, the result was so good I didn't want to add any additional processing anywhere on the pipeline, even the headset.

As for the FOV? I don't find it brutal. If you were actually wearing a racing helmet you would find you need to look around a bit to see things because it would block your view. Try going and doing some karting with a full helmet and notice how it constrains your FOV. I just kinda figure it's like that. It encourages me to be more active in looking around while I drive. I even turn off 'virtual' mirrors so I drive more like I would in real life, glancing over at mirrors on either side. It also helps me avoid 'driving in tunnel vision' instead of properly turning my head and looking in properly at the apexes. So yeah, for other kinds of VR titles, this FOV would be intolerable...to me, in some ways it's addition by subtraction.

 

TAA works quite well for me on a Q3 over link cable.

I have not measured the performance yet but it looks better and resolves more jaggies than msaa medium.
Some of the trees look like they have a lot of noise but overall i think it helped the image.

My only complaint about the VR image is Reizas use of a 'cool tone' in the image, to the point where i can see the blue of the cool image bleed over a little. Overcast / Hazy conditions look fine, maybe a little to dark with PP on.
I think the VR image would look much better if they embraced a 'warm tone' for the scene.

Most of that problem is probably due to the q3 lenses.

 

I felt like TAA on my setup (see my earlier message) looked blurry and even setting sharpening to 400 didn't clear that up. Maybe I'm missing "the sweet spot"?

 

Use sharpening up to 100 and use a lot of Supersampling.

 

No I haven't and don't think I need to or would want to.

If I use the Medium or low this happens.

What I have confirmed without a doubt, once this starts, it will happen every 20 seconds. Regardless of which VDS setting I'm using. I can even be sitting still and every 20 seconds my fps will drop from 72 to 69 fps.

 

I expected more from TAA in VR and I'm having the same problems as you. Have you seen any improvement? My PC is a 9800x3d with an RTX 4070 Super and I use

 

FWIW I've tried TAA for a full day of racing adventure and I'm back to MSAA(high).
Clearer, sharper and very similar performance in that I can hit 72 frames with my Quest 3, with only occasional short dips in busy traffic at night.
Zero incentive for me to use TAA...
Maybe the "monitor people" find it useful.

 

Here, with a Quest 2 and 4070 Super, ASW ins't working with TAA enabled. Strange.

 

Pretty much same experience. In fact not even sure it had any performance gain what so ever.. maybe even negative impact (as reported by some other VR users). Sticking with MSAA Medium in VR Quest 3.