Developer's Backdoor > GSX Backdoor
GSX Disappearing **SOLVED**
Fenchurch:
Well it's not just GSX, I've tried some FSDT sceneries in P3D2 and all I can see are aircraft and jetways, so I hope something can be done. I have confidence. ;)
The AddonManager installer moved my airports to its own folder and updated my FSX scenery.cfg, but didn't update my P3D scenery.cfg file. I fixed that in a few seconds with some Find and Replace though.
I've zipped a log file for the Couatl problem with GSX, along with a log for my attempt to launch at CYVR. This -GSX log mentions an error creating 'FSDT_Traffic_Cone1', but I've seen references to 'FSDT_Traffic_Cone3' too.
I've checked the new SimObjects folder and there are three models of FSDT_Traffic_Cone present.
My Prepar3D.CFG has two entries pointing to the new Simobjects\Misc folder. Are these correct and are both needed?
SimObjectPaths.6=C:\Program Files (x86)\Addon Manager\Simobjects\Misc
SimObjectPaths.1=C:\Program Files (x86)\Addon Manager\Simobjects\Misc
Regards,
virtuali:
It seems you are not using the current version of the GSX installer. Download it again now and try again.
It's not normal the sceneries weren't added to the scenery.cfg, so it was probably already corrupted (the installer won't touch a file that is not clean), and the same seems to be valid for the prepar3d.cfg, because there shouldn't be two lines for the simobjectpaths, so one of them is wrong.
I would suggest removing both of them and reinstall again (using only the current installer), but it's difficult to say if it will work, without looking at your existing scenery.cfg and prepar3d.cfg files.
bvanhout:
Well as a developer surely you should provide support for all previous products, so I suggest someone get P3Dv2 working again.
You have obviously changed something, I have changed nothing.
Solution please, not a shrug of the shoulders..................
bvanhout:
These are the last lines of the error message created.
virtuali:
--- Quote from: bvanhout on June 10, 2017, 03:07:04 pm ---Well as a developer surely you should provide support for all previous products, so I suggest someone get P3Dv2 working again.
--- End quote ---
And we obviously do, of course. I just reinstalled P3D V2 now and as expected, GSX worked flawlessly at the first try. So yes, it's confirmed the only possible reason for this error, is that some of your configuration files was already corrupted before installing it.
Which is why I said:
--- Quote ---but it's difficult to say if it will work, without looking at your existing scenery.cfg and prepar3d.cfg files.
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version