Not sure I understand?  That’ll just artificially increase the FPS when not unlimited?

if you want FPS potential then set to unlimited and Vsync Off.

Cheers Rob

some still have the old FSX mindset
lock 30, triple buffer ON in sim or nVidia Inspector, with manually setting FFTF and affinitymask,
even though these have been retired,

Edited July 29, 20187 yr by Chris Bell

The idea is to compare Locked with Uimited .

If I use FFTF Dynamic with framerate Locked higher than the Sim can deliver and have a FFTF value of 0.01 , then I have the same framerate as with Unlimited.

Eg : with Locked at 50 + FFTF at 0.01 I see 35 . When I disable FFTF Dynamic and set the internal framerate limiter to Unlimited I also see 35.

That is what I meant..

Edited July 29, 20187 yr by GSalden

its an idea! 
not so sure its a smart one 
all you stand to prove are still lower frames than unlocked as demonstrated in the test images posted earlier,

Edited July 29, 20187 yr by Chris Bell

FFTF = 0.01 with a framerate limit set is not a viable option as it will cause terrain loading issues (aka blurries)

53 minutes ago, Rob Ainscough said:

FFTF = 0.01 with a framerate limit set is not a viable option as it will cause terrain loading issues (aka blurries)

With FFTF Dynamic I use 0.01 on the ground and 0.20 at 7000 ft and upwards ( gradually changing when climbing/descending ) . So max fps at the airports and more terrain loading time when up in the air.

With my 7940 @ 4.8 no blurries.

I wanted to do some extra SLI flights today but still too hot inside the cockpit room (  29 degrees Celcius 😓

Gerard listen to Rob's advise!
im with Rob on this 100%, do not inject FFTF settings as you're only going to induce blurries!
delete the entry from your cfg and leave it out for good,

Edited July 29, 20187 yr by Chris Bell

5 minutes ago, Chris Bell said:

Gerard listen to Rob's advise!
im with Rob on this 100%, do not inject FFTF settings as you're only going to induce blurries!
delete the entry from your cfg and leave it out for good,

That is not correct Chris.

I have been one of the beta testers and it really works.

Many have tried and tested FFTF Dynamic and found it a great help like me. Even Steve W has tested it thoroughly and was very positive about it. He tested it over multiple weeks. His results and comments are on this forum.

Everyone wants max framerates at heavy airports and no blurries when flying. This program helps with both.

 

that may work for FSX, this is still a discussion about P3D v4.3 right? 
suit yourself 

Edited July 29, 20187 yr by Chris Bell

I’m not sure I entirely agree with some of these responses. We are all aware of the difficulties experienced at complex airports . Surely it’s sensible to be using the FFTF Dynamic utility to set a low initial value, and hence improve performance, while on the ground in such situations. As you climb out, the FFTF value rises until it reaches the default 0.33 (or any other preferred value) at and above your predefined altitude, in my case 5000ft.

The beauty of using this utility is that it can be adjusted on the fly to suit various situations. If, before starting a flight, you have good performance and feel you don’t need any assistance, and don’t want to adjust any slider settings, then simply adjust the FFTF Dynamic utility accordingly to reflect an FFTF value of 0.33 and go fly.

I peg my frame rates at 30fps in-sim without VSync or TB and still find the FFTF Dynamic utility can be helpful at times, so why not use it and reap the benefit? Oh, and I rarely see blurries these days. 

Mike

before this becomes about the tool,
both myself and Rob i believe were referring to the use of FFTF entry in prepar3D.cfg not the utility!

you are both comfortably relying on valid but old and no longer relevant variable that does more damage than good in P3D v4.x,

Edited July 29, 20187 yr by Chris Bell

20 minutes ago, Chris Bell said:

that may work for FSX, this is still a discussion about P3D v4.3 right? 
suit yourself 

It has been developed for P3Dv4 and later made compatible with earlier versions ...😉

I have been one of the beta testers and imho this program is really helpfull , like Mike explained.

——

But back on topic : hopefully I can fly again one of the coming days when the temperatures drops a little. I now start to sweat , just by looking at the cockpit 😨

Edited July 29, 20187 yr by GSalden

I believe that all Rob said was using an FFTF value of 0.01 with a limited frame rate will cause blurries, which of course makes sense, since one is virtually preventing the CPU from loading any fibers. He didn't say anything either about FFTF being a valid variable or anything at all about FFTF Dynamic.

 FIBER_FRAME_TIME_FRACTION was initially listed as a custom variable but removed from P3D supported variables a while back, it still can be found on older SDK revisions,

Edited July 29, 20187 yr by Chris Bell

im wrong, its listed there again!