FIBER_FRAME_TIME_FRACTION

[louisdecoolste 12]

You should probably tell how you made the switch ? How did you uninstall the old card drivers ? Did you delete the shader cache ? Reinstall P3D ?

 

Go through everything step-by-step as sounds like you missed something. And don't forget the rest of your system specification.

 

 

 

I'm sure others wlll tell you what a strange choice the... 

 

... card was  :smile:

[niksan29 10]

How did you uninstall the old card drivers ? Did you delete the shader cache ?

 

Yes and yes

 

Reinstall P3D ?

 

No...I have a lot of mods, reinstall it for so long;(

 

I;m sure others wll tell you what a strange choice the

 

Why strange choice? new graphics card I got for free...

CPU i7 3770K, 12 gb ddr3.

 

P.S my bad english, I'm sorry..

[Penz 45]

My simple perspective on FFTF is that (whatever it is that needs to be done to those frames) was originally designed to take 33 percent of the processor cycles on the core running the main FSX thread, if run on "a strong PC" from around the time when FSX was originally released - something like a 2.5 GHz dual core.

 

With the faster and more efficient processors of today, one can probably aim for around half that amount (it 's still work that needs to be done on the "fiber" core!).

 

I use a somewhat conservative value of 0.20 in both FSX and P3D, it works well on my 4.3 GHz 2500K.

[vgbaron 3,627]

I really wonder where some of these numbers come from. N4Gix has already posted Phil Taylor's link and there are several others from other members of Aces that describe FFTF.

 

FFTF has a range of 0.10  to 0.50

 

FFTF DEFAULTS to 0.33

 

anything ABOVE (0.51) or below (0.01) are not valid.

 

What I can't remember and don't have time to search out is what happens when there is an INVALID (0.01) number -

 

it is either ignored completely, which would mean the default 0.33 is used OR is is changed to the next valid value - meaning that 0.01 would change to 0.10 and 0.60 would change to 0.50.

 

I'm pretty sure it defaults to next valid but that's from memory.

 

From what has been said  neither LM nor the FSX:SE folks have made any changes to that structure.

 

The other and more critical statement by Phil Taylor is that FFTF doesn't work on multicore CPU's at all.

 

Vic

[jimcarrel 688]

I've got a 4 core 3770 and if I put any FFTF in I get stutters. So I'm not sure that I could confirm that it doesn't affect multicore.

[captain420 3,099]

So from my understanding is that the 3 must have tweaks for the .cfg file are:

 

AffinityMask

FFTF

Optimize_Parts (But this is already set to 1 when installing P3D v3)

 

I'm curious and will try this tweak today. 

 

Does anyone use the Bufferpools tweak anymore with p3d? Is it necessary?

[reecemj 146]

With P3D there are no must have tweaks. Some systems don't use any of those tweaks. I only use the optimize. Fly and test and you will know what's best for your system.

 

I remember reading this thread and FTFF and affinity mask causes stutters for my system in some situations.

[vgbaron 3,627]

Does anyone use the Bufferpools tweak anymore with p3d? Is it necessary?

According to NickN, bufferpools is no longer needed and in fact, does not work in P3D.

 

The other tweaks you posted are not mandatory and should be applied on a per system basis only if they provide an improvement - as in some cases, they make it worse

 

Vic