Where to find the previous version ?

[LSGG]

Hello,

Where may I find the previous version ?
Thanks
Michel

[RoughLanding]

If you updated the most recent version, back dating to a previous version will not help, the error will still show up.

[iMove Quick]

Not if the problem/bug came with the latest update. Because the latest update gave me to many headache's. Still can't use GSX.

[virtuali]

What problem ? The one that has been discussed and answered here ?

http://www.fsdreamteam.com/forum/index.php/topic,15020.msg109299.html#msg109299

[Daniel.Burke01]

I rolled back to a previous version I had in August, and I still have the issue.  That version worked fine then, so it must be something the installer is picking up in the "live update" portion of the install as I noticed things like the Deicing pads installing in both the old version and this version, but they didn't exist when the August version came out.  I would double check to see what is and isn't being installed in each version as that will at least help pin point what the issue might be.

Thanks,
-Dan-

[iMove Quick]

What problem ? The one that has been discussed and answered here ?

http://www.fsdreamteam.com/forum/index.php/topic,15020.msg109299.html#msg109299

No, it's related to FSX, not p3d. For the last few days I've been getting the bglmanx.dll error at start up. Tried alot, rolling back to older version, using older version of bglmanx.dll, but then gsx and the addon manager didn't show up.

Soo....I'm kinda stuck now.

[Daniel.Burke01]

Hey guys, If you have an older version of GSX, turn off your internet connection and run your previous version installer.  This worked for me.  Something is being pushed to the FSDT installers through the live update portion of the installation that is causing the issue.  I was able to bypass this part of the installation with my internet off and restored GSX to the last version that was available.

Thanks,
-Dan-

[virtuali]

And as replied in many other threads, I asked to to contact me in private to arrange a Teamviewer session, because it's the only way I could see what's the problem in your case, since we are still unable to reproduce it in any way.