Developer's Backdoor > GSX Backdoor
How to avoid building airport cache?
virtuali:
--- Quote from: GerdD on June 01, 2013, 03:05:12 pm ---I cannot accept explanations who do not help in solving the problem I had.
--- End quote ---
The explanation I've given you have the one and only purpose to explain you don't have any "problem" to begin with. As I've said, what triggers the constant cache rebuild is (according to YOUR description ) your changes to the Scenery Library.
And, this is obviously a FACT, if you change the Scenery Library, FSX WILL REBUILD ITS OWN CACHE TOO, REGARDLESS IF GSX IS INSTALLED, so your "problem" is not a problem in the first place: if you don't like a cache rebuild, even if you keep changing the Scenery Library (which is what you said), this is what FSX does, with our without GSX.
--- Quote ---If You do not believe what I am telling You,
--- End quote ---
I've done way more than this: I offered you to CHECK your system directly, to prove you what's happening and why.
--- Quote ---You can believe or not that after Installation and de-Installation with the latest download the complete gsx-folder in cuoatl-folder will remain here. Including the __init__.pye file! And I do not use P3D.
--- End quote ---
No, it doesn't. I'm fairly sure of that, because I've obviously tried it, just before replying to you. Installing GSX, the Uninstalling it, REMOVES the GSX files that allows GSX to start, they might left the folder there, but without the __INIT_.PYE, GSX will not start.
--- Quote ---I do not think a Teamviewer session between both of us makes much sense cause everything is fine for me now and I do not need any further explanations.
--- End quote ---
A Teamviewer session would simply prove the __init__.pye WILL be removed, and it was ME that offered to do it, and It's YOU that are refusing it, and this is of course quite telling: while I'm sure the uninstaller uninstalls GSX, it would be still interesting to know WHY it doesn't on YOUR system, which obviously means I believe you, but that doesn't mean the installer is "at fault", just there might be an unknown factor in your own system, which might prevent the uninstaller to work as it supposed to do, and by refusing to do a session, you are doing good to nobody, because you would never discover a possible issue with your system, and you are preventing us to eventually fix a problem that might be similarly happen to another user.
Hnla:
--- Quote from: GerdD on May 31, 2013, 07:13:38 pm ---This Forum should be a Helpdesk.
--- End quote ---
??? Getting an actual person is 900X better to personally offer support and answer your questions directly. Especially with such promptness!
Navigation
[0] Message Index
[*] Previous page
Go to full version