21 minutes ago, virtualstuff said:

looks almost ghosting effect from FG...

Suspect when you change FG of it's ok

Easy to test just disable FG from the menu graphics MSFS and test

Which AA and DLSS setting do you use?

With FG off it's perfect..I am using TAA and upscaling as well.

12 minutes ago, iFlySimX said:

With FG off it's perfect..I am using TAA and upscaling as well.

You could try DLSS with DLAA  (DLAA has far less artifacts as TAA)
see this topic also:

FG has still some artifacts unfortunately, you could try with setting F to minimize the effect. Based on those settings to see if  it's acceptable for your personal preference local... 
See the above topic for relevant and useful information...

Edited April 9, 20242 yr by virtualstuff

I learned here in forum to remap all custom views to the number pad. So I setup zoomed in PFD on num 8 and reset default view on num 7. Asobo A320 neo. Punching those 2 keys right after one another the PFD closeup pops in and out of view. Absolutely no momentary jitter after changing views. Tried with FG on and FG off. No difference. None at all. Except fps displayed in bottom corner with Steam fps display was 55 with FG on and 27 with FG off. I can't see a single thing different except the tiny FPS number.

EDIT: I'm using DLSS Quality instead of TAA or DLAA.

Edited April 9, 20242 yr by Fielder

OP might try using Asobo A320 instead of the Fenix which is a performance laggard.

11 minutes ago, Fielder said:

I learned here in forum to remap all custom views to the number pad. So I setup zoomed in PFD on num 8 and reset default view on num 7. Asobo A320 neo. Punching those 2 keys right after one another the PFD closeup pops in and out of view. Absolutely no momentary jitter after changing views. Tried with FG on and FG off. No difference. None at all. Except fps displayed in bottom corner with Steam fps display was 55 with FG on and 27 with FG off. I can't see a single thing different except the tiny FPS number.

EDIT: I'm using DLSS Quality instead of TAA or DLAA.

Great tip I have also custom views setup (0 to 9) in combination with TrackIR which have movement... Personally I´m using DLAA far better output here local....

We used this method already in the alpha build back in 2019 😎
DX12 and FG in general have still a long way to go, I'm curious about 2024.
But FG is regarding performance still a huge leap forward.

Edited April 9, 20242 yr by virtualstuff

I  can see in your video after clicking full screen icon the  jiggle when the view changes  to the PFD. That's what I don't see here in my MSFS. The jiggle. It just doesn't happen.

On a 120hz Oled gsync I still get tearing in MSFS, and Gsync has a massive issue with Oled in that it flickers the screen in dark areas, it's a known problem and no solution really so I turn gsync off to avoid that flicker.   Most games have a high enough fps I don't notice tearing but in MSFS I do get tearing no matter what settings I use, hell even with async it tears and has that jittery feeling indeed when panning.

If you don't have an oled gsync may do the trick for you but for me it just seems to be ignored all together, I think it's related to framegen/dx12 maybe?  As the screen menu itself no longer shows gsync as on when I boot msfs even when enabled in NCP.

This is my solution for a stable FPS and no tearing; I limit msfs to 90FPS in the Nvidia CP and turn on vsync there only, no vsync
 in msfs.  I am using Dx12, quality DLSS and Framegen though so no gsync.   In any case that works for me so far, so hopefully that helps someone with a similar setup.

 

For some reason, V-sync settings in the sim options do nothing: fps still merrily fly way above the refresh rate limit. But NCP frame limit works perfectly. So, I just use that.

5 hours ago, Fielder said:

For some reason, V-sync settings in the sim options do nothing: fps still merrily fly way above the refresh rate limit. But NCP frame limit works perfectly. So, I just use that.

It's worth noting that frame limiting is not the same thing as v-sync. You can still get tearing with frame limiting. V-sync buffers the last frame and won't replace it until the monitor has grabbed it.

If anyone else is experience ghosting/jitters with FG, please vote here: https://forums.flightsimulator.com/t/frame-gen-jitters-ghosting/637612

Edited April 11, 20242 yr by iFlySimX