16 minutes ago, joepoway said:

Are you running your Sony TVs at 30 Hz and also are you running with TB on and Unlimited in P3D. I run my Samsung 4K TV at native 30 Hz and use Vsync, TB  and Unlimited in P3D and found that to be smoother than the experimentation I recently did with the new Nvidia frame limiter at various settings around 30 fps. I had not thought about adding an external 31 fps limit with Nvidia CP to my current setup.

Joe

They are running at 25 hertz / Vsync on / NV Limiter at 26.

Not using Vsync leads to tearing on my WidevieW client pc.This is smooth without stutters or tearing.

Before I used 30 hertz but with TE GB London area I could have AG set to Very Dense + Clouds/Terrain Shadows and bad weather ( rain) I got some small stutters . Using 25 hertz gave my server ( dual monitor view ) the extra breathing space it needed to run smooth.

On 2/21/2020 at 9:03 AM, CoolCaptain said:

I had tried it. It works perfectly but I encountered late autogen loading during descent. For me, it is not as efficient as the P3D internal frame rate limiter, the one with whom I always have the autogen fully loaded during the whole flight.

 

This is how mine is set up. Set to 30 frames as I fly only online. No stutters at all. 

20 minutes ago, B777ER said:

This is how mine is set up. Set to 30 frames as I fly only online. No stutters at all. 

I don't understand how this is possible. You're literally getting zero stutters? So landing at a major airport like JFK or ORD it's perfectly smooth, all the way down?

1 hour ago, Chapstick said:

I don't understand how this is possible. You're literally getting zero stutters? So landing at a major airport like JFK or ORD it's perfectly smooth, all the way down?

He might be using settings that give his pc the headroom to land at major airports without stutters ...

9 minutes ago, GSalden said:

He might be using settings that give his pc the headroom to land at major airports without stutters ...

Is it really possible? Are we talking about the same breed of stutters? I understand that FPS can be maintained up to a limit provided the hardware capability together with scalability of graphic settings (the lower the setting the higher the FPS in general terms), but stuttering to me seems to be mostly always present no matter what. The only time I used to see no stuttering (mostly) was when my simulator was FSX running at a 60 Hz screen with VSync set at Half Refresh Rate via NVI... But FSX was a real full screen application, fortunately. I was never able to replicate this to P3D since then...

Edited February 23, 20206 yr by Wanthuyr Filho

3 hours ago, GSalden said:

They are running at 25 hertz / Vsync on / NV Limiter at 26.

Not using Vsync leads to tearing on my WidevieW client pc.This is smooth without stutters or tearing.

Before I used 30 hertz but with TE GB London area I could have AG set to Very Dense + Clouds/Terrain Shadows and bad weather ( rain) I got some small stutters . Using 25 hertz gave my server ( dual monitor view ) the extra breathing space it needed to run smooth.

...  and to be clear you are also setting P3D to Unlimited and using Triple Buffering in conjunction with Vsync, correct? 

 

Thanks

Joe

36 minutes ago, joepoway said:

...  and to be clear you are also setting P3D to Unlimited and using Triple Buffering in conjunction with Vsync, correct? 

 

Thanks

Joe

I do not use TB. It helps with smoothing if you can maintain a little headroom but it might cause small jitters when sometimes you cannot keep up the framerate...

This is how 25 hertz / Unlimited / NV Limiter 26 looks like :

Bodrum today ( live Traffic / live weather ) 

 

 

Edited February 23, 20206 yr by GSalden

2 hours ago, GSalden said:

I do not use TB. It helps with smoothing if you can maintain a little headroom but it might cause small jitters when sometimes you cannot keep up the framerate...

This is how 25 hertz / Unlimited / NV Limiter 26 looks like :

Bodrum today ( live Traffic / live weather ) 

Thanks for the response and nice setup !

Joe

Different setups and different screens and resolutions, scenery, whether showing the gauges or an outside view, fullscreen or windowed size, all play a part. Since these cause the differences in time to build frames. The Limiter is adjusting based on the time between frames. I just did a couple of tests with VSync=ON+Unlimited. NCP Max Frame Rate = 31 v 29 Mooney cockpit view. on the 31 limit I see frame times between 22..59, and on the 29 limit between 23..38.

Edited February 24, 20206 yr by SteveW

...60Hz monitor. Early frames are lost giving rise to the high frame rate up to 59.

5 hours ago, SteveW said:

Different setups and different screens and resolutions, scenery, whether showing the gauges or an outside view, fullscreen or windowed size, all play a part. Since these cause the differences in time to build frames. The Limiter is adjusting based on the time between frames. I just did a couple of tests with VSync=ON+Unlimited. NCP Max Frame Rate = 31 v 29 Mooney cockpit view. on the 31 limit I see frame times between 22..59, and on the 29 limit between 23..38.

Could you expand or summarize on why would you still want to use VSync=On even when there's an FPS limiter setting in NCP that you can use to limit P3D's FPS output at half of the standard 60Hz monitor's frequency? 

Thanks.

Edited February 24, 20206 yr by Dirk98

VSync=Off flips the buffer on a timely basis. No VSync shows the current state of the buffer which can be showing half shifted, or tear. VSync=On waits for a complete buffer.

4 minutes ago, SteveW said:

VSync=Off flips the buffer on a timely basis. No VSync shows the current state of the buffer which can be showing half shifted, or tear. VSync=On waits for a complete buffer.

concise and precise, all is clear, 

Thanks

It is counter intuitive and a little hard to grasp. Frames arriving early update the buffer before the last buffer is shown, so that buffer is lost, a new frame is started right away instead of limited. That leads to climbing fps rate and an averaging fps monitor can show a higher average rate. This is not actually such a good situation because it consumes CPU for no gain, but a score might show better quality.

Edited February 24, 20206 yr by SteveW

Hi,

In my simulator setup (P3D 4.5) with two views (main view=only outside view on 3840x1920 and a second undocked view for the VC only spread over two touchscreens) the limiting via nVidia driver to 30 fps works really fine ... until I use some undocked pop-up panels, which are moved to the second view. As long as all the pop-ups are closed, I run the 30 fps which I set in the nVidia driver. But If I open one pop-up panel, frame rate is only half at 15 fps. And if I open another pop-up panel it's 10 fps only. Closing the pop-up panels immediately gives me back the 30 fps.

If I dock these panels to the second view, it works again. So why I am using undocked panels? If I save the scenario with the undocked panels and load it again, the pop-ups appear on the right place. If I save the scenario with docked panels, they re loaded on the left upper corner of the view. So the position is not restored in that case. No idea, if this is a "feature" of P3D 4.5.

Rgds
Reinhard