I have seen a lot of post from the developers telling people that it does not do this, or it does not do that, but none that says that it affects other parts of your system.

Just as a heads up, some posters are skating perilously close to being libelous in nature. Be very, very careful with your written words.

Totally agree. I also use Acronis.
recommendations:

I have 1 copy of FSX FULL. The first was when installing FSX.
Also one FULL copy of the OS.

I'm installing new add and airports, etc.. (I write every change in a text file with dates). Installing leave for two weeks time. If all my flights work well, it means that nothing will change. Then I make a new incremental backup.

So, if something happens, I can turn back viewing the last change.

It is a little longer, but worth protecting our best FSX settings.

@vooddo - as FSX is really a queen we have to protect her. I uae the ACRONIS BACKUP TOOL on system and FSX disk before I install anything new. This prevents me from reinstallation of the whole thing.

cheers Tom

Adam, there is nothing left after uninstall... 

Checked it myself with my regcleaning tool.

 

If you feel better rebuilt the fsx.cfg file. 

Gerard - I did all that (I had a pre-FA fsx.cfg backed up). I ran a check against the last one used by FA and other than the frame limiter line (which was set to the last value I tried with FA) everything was the same.

 

My Regcleaner found no instances of FA (other than related to the Zip file), so that was all clear too.

 

However - I still think I have a slightly downgraded FSX.

 

To the AVSIM moderator(s) - IMHO this topic could be cooled instantly by a post or two from the DEVS that could put us out of our misery! With no input from them, it's all just conjecture.

 

Adam.

Hi Adam, 

 

please tell us what you like to hear. Please take some moments and write down the questions you have and we will answer.

Any program run on Windows will leave many registry entries since windows makes them to record activity and many other things. So if we uninstall an app it will remove it's own entries from the registry but it won't remove the entries Windows made. The app won't leave FSX running slower, that's most likely a placebo effect. Smoothness in FSX does not go hand in hand with fps, in fact higher fps leads to blurring ground textures and stutters since the smoothing actions of concurrency within FSX has less room to manoeuvre, and less time between frames means less time to complete the sharpness of texture detail.

After the last uninstall of P3D there were over 42,000 (yes, thousand) orphaned entries left by LM in the registry. What's a few more here or there.....    

 

Doug

Hi Adam, 

 

please tell us what you like to hear. Please take some moments and write down the questions you have and we will answer.

Thanks, BD - much appreciated (truly!). I suppose it must be just as hard for you to unravel this LONG thread as it is for us to read it.

 

My specific queries were in #477 (and earlier, I think) but I'll paste them here again to save you looking:

 

==========================================

Thanks for your patience BD!

 

I understand all of the above (which I admit you have posted numerous times).

 

I'm OK on the fsx,cfg part ... but ... just be *perfectly clear*:

 

1) No registry changes (NVI related)

2) No other "left over" DLLs (or suchlike) that could in any way impact FSX?

 

In all fairness, I think your wording in your advertising may be disturbing people "By – in other words – rewritting the FSX graphics engine" [note your typo!]. That's the thing that's scaring people! It implies physical re-writing, where it should really imply that it's manipulating the way the FSX graphics engine works (in memory) ... or something similar/shorter (!).

 

Adam.

========================================

 

I think we all agree that fsx.cfg is read and manipulated "on the fly" - and that the only value that may be written is the framelimiter line (so no problems there). I'm just a little worried that something else might have upset my FSX in some way - as I restored both my fsx.cfg and NVI profile back to pre-FA install and I think my performance has gone down (but not drastically).

 

Like many others here, I'm desperately keen for FA to work its magic - but not if there's a risk that FSX gets "hi-jacked" in some way. I have no axes to grind - just want to protect my months of painful tweaks and adjustments!

 

Adam.

After the last uninstall of P3D there were over 42,000 (yes, thousand) orphaned entries left by LM in the registry. What's a few more here or there.....    

Some folks would be astonished at just how full of absolute crap the Registry gets, which is all the more reason for running a rigorous registry cleaner every thirty days or so...

 

What really makes this "system" so poor is that no effort at all is made by Windows to clean up after itself. Is there any justification or need for the Registry to have an entry for every temporary file ever created? Seriously?

Yep, every time we run anything on Windows the registry fills up with records. :rolleyes:

No. Those of us with high end systems have high end systems precisely so they can be loaded up -- with complex sceneries, aircraft, weather and traffic. My high end system (4770K overclocked to 4.4 GHz with a GTX 3Gb 780 video card) struggles with several scenarios, in particular UK2000's Heathrow Extreme version 3 with heavy weather and realistic traffic levels. As I am basing my flying in the UK this is obviously an important hub and has become the basis of all my benchmarks in testing such add-ons as FA. And for me, whilst certainly not boosting frame rates (it reduces them somewhat), it certainly provides smoothness which was previously lacking.

 

