So I have a new graphics card the 4080, and my old one was a 3070. What can I say but a huge difference with the card. Now the question I have is turn frame generation on or keep it off. The reason I ask this is with frame generation on I get really fluid smooth motion, no doubt about it. I have a 60 MHz monitor and I lock my frames at 60. I also have G-Sync enabled and the monitor is G-Sync compatible. Taxing around is very smooth looking through the cockpit left and right is super smooth however I do get what I call skips in scenery when taxing and turning left or right. It's not quite stuttering cuz my frames are still around 55 to 60, but it's more like a little skip. 

Next I tried frame generation off, yes my frames aren't crazy high but I managed to lock my frames now at 30. Of course it's not a smooth and fluid like 60 however I seem to have more smoothness when turning on taxiways and dont see "skips"  in scenery. I'll still get a fluctuation of 27 then jumps immediately back to 30 landing during a takeoff roll.

Just want to know what people think of frame generation on, compared to off for those that have 4000 series cards. Don't know if it's a Microsoft thing, and Im also testing out having cache on or off for scenery.  Hope I made sense of what I'm saying. 

Basically I get less skips with frame gen off and locked at 30 than with frame gen on and higher frames. Now if I turn on frame generation and try to lock 30 frames it's really choppy. 

Always have it on, never have frame skips or any adverse effects from it either. Looks amazing at 4K/120.

Edited August 31, 20232 yr by kiwikat

I have 120 hz oled tv, when i have 60+ fps with fg on, g syn is not working properly, some tears etc.(with fg on I have 120+ fps), but when I have 60- fps(with fg on I have 120- fps) it is working smoothly. 

Edited August 31, 20232 yr by spitzer45

Have it off. When on things get weird when panning sideways and locking frames don't seem to work either. I don't need 75 fps just want frames to not go too much below 30 when at big airports with FSLTL at 100%.

 

FG is just a artificial way of doubling fps, so if you have stutters without you will have stutters with FG. Hence why Nvidia and Amd (FSR3.0) advice  you need to have at least fluid 60 fps before FG. 

Here I have it on on both MSFS pc’s and fps Unlimited.  4089 + 4099 icw SonybBravia 4K TV’s running at 60 hertz.
When capping the framerate ( with or without Vsync ) I get jitters and small stutters when accelerating down the rw or when making turns and looking to the Left.

Vsync On + 30 fps is smooth in the air but not entirely on the ground with a lot of details 

1 minute ago, pilotter said:

so if you have stutters without you will have stutters with FG. 

While technically true, in combination with a G-sync monitor, most stutters are still eliminated with FG on. Of course, you do not get rid off the stutters due to CPU spikes, they remain. Nevertheless, the experience on heavy airports with AI traffic and native FPS around 25 is greatly improved using FG, at least this is my personal feeling...

2 minutes ago, AnkH said:

While technically true, in combination with a G-sync monitor, most stutters are still eliminated with FG on. Of course, you do not get rid off the stutters due to CPU spikes, they remain. Nevertheless, the experience on heavy airports with AI traffic and native FPS around 25 is greatly improved using FG, at least this is my personal feeling...

yep, everyone is positive, but I still have to see hopefully with FSR3.0 in the near future. Lots of Youtube video's showing excellent results with FG, so I have high hopes.

25 minutes ago, pilotter said:

yep, everyone is positive, but I still have to see hopefully with FSR3.0 in the near future. Lots of Youtube video's showing excellent results with FG, so I have high hopes.

BTW: you have a 9 too much in your signature 😉 

Turn it on. I can’t stand less than 60FPS. I’ll take the occasional dropped frame or stutter over having to live with 30FPS constantly.

Key settings to check:

• Make sure you have G-Sync enabled for both full screen and windowed mode - critical if you ever have a pop-out or other window up
• Enable V-Sync in Nvidia Control Panel (this with Reflex/DX12/FG (below) will cap your FPS at a few below your max refresh rate automatically)
• Turn off any and all frame limiters (Nvidia, game, etc) - not needed 
• Disable V-Sync in game
• Enable DX12, Frame Generation, Reflex Low Latency (they’re all interrelated)
• Try using DLSS for anti-aliasing vs TAA. DLSS can provide sharper details at a distance while TAA can lose these details completely, but DLSS may be slightly less sharp on instruments. 

Edited August 31, 20232 yr by Virtual-Chris

1 hour ago, pilotter said:

FG is just an artificial way of doubling fps, so if you have stutters without you will have stutters with FG. Hence why Nvidia and Amd (FSR3.0) advice  you need to have at least fluid 60 fps before FG. 

Please take a moment to understand why they recommend this so you can understand why it’s not relevant to MSFS. The reason they caution against using FG in low FPS situations is because in most games, there’s a lot of motion between frames when FPS is low, and less motion between frames when FPS is high… think about a racing game or first person shooters. It’s obviously harder to generate a frame when there’s so much motion between frames that it makes predictions difficult, even for AI. So at low FPS, it becomes harder to generate an accurate compelling frame in high motion situations. Flight Simulators are generally not high motion. In fact, just the opposite. So unless you’re fling an F16 or something low to the ground, you’re not going to have any issues with FG at low FPS in MSFS. 

Edited August 31, 20232 yr by Virtual-Chris

I have 144hz at 1440p.  Also run a 4080 (I'm still regretting not getting a 4090). That veins said in 2D I'm still cpu limited most of the time.  I run FG enabled at all times.  Downsides of that in turn are running DX12 - it is a large consumer of vram..

With heavy payware like inibuilds JFK, default Longitude, heavy clouds and FSLTL traffic I definitely get the flickering screen from time to time.  Even with my gysnc monitor.  It's flickering because I'm not able to get the best fps in that demanding scenario.  But I'd say 90% of my flying is in more regional or rural areas so I do get the triple digits and it's super smooth.  And the difference between 30 or 60 and 120 is noticeable...  120 or 143 fps is butter smooth...liquid honestly...hard to explain.

I have turn it off, I get 60+ fps without it and see no gains to run at higher frames, it is a bit smoother in panning with DLSS, but then I get blurry panels, and DX12 will eat up all my available VRAM at many 3d party airports, I'm not convinced 16 GB VRAM will be enough either, especial at 4k.

Edited August 31, 20232 yr by Ixoye

Hi,

I have it turned on and it allows me to run three 75" monitors at 4K while also running an additional four monitors for my glass screens. With it off I'm limited to 2K on my external views.

 

I made this video just last night to talk about my experience upgrading to a 7800X3D + 4090, I talk a little about FG on and off and also share my settings.  

Personally for me, flying into the big hubs at 4k its a must if you are looking for greater than 30FPS.