55 minutes ago, gearsdown said:

I have now tried to turn Vsync off in game as well as in NCP. I then wrote 30 fps as limit in NCP. Too be honest; its not as smooth at all as it was with Vsync in game (off in NCP) and 30 fps in game. Not sure if its NCP's limiter thats the problem. Maybe Rivas solution is the way to go...? I was a bit surprised that all butter smooth feeling (exept for a stutter here and there), suddenly was gone.. cause when I get this right, 30fps will feel buttery too right? =P

RTSS smooths the frame time out, better than the nvidia frame cap. 
 

RTSS is a CPU-level FPS limiter, and introduces up to 1 frame of delay, whereas Nvidia Inspector uses a driver-level FPS limiter, which introduces 2 or more frames of delay

On 2/20/2022 at 1:24 PM, MrBitstFlyer said:

The article states that G-Sync plus V-sync in NVCP will give smooth fps, but you think different - what do you think the flaw is in that article?  I would have thought V-Sync would ensure each frame is timed correctly?

I think you might be conflating g-sync working properly with smoothness although it somewhat depends on your definition of "smooth". I define "smooth" as a combination of two factors: 1) consistent time in between frames, 2) a high enough frame rate to not perceive choppiness. G-sync plus v-sync provides an ideal configuration for delivering tear free frames to the monitor with low latency. G-sync has no direct impact on the smoothness factors I listed. It is best understood as a tool to eliminate tearing without introducing latency. This is important for fast-paced, high-framerate games like first-person shooters, where low latency matters.

Some people are more sensitive to one factor than the other. If you are sensitive to low framerates, you might prefer not to cap the FPS at 30, allowing MSFS to run faster when it can, but you may be more likely to notice slowdowns when the game or GPU can't keep up. For others, a sudden drop in FPS might immersion breaking and very undesirable. These folks might prefer to cap at 30FPS for consistent frametimes. If you prefer a balance you might use an external tool like RTSS to cap at something like 40-50FPS or whatever your hardware can handle.

3 hours ago, gearsdown said:

I have now tried to turn Vsync off in game as well as in NCP. I then wrote 30 fps as limit in NCP. Too be honest; its not as smooth at all as it was with Vsync in game (off in NCP) and 30 fps in game. Not sure if its NCP's limiter thats the problem. Maybe Rivas solution is the way to go...? I was a bit surprised that all butter smooth feeling (exept for a stutter here and there), suddenly was gone.. cause when I get this right, 30fps will feel buttery too right? =P

As Ian says, RTSS is better than the NCP limiter.

If you can only hold 30 fps and above (I don't know your hardware) then the vsync 30 in sim is the way to go.  However, dont forget there is a 'bug' in MSFS, or more accurately the vsync 30 is mislabelled - 30 actually gives you half your monitor refresh rate. So if the monitor refresh rate is 60, it will give you 30, but if the monitor runs at say 72 Hz, 30 in sim will vsync you at 36 Hz.  

Edited March 2, 20224 yr by bobcat999

How come I do get smoother gameplay (good test is spinning the glob in game), when I have Vsync off in NCP and then ON 30fps in in the sim? Ok, its smooth when its smooth, but suddenly there is drops, when the system cant handle the scenario and gfx settings for that trip I guss (maybe exactly what you have been trygin to explain?). 

But ALL vsync off, and then using NCP to limit the fcp (there is only one setting for this, right?) did absolutely not do the trick. Spinning the globe feels not as buttery, but maybe more stable over all. 

If I install Riva tuner, which settings to disble and enable JUST to get benefit of the limiter? (does afterburner need to run in background too?)

Oh...just found that @eltair explained this....I guess. Sorry. 

2 hours ago, gearsdown said:

Oh...just found that @eltair explained this....I guess. Sorry. 

No need for afterburner.  And just select global in RTSS if you cannot find the flightsimulator.exe.  Then select fps from the numbers in the window.  There is another setting below this.  I had it at -1 or zero, it didn't make much difference, but don't have it as a positive number, e.g +1 was no good for me.

If you can only reach about 30 fps with your system, the 30 vsync in sim is still the best way to go (if your monitor is 60 Hz), and will be smoother, as Asobo adjusted how it works last year - better frame timing, so it is very smooth if you can hold 30 fps.  All other fps limitations (in NCP etc.) must be turned off if you do it this way, otherwise it can make it worse.

On the other hand, if you intend to use RTSS, you must leave it open or reduced to the Windows title bar, otherwise it wont work.  Unlike some of the other methods, RTSS stops working as soon as you close it down. This is why selecting global won't affect any other game after you have closed MSFS, because you normally close RTSS after that as well, and then it doesn't affect anything else.

Two main reasons why vsync 30 in sim doesn't work well: -

1.  The hardware cannot hold 30 fps anyway.  If it dips below 30 fps it will still look stuttery.
2.  People accidentally have another program interfering with it by accident.  E.g. 30 in NVC and 30 vsync in sim, is not the way to go.  Make sure all other limiting programs and settings are removed.

Before I upgraded to my 3080Ti, I ran at vsync 30 set in MSFS for months on my old 1080Ti, and it was as smooth as silk. 
There are exceptions of course - if you are moving very quickly over the ground at low level, at 30 fps it will always have steps because the image is moving so quickly across the screen (looking sideways at take off is a good example).

Edited March 2, 20224 yr by bobcat999