Noel

Those are low limits the user has control over within the program. I am blessed to have the horsepower for more traffic but my preference is to keep it light.

Exactly, this is how I'm setup: 12 IFR in a 50km radius, 4 VFR, in FSLTL. This means I see a few aircraft all the time at departure and arrivals, rarely get given go-arounds and it all works quite well. I don't like crowded airports and airways in the RW so why put up with them here 😀

You might, I could care less. The way I use MSFS it's never to see how things might go last month. I will appreciate being able to duplicate weather appropriate for time of day when I fly in areas in other hemispheres so once again zero need to duplicate weather last week or what have you and I suspect that is the case for the vast majority of users. Glad they won't waste programming resources for more than 24h worth.

Well sure, that was why I passed this on to others here perplexed as to what was bothering me with FG. I only just figured this out. And here's the reality for me. I've figured out what it is that contributes to this--it's pretty much any kind of sharpening algorithm including Render Scale (mine's at 150), TAA (versus DLSS or other 'softer' algorithms), and as explained, AMD FidelityFX (at max 200). I'm using all of these hence the issue surfaces. I've become duly spoiled by looking at AMD FX of 200 along w/ RS at 150 and rock-solid image quality everywhere. The degree of clarity, sharpness and so forth from everything from characters in glass cockpits, FMC and so forth, to objects near and farther is unparalleled in my experience. Couple that with the fact I am constantly moving back and forth from main screen to 2nd, and every one of those gets a modest judder when returning to the main screen. Using FG allows me to put the native rate to 30fps and the cost of that is less sharpness, frequent screen judder and a little less 'stability' in glass cockpit/FMC. That latter is very modest and not a show stopper at all now when AMD FX is set at 50 or 70 or what have you. But with all three of these combined the value of FG for me drops enough to avoid using it as my default mode--largely this is because 7800X3D/4090 is able to produce solid frame rates of at least 40 in most settings. And the reality is I don't find a frame rate of 40 or 45 undesirable, at all. Panning is great, as is everything else, in native mode. What this translates to for me is that I'm only going to use FG when I can't maintain a native frame rate of 40 or more, and that can happen in the most complex settings I find myself in. Thanks all for helping me get to the bottom of this, for now. My sense is that this area will continue to be improved with driver revisions, IOW it will only improve.

Agreed--video capture does not show this well likely due to the capture rate and compression algorithms. If you saw what I see on my display live you'd have absolutely zero problem seeing serious artifacts as I've described them,. and by 'serious' my definition is bad enough to where it's simply too distracting, and undesirably unnatural. And I've stated several times these artifacts are very lighting-dependent. If you're curious enough to test it, do this: Set AA method to TAA Set AMD FidelityFX to 200 Back out of gate B45 in say the PMDG 738, and point yourself due east. Load up the Taxi or Runway load setting so your displays turn on and function. Set the time of day to around 1h after sunrise (so the tarmac is nice and bright, and the light is coming in from that low angle). Set weather to clear skies. Now pan or taxi and notice out the left window what the tarmac looks like close to the plane. Here, the flickering/strobing is too much, and the glass cockpit and FMC characters are unstable and vibrate or something when panning. Who knows maybe your system has something that would change this it's always possible. Our systems are otherwise not identical at all including HDR settings, various other factors. I strongly prefer maximum image quality over frame rate and the best possible image quality comes out of the normal rendering pathway, not thru frame interpolation. That being said the current version of NV DLSS FG is very good, and superior to prior versions. My guess is it will continue to evolve in a good way and some day may pass the Turing Test for matching native rendering. In fact it's already mostly there save these aberrations when certain types of sharpening algorithms come into play.

Dunno, but when I was trying various ways to get rid of FG associated aberration I tried DLSS > DLAA and indeed artifacts improved....but then the softer IQ.

By the time you get AMD FX down to 50 most all of this aberration disappears which is why I've been able to complete two flights now w/o getting nasty artifacts. As you know when you turn AMD FX off outright you definitely lose some image quality, so 50 makes sense as a compromise. I became duly spoiled by having AMD FX at 200 enhanced further by render scale at 150 that combination really delivers clarity. So for me whenever I can easily manage to maintain a native rate of 40fps from gate to gate which is the vast majority of the time I'll just continue leaving FG off because there is no downside with leaving AMD FX at 200 when you aren't using FG. For flights that are so demanding no can keep the rate at 40 I will switch to FG on and dial back AMD FX to 50 or 100 as able. We're in a space where compromise is still the order of the day but the choices between options are all quite good! Cheers

I left it at zero. It's certainly made the artifacts I tried to describe improve to the point I can live with them now.

120Hz, native 30fps x 2 = 60fpsFG, RTSS front edge sync, G-Sync I had it at 100 which I think is default then moved it to 200 a good while back as I thought it made image quality sharper and never gave it a 2nd thought. I tried it on and off a couple of times in a couple of scenarios today and clearly 200 make these artifacts worsen. Maybe 100 is okay I will check. I just restarted MSFS and did a quick acid test at KDEN aiming east shortly after sunrise in clear skies in the PMDG 738 and see if it's still good: pretty good flicker out the side but better than w/ AMD FidelityFX at 200! That type of lighting brings it out the most but easy enough to make anything else active and the flicker disappears. For example I can click on my 2nd screen, or any app that can steal the show in front of MSFS will stop the flicker and it's softened enough to where only the worst lighting brings it out, and the glass cockpit and FMC are solid now. It is very nice to put the base rate all the way down to 30 this really gives some headroom and it shows in terms of freedom from even rare stutters. And CPU temps stays nice as well. Cheers

OMG! I am a little hesitant to celebrate because I had this happen once before, one of those rare times when the artifacts described are must less intense. But...I realized when I put RTX4090 into the box I failed to change a setting in MSFS that I had been using forever: AMD FidelityFX Sharpening. I had it set on 200! I set it to 0, and voila, much improved artifacts! Not outright gone, but I can now honestly vote in this survey option #1: Yes, I experience some artifacts but never find them bad enough to avoid using FG outright. Sorry to drag others into this I just failed to realize it could be an issue because it wasn't with the 3080Ti for the past years and it really was not on my radar, obviously. Anyway, having a lovely fly from EHAM > LFLL and enjoying the solid 60fps and nary an artifact the entire flight, including in the glass cockpit and FMC. It is now very close to native. As a side note I installed DLSS 3.7 but that had no effect on artifacts.

I def get the 2nd screen issue but there is no way around that for FG users and I don't mind it though it's certainly a complete non-issue w/o FG. My base native rate also when FG is on is 30 x 2 = 60. Believe me, I would happily keep it there if it weren't for these artifacts. And as said, sometimes it's fine but almost always it's not. And here is another oddity: if I click on the 2nd screen all FG artifacts on the main screen disappear until I click back on the main screen, despite the frame rate dropping from 60 to around 44 or so. In fact I've done this just to get away from the artifacts just kept on the 2nd screen as long as able before going back to click something in the cockpit. This behavior should give a clue about something, the fact I can click screen two and the artifacts disappear. Hopefully with this post someone might have a clue where to look.

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)

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.

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'm seeing something similar: sometimes when the plane first loads to the departure airport turning on battery and external power does nothing, and from there it's hosed near as I can tell. What's more is Self Loading Cargo believes its hot and engines are running when it's ice cold and nothing is running! When this happens I have to reboot and start all over and pray...and I'm using the Stable version currently.