6 hours ago, Dirk98 said:

Bert, I don't get this. Ok, you can limit your fps in NCP to, say, 29 or 30 frames, vsync off, but your monitor is still at 60Hz. I understand therefore they are not synchronized yet them your game and your monitor. See if adding Vertical sync Adaptive (half refresh rate) in NCP draws an even better result.

Vsync is only required if there is screen tearing.. it does not improve performance, as best I know..

VSync in P3D holds the current frame for the time period of one monitor refresh, keeping the most recent incoming frame until refresh. VSync=Off shows the incoming frame at the monitor refresh time even if incomplete, up to the refresh frequency, excess frames are ignored. With VSync = On the next incoming frame must be completed or else the current frame continues to display. So when we choose half of the monitor refresh, the frame is displayed twice. Matching the frame rate to the refresh frequency or a division, keeps tighter coincidence example for 60Hz would be 30, 20, 15. When the frame rate output is a tiny bit less, limited at say 29.5 there's less time to wait for the next frame. Limiting at 30.5 and VSync would lose early frames continuing the display of the current frame so that the buffer is complete by the next time.

25 minutes ago, Bert Pieke said:

Vsync is only required if there is screen tearing.. it does not improve performance, as best I know..

I was thinking about fluidity only, not performance. Even light tremor around the target FPS as Steve wrote above can cause light stutters and I saw them. I was never too happy with P3D Vsync On + NCP monitor refresh at 30Hz therefore by the way. Even RTSS worked better. Now I just leave NCP at 30Hz monitor, P3D Vsync Off, and 29 FPS cap in NCP set. 

9 minutes ago, SteveW said:

So when we choose half of the monitor refresh, the frame is displayed twice. Matching the frame rate to the refresh frequency or a division, keeps tighter coincidence example for 60Hz would be 30, 20, 15.

My suggestion to Bert was to try setting 29 FPS in NCP, Half monitor refresh (of his 60Hz monitor) and P3D Vsync Off.

5 minutes ago, Dirk98 said:

My suggestion to Bert was to try setting 29 FPS in NCP, Half monitor refresh (of his 60Hz monitor) and P3D Vsync Off.

The better option for me Was 30.5 in Nvidia inspector as setting it at 29 would cause micro stutters.

 

9 minutes ago, Dirk98 said:

My suggestion to Bert was to try setting 29 FPS in NCP, Half monitor refresh (of his 60Hz monitor) and P3D Vsync Off.

The better option for me Was 30.5 in Nvidia inspector as setting it at 29 would cause micro stutters.

And also what’s with 4.5 and panning in aircraft and scenery loading stutter/pause?

 

 

3 minutes ago, mikeymike said:

The better option for me Was 30.5 in Nvidia inspector as setting it at 29 would cause micro stutters.

 

We do not take 29.5 and 30.5 literally:

Say your monitor is nearer 61 Hz then you might need 30.5 rather than 29.5.

 

...on a 59Hz monitor you might need 29.

here with a 20fps example, whereby the monitor measured nearer 60Hz:

 

 

Edited February 19, 20206 yr by SteveW

..the upshot is that the setting should be crept up to the best frequency rather than making a blanket value for 30.5 or 21.

...at or below the actual refresh is where to check. (Got that wrong in the example monitor was very close to 60Hz). Although FSX the same thing happens in P3D. It tries to rise to the higher limit and can't keep it. 

And why did I think that all this vsync at half the monitor rate only works for true full screen applications, like FSX... and not for P3D?

If you run FSX and go into windowed mode you find that there is no vsync limit, only locked fps. Go into fullscreen and the vsync settings in NCP work to limit it at half third and so on.

Since P3D is a window, VSync in P3D is used to override the desktop VSync in the window.

..so the monitor is about to show the new buffer, which is the desktop, and it starts to receive a new frame, it has to now wait again because of VSync in the window. So you might at 30 have to wait 3/4 frame, rather than 1/4 frame since they are shown twice at half refresh. Same happens in FSX with fullscreen as in the third refresh example at 20, drive it too fast and it suffers. Monitors with higher frequencies are better because there's less time to wait. Say at 144Hz we can do fifth 28.8  limiting at 28 would be a good place to start, and sixth at 24. Eventually as we get to higher frequencies it's only ever a short time to wait.

Edited February 19, 20206 yr by SteveW

Leave VSync=Off and when panning the frame isn't captive, we see shifted parts of the scene. In FSX fullscreen we would see tear.

Panning is dependent on the cameras.cfg pan rates which can look bad in a respectable setup but improves after rotating the view..

lol.

So with frame rate locked and VSync off and when turning, try VSync On and Off. When Off the flow is smoother if the GPU output is inconsistent. Frames are painted with the scenery and aircraft where they will be next time. If the frame is shown late we are not where we think we are. The locked fps is the actual time period so where we are painted is where we will be if the frame is ready to display on time. The VSync On setting refuses to show other frames so can show the little stutters.