Interesting idea. It manages certain cfg entries while FsX is running but on closure the FsX.cfg is untouched.
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.![]()
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?
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...
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".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.
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)
Saw Bill Leaming (n4gix) posted this youtube video link on FlightSim, very interesting.
http://www.youtube.com/watch?feature=player_embedded&v=p6QjTpxe_0E
My frame rates are consistently above 30-32 everywhere I go...why is his computer so slow and why does he need this software?
No I don't use jetliners like PMDG in a Thunderstorm and I never saw a need for three monitors
I won't labour the point.
henrystreet said:Pete Dowson's http://forum.avsim.net/topic/445641-fsx-fiber-accelerator/ [results]
I'm shocked more by the very low frame rates he has on 4.2Ghz i7 with or without it.