FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: brian747 on September 27, 2013, 12:18:44 pm
-
Hi!
I have a weird problem since I installed v1.8: suddenly the pushback happens as usual, but the staff and vehicles doing it are invisible.
Boarding, cargo handling, and so on don't seem to be affected: those vehicles and personnel are reassuringly present.
The only other strange thing I have noticed is that I have searched my entire C: drive and I can't find a gsx.cfg file anywhere, but I don't know whether I had one previously.
I did try running the vehicles update as well, and also a full reinstall of the AddonManager (which confirms that the product is ACTIVE), but with the same result.
Any advice would be most welcome! :)
Cheers,
Brian
-
I have a weird problem since I installed v1.8: suddenly the pushback happens as usual, but the staff and vehicles doing it are invisible.
Doesn't happen here, and can't be possibly related to the update, since nothing at all has changed in the pushback.
That's not of course anything related to activation of the Addon Manager or anything like that. Without activation, GSX would work in full at the Trial or FSDT airports only, and if there was a problem with the software not running correctly (like antivirus, or similar) nothing would work.
It's not a GSX.CFG issue either because, the only thing a GSX.CFG for an airplane controls in the pushback, is the nose distance to set the truck attach point.
Invisible objects are usually caused by video settings, problems with tweaks, video memory corrupted, too much vram used by other add-ons, etc. Fact that you noticed after the update was just a coincidence.
Try to remove your FSX.CFG located under %APPDATA%\Microsoft\FSX so FSX will rebuild it with default settings. Apply only the HIGHMEMFIX tweak.
-
Thank you for your swift reply, Umberto! :-)
Yes, understood: it looks like something seriously wacky is going on. The only problem is that as far as I can see (so far) it's the *only* weird thing..... 8-\
Anyway if/when I can find out what fixed it, I'll post back here.
Cheers,
Brian
-
This was solved by a *complete* (i.e. not just the AddonManager) uninstall and reinstall.
Cheers,
Brian