Fiber Accelerator by FSPS

This sounds like a good FSX improvement for those of us who are too lazy and/or too cheap to upgrade our systems to where the sim can run with maxed-out sliders and top-end FPS. :encouragement:
 
I have just been tinkering with the demo and got some quite positive results. I followed the instructions in the read me. I chose my worst performing airport - CYVR (because of all my addons, FSGlobal Mesh, Van+, UT2, FTX) Worst performing Aircraft - the PMDG 737-800. ANd the FSX Thundestorm WX preset.
Normally under these conditions I would avoid YVR like the plague, certainly in that aircraft. I would get fps in single figures and stutters which made it totally unflyable.

My PC for comparison is a 2600K Intel with 16GB RAM and a GTX660 video card. I run FSX in windowed mode (Pseudo full screen) highly tweaked cfg and in DX10 mode. I have the FPS locked at 31.

OK so I fired up FSX, set the parking brake and waited whilst everything settles down and was reading fps of 12.4 or thereabouts in the VC. I took a couple of exterior shots (one with AI in background) and got 14.7 and 16.1 respectively.

I then ran the fiber program and left all the settings at default. The same pics were now. = 13.3, 20.0 & 18.1.
I then pushed the slider down to 15 on the Fiber prog and now the fps were = 14.0, 17.2, 16.1
I then tried the slider on max and FSX froze.

So Cockpit shots gained 1 - 2 frames
Exterior shots without any AI in the picture gained quite between 3 & 6 fps
Exterior with AI showing - no great gain.

Not very scientific I know but for me it was marginal whether or not I would consider buying it.
 
Update - Just had a session flying around the Fraser Valley and YVR. FPS are improved in a 2-6 fps region within the VC. But it still stutters badly in the PMDG 737 especially flying west toward YVR, not so bad (micro stutters) flying away from it. Useable more so than without it but I'm not convinced the program is for me. If I were to rate it I would give it 5/10.
 
Interesting idea. It manages certain cfg entries while FsX is running but on closure the FsX.cfg is untouched.

As I understand it the fsx.cfg file is not touched at all! I've tried the demo and managed to get 3-5 frames increase with the Flight1 C182T at KSEA in heavy thunderstorms. My pc is just to darn old, because I still couldn't reach the 10 fps limit in that situation...
 
As I understand it the fsx.cfg file is not touched at all! I've tried the demo and managed to get 3-5 frames increase with the Flight1 C182T at KSEA in heavy thunderstorms. My pc is just to darn old, because I still couldn't reach the 10 fps limit in that situation...

Hi Bert,
Interesting findings. I've just read through the entire Avsim thread (most posts complaining about the demo!) and it seems that the best results come from limiting frames in FsX to a value that you can't normally achieve very often and then Fiber Acc' will dynamically alter cfg entries to suit the loading. Now as I understand it, the vsync tearing fix is only achieved when frames are limited to half the refresh rate, which in my case is 30 because my monitor refresh is at 60Hz. So if I start changing my limit in FsX then I will see tearing as the NVI setting will not be valid. Can anyone confirm this?
 
Hi Bert,
Interesting findings. I've just read through the entire Avsim thread (most posts complaining about the demo!) and it seems that the best results come from limiting frames in FsX to a value that you can't normally achieve very often and then Fiber Acc' will dynamically alter cfg entries to suit the loading. Now as I understand it, the vsync tearing fix is only achieved when frames are limited to half the refresh rate, which in my case is 30 because my monitor refresh is at 60Hz. So if I start changing my limit in FsX then I will see tearing as the NVI setting will not be valid. Can anyone confirm this?

Well I asked the same question on the Avsim thread and although I feel this issue requires answers I got no reply, so I suppose this (to me at least) important question will remain unanswered...
 
Well I asked the same question on the Avsim thread and although I feel this issue requires answers I got no reply, so I suppose this (to me at least) important question will remain unanswered...

Roger, I am not very knowledgeable on this but I'm pretty sure you will not see tearing. I force vsync on and don't ever see any tearing even though I don't use the 1/2 refresh-rate option and I rarely achieve 30fps.

I think the impact of using vsync is that your actual frame rate will in some circumstances fall to a factor (half or a quarter) of the monitor's refresh rate. (This is regardless of what FSX is reporting its frame rate to be.) My understanding of why this is is that you're instructing your GPU to wait for the monitor, not the other way around. When your frame rate significantly exceeds the refresh rate, the actual frame rate will be limited limited to refresh rate. When your frame rate falls just below the refresh rate, the actual frame rate may fall back to a factor of the refresh rate.

