Since SU5 I have the new shimmering /anti aliasing issues in menus and distant trees/buildings, particularly towards a low sun, and as described in multiple threads. However I wanted to ask about something that is not new in SU5 but maybe could be addressed if they are visiting the AA anyway to fix the above:
With TAA on, I have always had a “soft” image, particularly with objects that are more than say a meter away. I actually get the sharpest/clearest possible view of the cockpit by DISABLING AA entirely, but at the cost of horrific shimmering on external scenery (note this has always been the case and is much more severe than the new shimmering with TAA post SU5). To this extent if I fly an airliner IFR in zero visibility, I sometimes disable AA entirely to get the best possible view of the instruments.
With my setup of quest2 at full resolution, a specific example of the difference is in the a320 at default camera/headset position, the auto thrust button and anything further away becomes slightly blurry with TAA enabled. However with AA disabled, I can clearly see the lettering and note that the light on the auto thrust button comprises of 3 individual green strips, a detail difficult/impossible to see with TAA enabled.
My questions are
1- I assume that this is the same for everyone else and not a quirk of my setup?
2 - Is any expert (cough@CptLucky8 ) able to say whether this effect is an inevitable consequence (/feature?) of AA, or is it a long standing bug of some kind that we should request to have investigated?
To me, the 2 main culprits to legibility (render vs display resolution apart) are:
Bloom, affecting not only ground details but also integral lighting (the “lettering” you’re talking about)
Motion smoothing, inherently based on interpolating pixels and therefore in further sampling already sampled pixels.
This is why I’m also using 152% SS with the Index with good results, because it strikes a usable balance between motion smoothing processing power, and enough pixels to motion smooth with.
Yesterday though I’ve tried changing just a few settings to give some leeway and I’ve disabled motion smoothing to try it out. With the FBW A320 I was able to push the 9700K+2070S to 45fps in VR (well I’ve set fixed rate 45 but it might have skipped some from time to time, I didn’t use any graph to cross-check, just my visual impression).
Thanks for the reply, I should have mentioned I’m not running any ASW/smoothing and have bloom turned off.
I just find it so strange how there is so much shimmering in scenery with AA off, it’s like nothing I have experienced in other games. This shimmering is removed with TAA (albeit only partially since SU5) but at the cost of adding softness/blur which hampers the cockpit view compared to AA off. I wish this weird scenery shimmer didn’t exist in the first place and I would probably just run with no AA for maximum cockpit readability
I have not had time to look for long but I am not currently seeing a clear difference with Sharpening on or off… My layman’s gut feel is that it is actually locked to on for me in VR regardless of what is set in the UserCfg - Could this be the case and if so potentially the reason that there is shimmering on scenery even at native resolution with no AA?
I was on all defaults (Like you I spoted an issue with the AF on the release of SU5. Like you I resolved it by reverting the Nvidia CP to defaults. Unlike you I didn’t identify that this is what resolved the issue, and therefore wasn’t able to share this advice ) Fiddling with those two settings now, I don’t see an obvious difference on the aliasing/sharpness.
Thank you - I have voted on your linked bug topic and wishlist items.
However for me as mentioned it feels like there is far too much sharpening, which I am unable to turn off, and contributes to severe shimmering (TAA off) or occasional shimmering and constant slight blurriness (TAA on) even at native resolution.
I will hold off on a zendesk report as this is not a new issue and I don’t want to add any further to their plate, at least until the painful SU5 building+tree pop in issue is resolved!
One more reason to give users an adjustable UI setting for sharpening!
This shouldn’t too hard: if they are using the AMD CAS Shader, “sharpen” strength is a parameter you can adjust and already provisioned for in the shader code source.
I voted as I dream about the sharpen strengh be accessible to us. It’s already the case in different apps like Automibilista 2, through changing float value in a cg file, or Star Wars Squadrons directly through the GUI. In both case I was able to achieve the same result as a supersampling of 150% to 200%, without nearly any fps loss. So kind of magic IMHO for VR users.
For anyone else reading this, here is the mentioned wishlist item for more control of the effects in VR. Please do vote for this as well as the sharpening Bug report if these issues affect you !
I have experienced identical results. Very pleasing and legible cockpit instruments, combined with terrible shimmering of trees etc out the window. Will try turning sharpening off in the config file and see if that helps.
Agree with the original formulation, this is either a bug in the way Asobo apply anti-aliasing in the VR cockpit, or in how it interacts with the Quest 2.
) able to say whether this effect is an inevitable consequence (/feature?) of AA, or is it a long standing bug of some kind that we should request to have investigated?