FIBER FRAME TIME FRACTION Question

[Lionheart]

Hey guys,

In the quest to get smooth frame rates with FSX, a new factor (line/string/setting) was added to the FSX Config file called

FIBER_FRAME_TIME_FRACTION

My settings for TileProxy have it set to 1.33. May I ask what would happen if I bump it up to 2.33 or even 4.33? Will I fry my graphics card? Or am I safe and nothing really happens.

To be truthfull, I did boost it up to 2.33 and its running fine and stable, but I want to try out 4.33, lol... I thought though that I should check with the gurus of adjustments before doing this.

Many thanks for any input.


Bill

[stiz]

didnt SP2 render that line uneeded???

[Lionheart]

Actually, I thought they added it 'on' to SP2, but I am probably wrong. It might be a SP1 thing, now that I think about it.



Bill

[elcamino]

didnt SP2 render that line uneeded???

Is there a list around somewhere of the tweaks required \ nice to use for sp2?
There are plenty for fsx & sp1 and bits and pieces for sp2. Is there something
official? Like: "Forget all the rest, these are the ones to use for sp2."

[N332DW]

i think it was P-12C who laid it all out in his blog... it's about portioning out the workload between aircraft and scenery renders, so i dont think you will fry your card.

http://blogs.technet.com/p-12c_pilot...20/448111.aspx

there is no such thing as 110 percent , that only indicates one is "sand-bagging"to begin with.
...we're going 110% the speed of light

[Lionheart]

Hey N332DW,

Thanks for the heads up on P-12C's blog on this. I'll check it out.


I dont think its a percent, but a fractional factor, like FS landing gear setting values of max compression per travel distance.


Dont get me going on speed of light theorys. :d A fave subject of mine.


:ernae:

Bill

[Bjoern]

a) FFTF is only needed if you have a single core.

b) No such thing as 1.33 or more. If I remember correctly, the setting simply controls how much calculating power goes into terrain rendering. A setting of 1.33 would mean that 133% of the CPU power would be used for the terrain - no worki comeradski.
Your best bet would be a setting of 0.5-0.6 if you can trade off sim speed for terrain rendering.

[JT8D-9A]

You can experiment with "SWAP_WAIT_TIMEOUT" (=number of frames), in the Terrain section of your FSX.cfg. The default value is 30. You can try to reduce it.

EDIT: sorry, i should have read your topic more carefully :redf: I was thinking about texture loading and not smoothness.. have you locked your frames?

[Lionheart]

You can experiment with "SWAP_WAIT_TIMEOUT" (=number of frames), in the Terrain section of your FSX.cfg. The default value is 30. You can try to reduce it.

EDIT: sorry, i should have read your topic more carefully :redf: I was thinking about texture loading and not smoothness.. have you locked your frames?

Hey Nils,

Yes, frames are locked at 20.

I am having issues with fuzzies and high resolution loading. It is taking forever and wanted to see if I could boost the time/loading factor.



Bill

[harleyman]

Hey Nils,

Yes, frames are locked at 20.

I am having issues with fuzzies and high resolution loading. It is taking forever and wanted to see if I could boost the time/loading factor.



Bill

Take a nap...it works well over 50......:d

Sorry...I am no help.......

[Lionheart]

Take a nap...it works well over 50......:d

Sorry...I am no help.......

LOLOL.... :costumes:

Yes.. That works for me.

Im getting old.. My eyebrows are all gray... arrghh...

[barryward12345]

Lionheart

What do you call "High res" in TP?? Are you attempting to get 30cm textures??

Barry

[barryward12345]

Some time ago, I posted this below, over at AVISM

I have today installed TP into my new, fresh FSx installation. Over the past week, I have been "tuning" FSx and have read a lot about so-called"tweaks" for FSx. It appears that most of these were in fact developed before SP1 was issued and it seems that some are no longer of any use. In fact they may even be detrimental. It also seems that your success or otherwise in running FSx is dependent on a number of things - which some of these tweaks interract with in a negative way . 2 of these "things" relate whether you have a dual core or single core machine - and also to what amount of vid RAM you have.

