David Mills

First, please note that you changed the settings in your Nvidia Control Panel for all of your programs when you changed Global Settings. Instead, you should use the tab for Program Settings, then select Microsoft Flight Simulator as the program to be affected by your changes. What works for one program may not work for all -- which is what you're doing when altering Global Setting. Personally, I keep my Nvidia Control Panel -- and the Microsoft Flight Simulator tab settings -- to default, except for enabling VSYNC. Currently VSYNC does not work under DX12 when you enable VSYNC from the in-sim graphics options. You must enable VSYNC externally through the Nvidia Control Panel. I too use TAA along with Frame Doubling.

@Noel Could you possibly post a video of your current issues and point them out? I think that would help clarify things a lot. I hate it that you spent all that money and aren't enjoying good results.

@Noel. Are you trying to use your excellent frame-time-stability tweak with your new 4090 and FG? We're not talking about flickering in VR, are we? The vast majority of 4090 users don't seem to suffer the issues you describe with FG. It's definitely a stretch to accuse those happy with FG of a cabal to hush up FG artifacting. My system -- which is built with completely-off-the-shelf parts by Jetline Systems -- handles FG perfectly. There is no artifacting whatever. (There used to be, however, before recent sim updates.) You know that in-sim VSYNC doesn't work with DX12 and FG enabled. You know that GSYNC only works properly with FG using a DP connector. What brand of 4090 do you own? There is something, somewhere, hardware or software, causing these problems for you. Other simmers, as you've shown, suffer these problems as well. What is the commonality of those experiencing these issues? But most users don't suffer these problems. Instead of throwing in the towel, you need to continue teching this out -- as you've done so impressively in the past -- to isolate the problem. FG is not fundamentally and inherently flawed as you appear to imply. Something else is causing your issues.

Thanks to @Beagle12 for asking the question and @hansb57 for providing the answer. I've long wondered myself about getting rid of that yellow label. Thank you both!

Then he needs to update his publicly-visible system specs, which list his current GPU as an RTX 3080 Ti FE.

You guys need to make clear that you're not talking about built-in Frame Generation for Nvidia 4000 series cards. You're talking about a software patch that attempts to reproduce such frame generation without owning the necessary hardware. Far from FG being a "colossal fail," FG on the Nvidia 4000 series cards is the most glorious invention since the Big Bang dawn of the cosmos. It produces none of the graphics aberrations you mention when properly tuned and used with TAA anti-aliasing.

There used to be a rule when calibrating your color scheme for a video shoot. Point the camera to a white object -- usually a white sheet of paper, then lock the White Balance button on your camera. The theory was that, if you get white accurate, the rest of the colors in the scene will be accurate as well. Whether this past video procedure has any relevance to colors in MSFS, I don't know. Someone comment ...