I've been perplexed at why it is I seem to be one of very few who find artifacts associated with hardware based Nvidia DLSS Frame Generation usually much too severe to ignore so 90% of the time I have FG turned off, which of course is unfortunate at best.  Oddly, and this seems mostly to do with time-of-day lighting (dawn/dusk seems worse), sometimes these aberrations are modest enough to use FG so I do.  For me these artifacts happen with any kind of motion including the plane rolling or panning the cockpit and include:

• Flickering/strobing when looking at tarmac, typically out the side window of the airliners I fly.
• Shimmer/flicker of certain elements in glass cockpits, or for example characters in the PMDG 738 FMC, when panning.

Fortunately I can almost always maintain a minimum native rate of 40fps but the bad part is not able to set native at 30fps and get all of that headroom.  Again, just trying to get a feel for why I seem to be in what seems to be a party of very few with this issue.  I also have two screens at play and discovered this is not the issue, though it has known issues when FG is enabled for the main screen.

Edited April 23, 20242 yr by Noel

FG on, DLSS on quality, 4K native -> Off we go. No problems. 4080/12900K/32GB

If MSFS runs with FG has to be on DX12, it is in beta! I believe it would be a good idea to raise the issue with ASOBO and make sure it is fixed properly. Despite what some may claim, there are instances of CTDs and other issues related to the unfinished DX12 in this software. Another potential cause for these issues could be an improperly overclocked CPU and GPU.

What is an artifact?  I have a 4080 and don't really see anything unusual.

Honestly no problems. Loving DX12, FG and DLSS 3,6, Ultra Quality at 0,80 on my 4K display. Not on Beta either.

Honestly, seen nothing that bothers me. Only thing I really see is a hiccup when I click something on my other monitor and back, as it syncs up.

32 minutes ago, LRBS said:

If MSFS runs with FG has to be on DX12, it is in beta! I believe it would be a good idea to raise the issue with ASOBO and make sure it is fixed properly. Despite what some may claim, there are instances of CTDs and other issues related to the unfinished DX12 in this software. Another potential cause for these issues could be an improperly overclocked CPU and GPU.

DX12 in beta has nothing to do with it though.  Artifacts are just a consequence of using FG at lower frame rates.  I have seen them in titles such as Cyber Punk for example when panning the screen quickly. 

Better drivers and versions of DLSS3 might reduce it in future, but it has got nothing to do with a fault in DX12.

I do agree Asobo need to fix up DX12 and the sims interaction with it, as we still have a few other issues such as tile bleed, and the really poor water reflections from the cockpit when next to the structure of the aircraft, such as the window frames.  Also, although the sim can run in DX12, there is next to no actual optimisation for it.  Other titles show much bigger performance gains in DX12.

Asus PG279Q display (2560x1440) @100Hz Gsync fullscreen, Dynamic Super Resolution 3840x2160 on desktop (200% scale for my old eyes) and in MSFS, DLSS 3.7, Nvidia 4090, 13900KS CPU

Absolutely stutterfree experience without shimmering using TrackIR panning since I read this article and changed my settings.

Great idea with the poll Noel. The only FG-related artifacts I see is the ones caused by incorrectly rendered AI frames. I notice this very rarely, even when scrutinizing my own YT videos. Last time I saw it was on fast moving numbers on the dev mode overlay: 

Apart from that, FG works great, as long as the native FPS is high enough (30-35). 

Edited April 23, 20242 yr by Cpt_Piett

1 hour ago, Noel said:

I've been perplexed at why it is I seem to be one of very few who find artifacts associated with hardware based Nvidia DLSS Frame Generation usually much too severe to ignore so 90% of the time I have FG turned off, which of course is unfortunate at best.  Oddly, and this seems mostly to do with time-of-day lighting (dawn/dusk seems worse), sometimes these aberrations are modest enough to use FG so I do.  For me these artifacts happen with any kind of motion including the plane rolling or panning the cockpit and include:

• Flickering/strobing when looking at tarmac, typically out the side window of the airliners I fly.
• Shimmer/flicker of certain elements in glass cockpits, or for example characters in the PMDG 738 FMC, when panning.

Fortunately I can almost always maintain a minimum native rate of 40fps but the bad part is not able to set native at 30fps and get all of that headroom.  Again, just trying to get a feel for why I seem to be in what seems to be a party of very few with this issue.  I also have two screens at play and discovered this is not the issue, though it has known issues when FG is enabled for the main screen.