(I stand to be corrected on most of that, except the part where I don't ever see tearing ;) )
 
They explain quite well what is done under the hood.
What they wrote is a bit exagerated, but basically they dynamically tweak the main variables of the FSX.cfg in flight. The texture_bandwith_mult, texturemaxload, etc... are adjusted depending on the available ressource. You basically set a lower FPS limit, and the soft reacts as soon as the FPS in game get too close to it to try to prevent them from dropping.
They don't explain anything that they do. It says in the product description it is not used, "we directly, in real-time, dynamically inserting FSX tweaks without touching fsx.cfg". The developer also mentioned in another post "We don't touch fsx.cfg - neither read or write . It is completely ignored." He then goes on to mention how they "rewrote the FSX graphics engine".
 
Roger, I am not very knowledgeable on this but I'm pretty sure you will not see tearing. I force vsync on and don't ever see any tearing even though I don't use the 1/2 refresh-rate option and I rarely achieve 30fps.

I think the impact of using vsync is that your actual frame rate will in some circumstances fall to a factor (half or a quarter) of the monitor's refresh rate. (This is regardless of what FSX is reporting its frame rate to be.) My understanding of why this is is that you're instructing your GPU to wait for the monitor, not the other way around. When your frame rate significantly exceeds the refresh rate, the actual frame rate will be limited limited to refresh rate. When your frame rate falls just below the refresh rate, the actual frame rate may fall back to a factor of the refresh rate.

(I stand to be corrected on most of that, except the part where I don't ever see tearing ;) )

Hi Mark,
It would seem that force vsync doesn't work in Dx10.
 
Frooglesim has done a first impressions video on this
I doubt I'll get it as I fly almost exclusively in P3D now but his results are very interesting.
 
After looking at all the information I can't see the value in this software. I have an older Q9650, Nvidia GTX 285, 4GB Corsair Dominator RAM, water-cooled clocked at 4.2GHz that will run circles around his newer computer apparently. My frame rates are consistently above 30-32 everywhere I go...why is his computer so slow and why does he need this software? I run Orbx and REX4 with FSX. I honestly cannot believe this software is needed for any of the newer i7 based computers that are clocked at 3.2 or better.
Ted
 
My frame rates are consistently above 30-32 everywhere I go...why is his computer so slow and why does he need this software?

Did you read the part where he says he runs three 27" displays? (And an extra one.) If you are saying your computer will hold 30fps with a PMDG aircraft at KSEA in a thunderstorm on a 6Mp display (possibly 11Mp, he isn't specific) I am going to be sceptical.
 
No I don't use jetliners like PMDG in a Thunderstorm and I never saw a need for three monitors, but I can average 30 fps with A2A aircraft with Accu-Feel on a dual monitor at KSEA in bad wx to include the old Boeing B377.
By the way...there are others in here and in other forums I have built units for than can attest to above avg frame-rates and excellent graphics with the units I build.
 
I won't labour the point.

Mark I guess this looks like I am glad handing myself...that is not the point. There has been so much SNAKE OIL software out there for FSX that really if you know your system capabilities and don't try to overload them you should be able to enjoy a really nice experience. I still don't see this latest piece of software as the end all-do all for FSX. It is an old engine that is finally coming into it's own with the i5 and i7 series motherboards and CPUs. Still it has some crazy quirks that drive the best hardware and software geeks NUTS! I am so glad Lockheed Martin took the reins and made P3D what it is and it is only getting better.
Ted
 
I fly Iris PC-21, VRS Superbug, Ant's T-28C/D, well you get the picture. Almost all below angels 10 with OpusFSX for weather. Done extensive testing with my rig http://uchisworld.wordpress.com/2014/05/26/happy-anniversary-part-2/ been working with computers professionally since the late 1970's yadayadayada.... bottom line: my results with the demo (at KSEA, as depicted in my website, and at Hobart Tasmania by Orbx, are almost identical to Pete Dowson's http://forum.avsim.net/topic/445641-fsx-fiber-accelerator/

My frames did not improve more than 10% but OMG the smoothness factor was much better. And, even before reading Pete's comments, I was able to increase the detail sliders with no loss of FPS or smoothness.

There is a demo you know and based on how it worked, I am purchasing.
 
Back
Top