VR Discussions, Questions & Feedback

Is the DLAA more performance intensive than 8x MSAA or is it comparable to 4x?

 

Wrong and wrong.
I was talking about framegen vs QVFR

Maybe read again the convo.

 

I ran QV mod last night on my MeganeX. I usually run 5600x4000 per eye (Sboys3 driver says it's 1:1 with the panel) with the game on medium/high settings and the QV didn't really make much difference , even when ran in performance mode.
What did make a difference is the QV DLAA, it looks much better than MSAA high + any amount of super-sampling I could throw at it.

 

He’s replying specifically to this bit

“Edited (did not see your signature on mobile): Aha, Pico Neo3 Link. No eye tracking - QVFR is not for your headset then”

By saying that fixed QVFR is still working well for people even without eye tracking.

Of course eye tracking allows bigger gains due to the ability to be more aggressive but that’s what the comment is about - QVFR doesn’t necessarily need to be dynamic to be beneficial… you just have to be more conservative with the settings

 

Performance wise just tested.
msaa is a bit faster, but in my testing here, was marginal

 

Yeah I didn’t see much difference between MSAA 8x and DLAA in terms of perf, but apart from the current issue with trees the image is *much* better with the DLAA option all else being equal (preset M or L were notably the best for image stability).

this chap is intending to roll out a completely different pipeline today using MVR (like iRacing) which should address the CPU overhead for anyone having CPU bottlenecks and then will be looking into full DLSS implementation (including I believe DLSS NR).

hopefully Reiza will take notes….

Out of interest did you try different presets? I personally found Preset M to be the best for keeping the image stable

Trees are a bug/quirk though, hopefully will be fixed soon.

 

Yup, but the guy is already using FFR. No need for fixed QVFR (which is imo worse in this scenario: rectangle shape is more disturbing than 3 rings).

 

Just has a glorious Day Night cycle race around Le-Mans running QV.

A-MAZE-ING!

Shame 70% of the field ran out of fuel though.

 

I'm sorry I thought I read : "Pico Neo3 Link. No eye tracking - QVFR is not for your headset then."
Which is incorrect.

What were your QV settings ? Try something more agressive (outer res 10% and Foveated area size of 20%) to see if you really get no gains. Than you can dial it back down to your preference

 

I even had worse performance(I couldn't keep 90fps locked, no matter what the setting). After a discussion with the dev I found out that it's because of the CPU. I have the i14700k, you the i9 14900K. That's the issue, these CPU's are the limitation while using QV with the current implementation.

But there's good hope for us, the developer is now working on implementing Multi-View Rendering (MVR), "It allows a game to render the scene once and generate two images from different viewpoints. With QuadViews AMS2 normally renders each eye twice, but MVR allows it to do both at the same time reducing CPU workload." according to the dev. If this won't fix it, then we'll have to upgrade the CPU to see the benefits of QuadViews.

 

Yeah I seen the CPU spikes last night. I've removed it now. It wasn't really worth it for me as it made a lot of things get jittery , flickering textures etc and the only benefit it brought was DLAA.

I tried a few different settings with custom sizes etc. Looking forwards onto the track made the dials look like my lenses were smudged.
I've got little interest in perusing it further as my headset already looks about as sharp as I can get it. Even running AMS2 at 7000x per eye resolution the difference is barely noticeable apart from the sharpness of the distant tree leaf textures.
The DLAA was nice, the FFR part wasn't worth it.

 

I hope MVR brings up the improvement you need. In LMU, it was a nice difference:

• Sim-QVFR without MVR is a modest gain over Dan’s mod on frame time. The big change is VRAM, which drops by about 36%.
• MVR is the main gain. It cuts a further 13% off GPU time and 18% off CPU time, and it helps the worst frames most. The 95th percentile CPU time falls from 10.3 to 7.6 ms.
• The 13% GPU gain is the right size for MVR. Two of the four passes skip the scene, so the engine doesn’t save a full half, and the lens-mask and glare passes are still done four times.
• The gap holds throughout the run. It is about 20% on GPU in the first minute and about 17% in the last, so it isn’t just the cars spreading out.

 

It’s now available, including a fix for the trees with DLAA

https://github.com/hypeapps/ams2-qvfr/releases/tag/v0.5.0

Which headset out of interest?

Edit - I see MeganeX above, I guess bit of a shame there is no eye tracking. New mod still might be worth trying for the DLAA with fixes… you’d just have to run with larger box or higher periphery to make the box less visible

 

I'll give it a go, probably set the full scale render area close to around 90% though and just use the DLAA.

 

I imagine something around 70-80% and a modest reduction in peripheral to around 50% or something should be pretty invisible. Reduce the feather margin significantly, probably only need 5-10% at most with that sort of size.

you can also round the corners of the foveated box which may make it a more natural fit for the lens sweet spot shape

I also imagine the mod can apply DLAA without the MVR/QVFR or at least could easily be made to.

 

edit:
Ditched DLAA and all the problems went away. Still can't run without judders in 90hz mode. But can run MSAA high with all the cars in 75hz mode. Image is a bit softer than without.

 

v0.5 working excellently om my i13900 / 5090 / Dream Air combo

Its pretty much AMS3 now

 

Yeah no joke. Everything on max settings, 204% on steam, 130% in QV window and frametimes generally around 6-7ms with DLAA (more like 8ms with preset M).

it’s great… need to have a play with more stuff like night/rain etc next.

 

This is incredible stuff. Crying in the corner it does not work with beta.

 

Do you run 72hz?

For me it's impossible to get 90fps/hz locked in all scenario's as I was used to have with my i14700k, Dream Air, 5090.

The CPU frametime is between 8 and 13.5ms with 90hz, everything above 10ms causes framedrops.

Without QV I always have 90fps/hz locked(but I cannot run such high settings).

I can see the benefit of the QV mod, with insanely good visuals (8xMSAA+ 204% sboys res), the gpu only uses ~50% and I still got 75-90fps. This while without the mod and 4xMSAA / 170%, I have 90+% gpu usage. But I simply cannot get it stable at 90 with the mod, so it's not usable with my CPU...

So unfortunate, it feels SO close, but it simply seem to work better with the AMD equivalent.