3 hours ago, Pathfinder633 said:

Makes no sense, why not just call it gamma correction period? (as it used to be called), its not as if anyone turns of AA so its basically applied to everything anyway.

 

Because that would be incorrect. The setting, when on, makes gamma adjustments to the pixels around the edges of assets, where AA is applied, not the whole image.

10 hours ago, March Hare said:

Because that would be incorrect. The setting, when on, makes gamma adjustments to the pixels around the edges of assets, where AA is applied, not the whole image.

While I agree with what you are saying, if AA is on, isn't it applying it to the whole image or screen anyway?  Not just individual objects? 

In other words, I cant see how it can pick and choose objects to AA, I thought it just did the whole screen anyway.

1 hour ago, bobcat999 said:

While I agree with what you are saying, if AA is on, isn't it applying it to the whole image or screen anyway?  Not just individual objects? 

In other words, I cant see how it can pick and choose objects to AA, I thought it just did the whole screen anyway.

Well, there are many types of AA technique, but usually the GPU is detecting the edges of objects and applying the AA effect there. Full-screen spatial types of AA process the entire image and apply extra coloured pixels by supersampling, then downsampling and retaining some of the extra pixels created in the process, usually resulting in unwanted blurriness of the whole image, so it isn't generally used now in that sense. Although some AA techniques still use spatial processing to an extent (and some only detect and apply AA to edges), they are also detecting the edges of polygonal and other objects and applying AA only to those edges. This is all simplifying and generalising, of course. The point being, though, that the GPU isn't normally throwing a bunch of pixels everywhere across the entire screen; the GPU does intelligently detect edges of assets and applies AA to the edges where "jaggies" are likely to show up. The NVIDIA AA gamma correction setting (to my knowledge) only applies gamma correction to the pixels round the edges of objects that have been altered by the AA technique, not every pixel on the screen.

Edited October 13, 20214 yr by March Hare

Hello, cure for pixelated or grainy clouds, anyone test? 

Edited October 13, 20214 yr by spitzer45

I have a hard time believing that turning off that feature would cause CTD.

26 minutes ago, Ixoye said:

I have a hard time believing that turning off that feature would cause CTD.

Same, tbh.

27 minutes ago, Ixoye said:

I have a hard time believing that turning off that feature would cause CTD.

Exactly.  There are so many other CTD's going on, it would be difficult to pin it down to gamma correction.  

1 hour ago, spitzer45 said:

Hello, cure for pixelated or grainy clouds, anyone test? 

No, but setting Texture Filtering - Negative LOD bias to CLAMP helps.  Looking forward to the touted 'impressive' update to weather mentioned by Asobo, but not sure when that is.  Right now clouds need a lot of work!

1 hour ago, Noel said:

No, but setting Texture Filtering - Negative LOD bias to CLAMP helps.  Looking forward to the touted 'impressive' update to weather mentioned by Asobo, but not sure when that is.  Right now clouds need a lot of work!

Woh.  Changing that setting is a huge improvement.

24 minutes ago, Gregg_Seipp said:

Woh.  Changing that setting is a huge improvement.

So, clamp it? 

8 minutes ago, Ianrivaldosmith said:

So, clamp it? 

Yes.  

 

5 hours ago, Noel said:

No, but setting Texture Filtering - Negative LOD bias to CLAMP helps.  Looking forward to the touted 'impressive' update to weather mentioned by Asobo, but not sure when that is.  Right now clouds need a lot of work!

I've always had it set to clamp globally, for all games. That's always appeared to be the ideal setting.

Also, agreed, setting AA gamma correction off would not cause a CTD, as it's not doing anything and MSFS certainly doesn't require it to be on for any reason.

On 10/12/2021 at 2:09 PM, ryanbatcund said:

I also had a CTD in the CJ4 with this setting OFF.  I flew the same route to verify with it ON (as it was) and no issues.  Not sure why it would cause a CTD but it did for me.

I had the same CTD with the CJ4 first flight after I turned this off . Strange !

Setting Clamp for me affected performance negatively for me - I did see some visual improvements in the clouds but was not worth the stutters....must be my mid range setup.   Back to Allow for me.

Edited October 14, 20214 yr by marcg11

I wish someone could write a comprehensive article on what all these graphics settings do. 

There is also so much conflicting information from 'experts' - such as Windows Hardware Accelerated GPU Scheduling (HAGS) on or off, threaded optimisation on or off, CPU Hyperthreading on or off in the bios etc.  I like Flight Simulator blog and their graphics optimisation notes, but I can't even agree with everything they say on there.  The sim runs better with hyperthreading for me personally, and they say turn it off for some reason.

Some input from MS / Asobo also would be valuable on what settings they use (generically - not taking different PC performance levels into account).

Asobo work hard to get us performance gains, but a few words about how Nvidia Control Panel settings influence the sim and the performance and graphics quality, could probably influence performance just as much. 

Although, I don't even know if they have realised their terrain detail level slider wasn't working properly yet.  I haven't seen it mentioned.  Fixed for SU6 do you think? 

Edited October 14, 20214 yr by bobcat999