FSDreamTeam forum
Developer's Backdoor => GSX Backdoor => Topic started by: bvanhout on June 02, 2017, 09:17:15 pm
-
Every time I open into P3D v2, GSX is nonexistent.
I have tried reinstalling the programme from the latest version as of today.
I have reinstalled the addon manager.
I have tried reactivating GSX with my product code but all to no avail.
-
Do you have both the Addon Manager and the Couatl menus under the "Addons" menu ?
-
Only Addon manager even after reinstalling GSX
-
Uninstalled Couatl, Addon manager, GSX and SODE and reinstalled latest versions of all.
GSX works fine in FSX, but continues to give an error in P3D v2.
Image and error doc attached.
-
Have reinstalled the stand alone Addon manager and to no avail.
This error message continues to appear.
Solution?????
-
Solution?????
Try to add the whole Addon Manager folder to the antivirus exclusions list.
-
I will try this but the programme works perfectly with FSX.
I have FSX and P3D v2 on the same machine.
-
Could you please post your Prepar3d.cfg file ? ZIP it at Attach it to a message, don't copy in the message text.
-
Config file.
-
You can enable logging without being able to access the GSX interface, this way:
open the Notepad and type the following on a new blank file:
logFile=couatl.log
(please note logFile is written beginning with a lower case l and a capital F )
Save the file as couatl.ini in the %APPDATA%\Virtuali folder, run the sim and then exit after it finished loading. Check your %APPDATA%\Virtuali folder and if there's a Couatl.LOG file there, then send it to me same as the .cfg file.
-
Log file
-
What's your Prepar3D version, exactly ?
-
2.5.12946.0
-
Hello,
I have this issue as well. GSX 2.0 loads in my FSX-A, but I have the Couatl issue with my P3D2 version 2.5.12945.0.
Would posting my Couatl log be of any interest?
-
Possibly, but I can tell you that we might not be able to fully support you, since nobody at FSDT still has P3D 2.5 installed.
-
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,
-
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.
-
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..................
-
These are the last lines of the error message created.
-
Well as a developer surely you should provide support for all previous products, so I suggest someone get P3Dv2 working again.
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:
but it's difficult to say if it will work, without looking at your existing scenery.cfg and prepar3d.cfg files.
-
Again:
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.
-
I have sent you the P3D config file, you have not asked for the scenery config file before.
-
Scenery config file.
-
I have sent you the P3D config file
No, you haven't. You only posted two lines of it, sent two logs and an error log, and a scenery.cfg in your last post.
you have not asked for the scenery config file before.
Yes I have, twice.
-
Your scenery.cfg seems fine, but there aren't any fsdreamteam areas in there. Do you use the Migration tool ? Since your error seems to indicate problem with the Prepar3d.cfg, if you are using the P3D Migration tool, maybe you are having the same problem discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,15816.msg114233.html#msg114233
I just had a longer TeamViewer session yesterday with a user having a similar problem, only to find out that this Migration Tool has severely messed up the simobjects.cfg/prepar3d.cfg which confused the SODE Platform Manager totally.
Using the Migration tool on proper P3D installers, will surely result them to fail.
-
You requested logs and error messages and then in entry 7 the p3d.cfg file
I sent you the P3d.cfg as an attachment. When I download it from that entry it shows the whole config file, not just 2 lines.
Please refer to the entries where you asked for the scenery.cfg file.
You requested the scenery config file for the first time in reply 19 and I sent it right after that. ???
-
I have removed GSX, SODE and the Addon Manager from the PC, plus all related folders.
I have used the original scenery config file with no addon scenery and allowed P3D to rebuild the config file from new.
I still get the same error message when trying to use GSX.
-
Ok, I found the problem, it was P3D V2 which wasn't correctly detect by the installer. Fixed by downloading and installing the current Stand-Alone Addon Manager now.
-
Thank you GSX working now.