I don't understand why you are still perplexed. Several weeks ago you posted on this forum that you'd determined your old CPU was not capable of keeping up with the new GPU you'd just installed. Your explanation for the graphics problems made perfect sense. You further speculated that others here had purchased entirely new machines -- with state-of-the-art CPUs and GPUs correctly matched from the start -- and that they therefore didn't experience the graphic artifacts you suffered with your current mismatch of CPU and GPU. I don't understand, now, why you are once again befuddled. You already correctly diagnosed the problem and solution (upgrading your CPU). 

43 minutes ago, bobcat999 said:

DX12 in beta has nothing to do with it though.  Artifacts are just a consequence of using FG at lower frame rates.  

Better drivers and versions of DLSS3 might reduce it in future, but it has got nothing to do with a fault in DX12.

 Other titles show much bigger performance gains in DX12.

I am afraid that there might be a misunderstanding. What I meant was that FG is only supported in DX12. Additionally, I agree that it's possible for artifacts to appear during frame generation when using DX12, especially at lower frame rates. Even if we have the latest drivers and versions of DLSS3, it won't make a difference if the software isn't optimized correctly for DX12.

6 minutes ago, LRBS said:

I am afraid that there might be a misunderstanding. What I meant was that FG is only supported in DX12. Additionally, I agree that it's possible for artifacts to appear during frame generation when using DX12, especially at lower frame rates. Even if we have the latest drivers and versions of DLSS3, it won't make a difference if the software isn't optimized correctly for DX12.

I see.  Yes I agree.

3 hours ago, David Mills said:

I don't understand, now, why you are once again befuddled. You already correctly diagnosed the problem and solution (upgrading your CPU).

You are the guy that was sure to note I hadn't updated my sig when I made the original post some time ago, that some believed the post title might be about the FG mod, not Nv hardware-based FG, since I had already installed RTX4090.  I updated my sig a few weeks ago when I installed the new CPU, take note.  The issues persist, hence as I stated clearly in this post I remain perplexed others aren't having the same issues that obviate the use of FG, most of the time in my situation.  I made the post to find out how common this might be with high end hardware, and if there might be a potential solution.  The first step of this is finding out how much is just that people are sufficiently happy with FG to ignore its artifacts, or if it's possible others aren't seeing this.  I am 1000% certain if anyone sees what I see, they would likely react the same way I have.  Maybe it's my specific display?  That is common to both CPU/motherboards.  I just don't have a clue and wish I did.

Edited April 23, 20242 yr by Noel

4 hours ago, ryanbatc said:

What is an artifact?  I have a 4080 and don't really see anything unusual.

Did you not read what I wrote, or was this not clear enough? 

• Flickering/strobing when looking at tarmac, typically out the side window of the airliners I fly.
• Shimmer/flicker of certain elements in glass cockpits, or for example characters in the PMDG 738 FMC, when panning

These things don't happen w/o FG being ON, and they're anywhere from modest and easy to ignore (rarely) to so distracting I end up killing FG.  I tried once before to video this and maybe I can do it with my iPhone.  Capturing w/ built in video altered what I see live so I will try this once landed in....Bucharest ;o)

 

Edited April 23, 20242 yr by Noel

10 minutes ago, Noel said:

Did you not read what I wrote, or was this not clear enough? 

• Flickering/strobing when looking at tarmac, typically out the side window of the airliners I fly.
• Shimmer/flicker of certain elements in glass cockpits, or for example characters in the PMDG 738 FMC, when panning

These things don't happen w/o FG being ON, and they're anywhere from modest and easy to ignore (rarely) to so distracting I end up killing FG.  I tried once before to video this and maybe I can do it with my iPhone.  Capturing w/ built in video altered what I see live so I will try this once landed in....Bucharest ;o)

 

The only thing I really get is the occasional flicker from my monitor, especially if I tab over to my second non gysnc monitor.  It used to flicker quite badly (the main MSFS monitor) when I tabbed out or the screen focused on the 2nd monitor.  But I think a recent SU along with new nvidia drivers fixed that.

In my experience the artifacts tend to happen when the actual FPS drops and the AI tries to generate the new frame...  if I have like 30+ actual fps, frame gen works very well.  But when I go lower (and I do haha - eye candy!!) I definitely get some flickers here and there.