FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: VinceAK on February 06, 2017, 10:32:27 pm
-
I was trying to test some sceneries so I tried to disable GSX. Right after I did that it threw me the "addon <unknown> is causing Coualt Scripting Engine to restart" and there's no way I could restart it. Everytime I tried to restart it gave me the same error. Here's the error log
couatl v3.1 (build 3625)
panic log started on Mon Feb 06 12:26:11 2017
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 73, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\__init__.py", line 825, in do
AttributeError: 'module' object has no attribute 'gsx'
{}
-
his error is really puzzling, it shouldn't happening, because it looks like you haven't GSX installed. Are you sure you installed GSX and not just the Addon Manager ? Maybe you removed it and then reinstalled the Addon Manager without GSX ?
-
Exact same problem as i was getting. After re-install that error is gone but i cant use GSX
-
Could you please check if you disabled GSX, maybe when trying to get rid of the problem ? It can be done with the GSX menu, by choosing the "Disable addon" menu option.
Of course, if you disabled it, it would not be possible to access the GSX menu now, but that setting is saved in this file:
%APPDATATA%\Virtuali\Couatladdons.ini
See if you have these lines near the start:
[gsx]
disable = 1
and change it to
[gsx]
disable = 0
Then start FSX again.
-
I'm certain that GSX was installed because right before I disabled it, I used the follow me and unload the plane. I disable it using the "disable addon" under GSX menu.
I ended up restored my computer to an earlier point and reinstall GSX. After I got that error I tried uninstall and reinstall GSX and it gave me error during installation.
-
Please check my previous reply.
-
I have the same issue in FSX. I reinstalled full version of GSX and stand alone addon manager. My GSX is enabled. I also set full ownership of the FSX folder and Virtuali folder. The message still came up and cannot run GSX in FSX. Please help! Thanks.
-
I have the same issue in FSX. I reinstalled full version of GSX and stand alone addon manager. My GSX is enabled. I also set full ownership of the FSX folder and Virtuali folder. The message still came up and cannot run GSX in FSX. Please help! Thanks.
I can only repeat and confirm, the only possible reason why you have that message, is because you disabled GSX. See the above post for instructions how to enabled it back:
http://www.fsdreamteam.com/forum/index.php/topic,15100.msg109785.html#msg109785
-
Hi there
After install the new version , when I disable GSX from the menu, the Enable from the add-on menu disappeared.
The previous version show the Enable
-
After install the new version , when I disable GSX from the menu, the Enable from the add-on menu disappeared. The previous version show the Enable.
The whole point of the solution suggested in the thread linked above, is precisely because, after that error, you don't have the Enable option, which is why, you MUST set the "Disable = 0" line in the Couatladdons.ini file manually.
-
starting with Disable = 0
http://imgur.com/a/cDgNL
press the Disable
http://imgur.com/a/5G0CU
Causing Error
http://imgur.com/a/FE95R
No GSX
http://imgur.com/a/74W43
now i have to close the P3D and change
Disable goes to 1
http://imgur.com/a/K5Vla
its no making sense that everytime i need to change in the file
thx
-
its no making sense that everytime i need to change in the file
As your screenshot shows, it's you that Disabled GSX so, as I've said, you you Disable it, you MUST edit the Couatladdons.ini file to re-enable it! As I've said, that was precisely the reason why I told you to look that post: if it was possible to Re-enabled it by the menu, I would have told you to do so.
-
Hi
Fist I want to thank you for your response.
Second I know I disabled. But I mentioned that before the new version of GSX , after disable I could Enable it from the add-on menu , and not by configuration the ini file
-
But I mentioned that before the new version of GSX , after disable I could Enable it from the add-on menu , and not by configuration the ini file
But since you have reported an error, I told you exactly how to fix it. We'll probably remove the ability to disable from the menu altogether, because it's only confusing.
-
OK . i understand the issue.
But i want to write the 2 Use-cases why i use the Disable and Re-Enable Feature and if you can solve them for me.
First Issue
-------------
on airport that has not jetways )Sleeve plane( by Ctrl+J,
causing that the PUSHBACK Doesnt work.
to solve it i have to set on Customized-> Parking has Jetways
and to activated i use the Disable and Re-Enable Feature.
Second Issue
-------------
On PMDG Boeing 777
the Boarding feature doesnt stop
so i use the Disable and Re-Enable Feature
THX
-
But i want to write the 2 Use-cases why i use the Disable and Re-Enable Feature and if you can solve them for me.
Both issues could be handled in a much better way than disabling GSX.
on airport that has not jetways )Sleeve plane( by Ctrl+J,
causing that the PUSHBACK Doesnt work.
to solve it i have to set on Customized-> Parking has Jetways
and to activated i use the Disable and Re-Enable Feature.
I don't understand you very well. What's the "Sleeve plane" feature (maybe you wanted to say "Slew"), and what it has to do with the jetways ?
Surely Pushback works with all parkings, not just those with Jetways.
Maybe you are referring to a 3rd party airport which has mistakenly set the Pushback preference to "None" at all parkings ? But you should at least have a Straight pushback option in this case, and you can of course change the Pushback preference in GSX.
So, please, report where this is happening, and clearly indicate the scenery used.
the Boarding feature doesnt stop
so i use the Disable and Re-Enable Feature
Boarding surely stops on the PMDG-777. Could be you set a very long boarding time per passenger, so it's taking lot of time ? Please clarify how this happens.
But regardless of the issues, you should NOT "Disable" GSX entirely.
If you have a problem with a particular airport, you can disable the AIRPORT on GSX, as explained in the manual, using the "disable_on_airports" line in the Couatladdons.ini file.
If you have a problem with GSX being "stuck" in some kind of situation you think you cannot escape, you should "Restart Couatl" instead, NOT Disable GSX.