If folks measured results by smoothness rather than by frame rate I'm sure many would come to different conclusions than several posted here. And you shouldn't get any "blurries" resulting if the instructions are followed and the lower frame rate not set ambitiously high.

 

Pete

 

I am running a similar system (video card has more ram though), like you I also seen my frame rate drop, but I did not see any improvement in smoothness.  To begin with I had very little stutter/smoothness problems without using the tool.  I did notice that my cfg file is different than yours,  basically I used some of NicN and some of Kostas suggestions,  plus my own programing knowlege.  The way I see things is it's great that they have a demo, people can make up their own mind.

@adam.

 

As already said the only thing that is related to fsx.cfg is the Target Frame entry which is changed by FSX when FSX closes. We told that from the first day, just exit FIBER before FSX and you are secured .

 

There is ABSOLUTELY NOTHING in the app that may harm your fsx in any way. It is technically impossible by the approach we used. Changes are done only while FSX is running, and that's it. The are no "small letters on the backpage" , "oh we forgot to tell you that", "ah yes, I told this is not happening , but I never said that X may not happen". There is NOTHING that can change your FSX or any other application, or hardware or software, or or ... NOTHING

 

* (off topic, technically speaking mode = ON ) The only way fsx would be permanently be changed by an application is:

1) Change a core FSX file with a new one (not only fsx.cfg but other files too).

2) Put a .dll file running along on it (on fsx.exe process) while fsx is running.

3) Make some kind of "virus" loading hidden files when it detects fsx loading.

 

We certainly don't do any of the above. They are not professional approaches.

 

-------------

 

Also you wrote : 

I think we all agree that fsx.cfg is read and manipulated "on the fly" and that the only value that may be written is the framelimiter line (so no problems there).

 

But again that is not accurate.

 

We don't read fsx.cfg . There is no need to. We use our technique to read/write all necessary data momentarily.

 

We don't write fsx.cfg . FSX does. So if - due to conditions - you are on a difficult airport and that time FA forces "unlimited" frames to FSX this value - IF YOU CLOSE FSX BEFORE FIBER - this value is written by FSX (that is an FSX function) to fsx.cfg.

 

Hoping this will finally solve the matter once and for all:

If user exits FA before he exits FSX there is no change at all, anywhere.

If user exits FSX before he exits FA, there is a probability (if he was forced at that time into "Unlimited") to have FSX write this value into his fsx.cfg and have unlimited set next time he starts FSX.

 

Hope these solve any matters raised. If not please make more questions.

PS. Thx for the typo. Not our mother language, we just try our best. We do know coding better than plain English, be assured   

Given the importance of FSX FA terminating before FSX I think it's worth reiterating that for those of you who have a registered copy of FSUIPC4 you can place an entry in fsuipc4.ini that will start the program once FSX has loaded and terminate it prior to FSX closing down.

 

Find the [Programs] section in fsuipc4.ini and create the following entry. You may need to adjust the number before = if you already have programs started this way.

 

[Programs]
RunIf1=Ready,Close,"C:\Program Files (x86)\FSPS\FSX Fiber Accelerator\FSX Fiber Accelerator.exe"

 

Make sure you place quotes around the path (as it contains spaces) and refer to the FSUIPC documentation for more detailed info.

 

It then ensures that you can never close FSX whilst FSX FA is still running. :smile:

Just tried the Demo and oddly enough I was impressed, took my normal benchmark setting and increased FPS 25%.

Given the importance of FSX FA terminating before FSX I think it's worth reiterating that for those of you who have a registered copy of FSUIPC4 you can place an entry in fsuipc4.ini that will start the program once FSX has loaded and terminate it prior to FSX closing down.

 

Find the [Programs] section in fsuipc4.ini and create the following entry. You may need to adjust the number before = if you already have programs started this way.

 

[Programs]

RunIf1=Ready,Close,"C:\Program Files (x86)\FSPS\FSX Fiber Accelerator\FSX Fiber Accelerator.exe"

 

Make sure you place quotes around the path (as it contains spaces) and refer to the FSUIPC documentation for more detailed info.

 

It then ensures that you can never close FSX whilst FSX FA is still running. :smile:

 

Hi Ray,

 

Thanks a lot for this, but I can't get RunIf to do anything. I've verified the path, and checked the docs, but the only way I can seem to get Fiber to start is if I use Run1 (with no options of course). Any idea what might be wrong?

 

Thanks!

John Francis