So I've been experimenting with using a target frame rate in P3D.

And found some interesting results.

I've running Vsync @ 30 Hz for a smooth 30 fps meaning no mattter the target frame rate I'll always be @ 30 fps.

With the target framerate set to 30 core zero use hovers @ the 90 to 100% mark, mostly it is mid to high 90s.

If I increase the target frame rate by 1 i.e. 31 fps, core zero use drops to 50 to 60% use.

Frame rate is still a smooth 30 due to the use of Vsync, in fact it's smoother as with the target set to 30 there tended to be the occasional drop slightly below the vsync rate whihc causes a jarring.

Quite an interesting result as I've often wondered how so many people could be reporting ~100% core zero use all the time when i barely see it ever happening on my rig given I use a fps target of unlimited.

Cheers

 

I understood  with vsync enabled, you must not use the frame limiter

Not really, there is nothing stopping the use of either or both, in any case for VSync to work the frame rate needs to match or be higher than the monitor Hz rate.

e.g. if you're runing a 60 hz screen mode P3D will need to output 60 fps in order to "VSync' to the screen mode and allow super smooth flying.

I run a 30 Hz screen mode which means P3D only needs to be able to maintain 30 fps and allows me to turn up the GFX settings for greater immersion. 60 fps is a goal out of reach once new scenery and addins are installed into P3D (maybe possible with a 6Ghz nitrogen cooled CPU).

Typically without vsync enabled and the target frame rate set to unlimited my rig can manage around 40-50 off fps as long as there are not too many 3D objects and the plane is not too complex.

Setting the frame rate limiter to anything other than unlimited does tell P3D to use the values for the defined settings of TEXTURE_BANDWIDTH_MULT and FIBER_FRAME_TIME_FRACTION, otherwise they are ignored.

This is where utilites such FTFF Dynamic and Riva Tuner Statistic Server become handy tools for manage the FIBER_FRAME_TIME_FRACTION dynamically (for improving scenery loading) and Riva Tuner Statistic Server allows vsync @ half a monitor's Hz rate (should the monitor not support a 30 hz rate for example).

Cheers

8 hours ago, Rogen said:

This is where utilites such FTFF Dynamic and Riva Tuner Statistic Server become handy tools for manage the FIBER_FRAME_TIME_FRACTION dynamically (for improving scenery loading) and Riva Tuner Statistic Server allows vsync @ half a monitor's Hz rate (should the monitor not support a 30 hz rate for example).

FTFF dynamic causes microstutters on my system.

Riva Tuner works great, been using it for quite some time now.

4 hours ago, newtie said:

FTFF dynamic causes microstutters on my system.

Really?

I wonder why? cause I'm not seeing microstutters but then again I'm running VSync @ 30Hz and have a few tweaks as well (such as Slik Smoothness in the NVidia Inspector).

Do they occur on both methods of FTFF Dynamic injection?

I know FTFF Dynamic works as I had a particular area that would be blurry as I flew up over it with the P3D limiter set to unlimited. With FTFF Dynamic running, the area loads fine and crisp with the P3D limiter set to unlimited.

Cheers

Edited October 12, 20196 yr by Rogen

Hi Rogen-

I tried this app multiple times and always wind up removing it. But, that's just me on my system.

I don't really suffer from blurries as I run sliders mid/left with mostly photoscenery and some ORBX airports tossed in for good measure. But it wasn't always that way.

Looking back, installing my three Samsung 500GB SSDs with the OS and P3D on a Pro has yielded the best results for loading.

Riva Tuner 1/2 Vsync @ 30fps across my three Dell 27" monitors works great for me; haven't touched it since installing this quite some time ago.

5 hours ago, newtie said:

I tried this app multiple times and always wind up removing it. But, that's just me on my system.

 

That was my experience too. RTSS 1/2 refresh rate and VSYNC ON with moderate-high settings. I did not change anything since quite some time. But I admit, I'm tempted to tweak from time to time just to find out what I already know ...