Fiber frame time fractioning HELP

[Nduru 1]

Hi guys, I currently have Fiber frame time fractioning tweak on 0.01 and it gives me the best possible fps but causes me to have high gpu loads and textures loading very slowly, and so i tried removing it but that gave me crap fps and stutters while flying through clouds. So what value do you guys use? I am not sure what value to choose between 0.01 and 0.33, what values do you guys recommend i try? Thanks

[Bert Pieke 7,585]

That totally depends on your system...

 

0.20 and 0.16 are popular values  B)

[louisdecoolste 12]

As you know the upper and lower limits, try working toward the middle from the ends until you reach a number that satisfies your requirements and system. Change in blocks of 0.05. 

 

Personally,  I see no benefit in having anything added to the .cfg at all (default with no entry is 0.33)

[z06z33 763]

.01 is way to low try.1 it works for me

[vgbaron 3,627]

Anything lower than 0.10 is ignored and set to 0.10.

 

Vic

[Nduru 1]

Thanks guys, will try 0.10 0.20 and 0.16

[1st fltsimguy 466]

I have a ton of Orbx land scenery.  I played around with this value for a considerable amount of time and settled on 0.20 which gives me smooth results on an i7920 3Ghz machine (ancient by some of today's standards.)

[pmb 5,137]

That' s funny. Three or two months ago the "invention" of 0.01 was celebrated as the best thing since sliced bread throughout all fora.

 

Times are changing quickly.

 

Kind regards, Michael

[JJJackson 22]

Yes pmb and a lot of gurus out there claim that it should not be used at all!!!

 

Jack

the Swede in Spain

[vgbaron 3,627]

Sometimes people see what they want to see and believe what they want to believe. Facts are irrelevant.

 

 

Vic

[nudata 10]

Sometimes people see what they want to see and believe what they want to believe. Facts are irrelevant.

 

 

Vic

 

Propagating "tweak" settings as absolute is an ego excercise or ignorance. A range of values serve a range of hardware and associated software. But, some people really love to make proclamations. I started a thread on this a while ago and I use .01. It worked and gave me a boost in FPS. It still works today. My advice is spend a few hours going through a range of settings if you want to squeeze the max FPS. However, add something new and that value may not be ok for running it in P3D,

[louisdecoolste 12]

Most tweaks do nothing, most of the time. Some do bad things some of the time. Occasionally a tweak might do some good. VERY occasionally !

 

Unless you try them you won't know. Unless you have a back-up plan or the knowledge to restore the computer to pre-tweak you are risking a lot.

 

Simply throwing them at your sim does not work 100% of the time. 

 

And alongside the backup you need a testing plan that is representative, repeatable and sustainable. Does that tweak work with your system in your simulation environment and meet your requirements ? That's why self education is the key, not coming into forums and asking questions about `best tweaks`.

 

They are all purely subjective.

[pmb 5,137]

Usually, you have to find your balance within the magic triangle:

                                          

                                               blurries

                                               |           |

                                         |                       |

                                low fps ------------- stutters

 

FFTF values as low as 0.01 just tend to shift you to the top of the triangle but give good fps. If you want to fight blurries and get good fps at the same time, you can achieve this by releasing the framerate counter to unlimted - usually at the expense of incurring fluctuations and stutters. And so on. This mostly refers to demanding areas, of course.

 

If one would find a way to eliminiate all the three at the same time even in hard areas he would be granted the Noble Prize of flight simulation.

 

Kind regards, Michael

[Nyxx 6,993]

Its very simple really.

 

Default is .33

This gives .33 of every second to loading textures. 

 

I only use Global and on my PC with P3D on a super fast SSD it does not need .33 to load global/vector (lots of things turned of within vector), i get perfect texture loading with .01 But....

 

If i use OLC or a Orbx region(I dont anymore but when i did) .01 = blurries, They need more CPU time to load, simple as that, photo real = test.

 

It's doing to be different for everyone depending on your set up. There is no wrong or right, it's a suck it and see thing. 

 

 

So if you get  blurries you need more CPU time and can delete the line to go back to .33.

I would suggest if your only using global try .01, if regions or OLC or other texture start at .1 or .15 then .2 to .25 see what works on your PC. If .25 does not work don't use the tweak.

 

Find what works for you is the bottom line and you alone nobody else.

 

With my set up and what I use .01 works great and I get the best FPS I can, I have mine locked @30 and it stays there even at Aerosoft EGLL,MT6@20% with PMDG 777. Happy days. OLC was not worth the FPS hit and slower texture loading that comes with it. Everyone is different and everyone's setting will reflect that. Like all tweaks try them yourself and add one at a time and see if they work for you. Dont use any if you see no gain yourself.

[nudata 10]

Thanks David. I had forgotten the actual purpose of the "tweak". Thus I should mention that I also run P3D on an SSD with a .01 setting. That value MAY be a best for SSD users to try first. I never experimented. I just enjoyed the maybe 20% boost in performance.