Sorry to be dim guys, but can someone explain to me, once you have set, say for example a frame rate of 30 in the GUI, exactly how does it decide when to allocate more processing power to loading terrain instead of maintaining frames? I understand the concept, but not the implementation. The way I understand things, sat at an airport, it will increase frames in return for loading scenery, which is great as it means stutters become less at some of the big heavy duty hubs. But, once airborne, how does it decide to allocate processing power to loading scenery so as to reduce blurries?

 

I'm assuming this is what happens, or is it just about getting as high a framerate as possible?

My understanding is that it will try to hold the fps number that you have set.

 

So, if it can hold 30, it will devote spare resources to texture loading, not to further increase framerates.

Hi Bert, but if you set your framerate at 30, the rest of the resources naturally are used for loading terrain,  that has always been the reason for locking framerates, at least that has always been my understanding. Is this not the case?

 

EDIT: OK, I think I get it. But if I'm right, and it tries to maintain a preset amount of frames eg 30, then that is not always going to be advantageous. If you are flying in a CPU intensive scenario, eg, heavy weather, NGX, lots of AG etc etc which perhaps you'd normally achieve maybe 20 frames, then by this little gizmo pushing frames up to 30 then it can only have a negative impact on texture loading, resulting in blurries. Presumably by effectively reducing the FFTF to increase framerates, but of course we know what happens when you change the FFTF.

 

This is beneficial around an airport, sure, but if flying with frames less than your preset amount, in my example 30, then I can't see how it will be a benefit, except when there are plenty of frames available that can be divided up between a framerate and terrain loading.  I'm happy to be corrected and maybe someone can offer an explanation...

Hi Bryan

 

I have the same processor as you but have overclocked mine to 4.2ghz, have you though about doing this yourself? I have very minimal computer knowledge but managed it myself. It makes a heck of a difference!

 

Gavin

 

Hey Gavin....I did some research in the spring into the possibility of OCing my PC.  I have a Gateway and the particular motherboard, apparently according to all my reading was that this BIOs is locked in some way to prevent OCing.  I found a lot of material on this topic and a couple of OCing tools which apparently when tried don't work because of this "locking".

 

I am PMing you.

This is beneficial around an airport, sure

 

Precisely. That's my point, as I explained earlier. The benefit I get is no stuttering at a fully populated UK2000 EGLL. I don't see any "blurries" because all I see is the airport or its runways and its AI. When I'm away from the airport or high enough to see the landscape around me, the frame rate is high enough for FA not to reduce FFTF. I see no blurries then either.  To make such a transition more "definite" the new version, 1.2, provides keystrokes to allow you to change the desired frame rates or even switch off FA's action too, on the fly. I don't really think this is needed on my system, though I am programming a little Lua plug-in to change the FA target at a specific AGL.

 

As folks have found over the years and you yourself point out, there are benefits and costs of having lower FFTF values -- and also having the FS frame rate limit set "unlimited". The benefits can be less stutters, the costs more blurries. It's a trade off which we've all been making manually but there's never been one 'correct' value which suits all circumstances. This little program is a tool which allows you to have those trade-offs made automatically (or semi-automatically), so you can have it both ways. And it does it without you needing to pause and visit the menus, or edit the CFG file and reload.

 

Pete

 

 

I was going to download the demo and run it, but never got around to it.  Now, however, I will just purchase it outright and use it.

 

I would use the DEMO, to assure yourself, that it is adding user-value to your simming.  The DEMO gives you an unfettered 6 hour try out.  For myself, I actually only used the DEMO 15 minutes.  I was taking off from ORBX Northern California's SP1  KSFO, and was banking towards the downtown area, at about 11 FPS (I have serious demands on FSX...) and had some stutter and chunk. I then fired up FSX Fiber, and the sim smoothed right out before my eyes....even though it stayed around 11-12 FPS, the stutter was gone, along with the chunk.  There was no truly visible degradation in the rendered scene.....

 

I ended my FSX session....located a seller...and purchased the full use program, right there on the spot.  Been happy with that decision, ever since....

 

Sesquashtoo

the new version, 1.2, provides keystrokes to allow you to change the desired frame rates or even switch off FA's action too, on the fly.

 

Ahh, now I can see some great benefits with this Pete. So it would be effectively possible to set the cfg manually to give the best performance for terrain loading, and keep the gizmo effectively switched off in the air, knowing you were getting the best performance for scenery performance Then when you need the extra fames on the ground, you could use the gizmo, which would change the FFTF accordingly. That's really very exciting.

I fly the PMDG B777, and need all the help I can get.  FSX Fiber, has helped me, would not want to fly without it.

 

JFriz

I have a question - I have an external frame limiter (can't recall which right now). Will that cause problems for this tool ? Does it need to be disabled ?

Hi Dick, no you can still use a limiter. You can't use the 1/2 sync setting in Inspector.

So guys,

 

Advice please, I have fibre but uninstalled it as it just did not do anything however reading the posts it mentions the FFTF. My cfg file has the entry already in there and set to 9 at all times, if I took this out would fibre work any better.

 

What I a asking is if the entry is already there does it effect how fibre works.

 

Many thanks

Fiber in the fsx.cfg file is different than the Fiber utility. The Fiber utility has no idea what is in your FSX.cfg file.

 

To test for yourself: Cut and paste your fsx.cfg file to a safe place, run FSX, install the Fiber utility, and then test.

Thank you Jim.

 

Will try that and see.

 

All the best.

Hi Dick, no you can still use a limiter. You can't use the 1/2 sync setting in Inspector.

That's fine. The 1/2 sync option isn't available in my version of NI anyway :smile:

That's fine. The 1/2 sync option isn't available in my version of NI anyway :smile:

I use an external limiter set to 30...and also have FSX locked to 30. Fiber will do its thing independant of those settings, as when running to unlimited..and back and forth. Quite amazing to see this all happening, dynamically in real-time. The program is a keeper for sure...

Advice please, I have fibre but uninstalled it as it just did not do anything however reading the posts it mentions the FFTF. My cfg file has the entry already in there and set to 9 at all times

 

Are you sure..

 

The default value for FFTF in FSX is 0.33.

 

Some recommend to try 0.2 or 0.15...    Where did you get 9 from?