I note that installation of TP makes some changes to the FSx.cfg file

1. TEXTURE_BANDWIDTH_MULTI is changed for 40 to 400

2. FIBER_FRAME_TIME_FRACTION goes from default 0.33 to 1.33 (with a note in the installation folder to say that if this is too sever, then go back to0.66)

3. BUFFERPOOLS goes from default 4 MB to 5MB

From Phil Taylors' ( MS) blog is this info relating to each of these:
================================================== =============
TEXTURE_BANDWIDTH_MULTI

The TEXTURE_BANDWIDTH_MULT option in the Graphics section is the target frame rate use for calculating texture bandwidth. The higher you set this value the more textures we will allocate and copy per frame to the graphics card. The lower you set this value, the less we will allocate and copy up to a minimum limit. As an example, the default rate in the “high” perf bucket setting is 40. The lowest perf bucket setting is 10.

Higher settings on this flag can cause stutters on frames where the terrain system has finished compositing lots of textures. Lower settings can reduce stutters on busy frames and spread out the load across multiple frames

So thinking this thru, if the value you set is 40, and your frame rate limit is 30, then we will send 40/30 or 4/3 as much textures per frame.

Moving this value to 400, like I have seen some users post in the forums, is probably *not* what you want to do since that increases the texture load on the graphics card by 10x, eg 400/40 = 10x. And after talking about this to Raf, setting it to 0 is ignored and can be validated by setting it to 10 which should give no different results.



FIBER_FRAME_TIME_FRACTION

The operation of FIBER_FRAME_TIME_FRACTION on single core machines has not changed since RTM.On multi-core machines in SP1, we moved many fiber jobs off of the primary thread and onto secondary threads. Since FIBER_FRAME_TIME_FRACTION only affects scheduling of jobs on the primary thread, it will have less of an impact on the performance of Flight Sim on multi-core machines. In fact, we moved so many jobs off of the primary thread that there probably isn’t enough fiber work left to soak up the full time allowed by the default value of 0.33.

Therefore, on multi-core machines, there’s very little reason to tweak the fraction because it really only impacts performance of single core machines.


BUFFERPOOLS

The pedestrian sounding BUFFERPOOLS is a section of its own in the fsx.cfg file. There is a setting in there called Poolsize, as in



Poolsize=n

Where n is the amount of bytes we will allocate for one pool of vertex and index buffers to store geometry.

In RTM, the default setting was 1MB (1000000). The lower this number, the more pools the allocator will have to rummage through to find space for buffers and the more stutters you may have. In Sp1, we raised the default to 4MB (4000000) and optimized the underlying algorithm for finding free buffers

So be careful here, making this smaller can hurt you, since searching for space takes time and can cause stutters, and making the number too large can waste space. 4-10m is probably the range to be thinking about using unless you have a very high memory graphics card (>512mb )
================================================== ============

This is all very "theoretical" - but in my case, I have a Dual core CPU ( so the bit about the FIBER_FRAME_TIME_FRACTION is relevant to me) and I also have only a 256 MB vid card (which struggles) so the bits about BUFFERPOOLS and TEXTURE_BANDWIDTH_MULTI are also relevant to me.

At this early stage, I have started using TP with FSx using my FSx.cfg file as set up for "normal" non-TP use. It seems to be working quite well like this.

So, I would encourage everybody to have a think about the above in relation to whatever machine you have

I now run my FSX.cfg stock standard - using only slider control from within the Sim

I have yet to find any FSX.cfg "tweak" that really achieves anything in the way of improving my medium systems performance.



Barry

[Lionheart]

Many thanks Barry for the information. Very much appreciated.

One learns so much about computer technology via flying in FS. :d


:ernae:




Bill

[Bjoern]

One learns so much about computer technology via flying in FS. :d

Oh yes!

With the right people though, it's a piece of cake.