FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: azragod on July 10, 2016, 12:48:55 pm
-
Hi all,
Like many other users said in many other forums, after last update, GSX doesn't appear in addon-menu. First error was the already explained "unknown add-on error", so I manually updated GSX (stand-alone manager). No more succes.
I already tried to :
uninstall all, re-install, restart all, de-activate and re-activate from addon manager (which unistalling and reinstalling worked well...), nothing works. Couatl.exe still not running.
I also could see that nothing relevant was written on de dll.xml file.
So, also tried to add manually the lines :
Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
But no more succes so far...
Any idea ?
Thanks for reply.
Lionel
-
Just tried to launch couatl.exe manually (from Prepar3d\fsdreamteam\couatl folder) after P3D start, and suprise... It works now ! But P3D still don't run it automatically.....
Lionel
-
I cannot be sure if your EXE.XML is correct. It's surely wrong as you posted it, since it's missing an opening tag. If the EXE.XML has an error, the sim will ignore it entirely.
Also, if you use P3D, the correct place for the file is the %PROGRAMDATA%\Lockheed Martin folder, not the %APPDATA%\Lockheed Martin folder
-
Thanks for your reply, but...
The FACT is that everything worked well before your last update.
Problems came WITH and because of your update.
It's quite annoying, at least, that your customers have to check all their system and find by themselves where your program made errors.
Please don't invert responsabilities.... and please work on your update program which cause these problems to finaly fix them !
Thanks.
Lionel
-
The FACT is that everything worked well before your last update.
Problems came WITH and because of your update.
You are confusing the effect with the cause. What you are labeling as "fact", it's what is happening now, so it's the effect. But it's not what has CAUSED it.
It's quite annoying, at least, that your customers have to check all their system and find by themselves where your program made errors.
According to your own report, you first had this error:
First error was the already explained "unknown add-on error"
Which is caused because you haven't updated the software when prompted.
Then, you have the issue of the Couatl.exe which doesn't start automatically, but it WORKS if you start it manually (always according to your report, so I guess the initial error is gone, right ? ) AND you posted an XML that, as you posted it, is surely wrong, because it's missing an opening tag.
This will explains exactly why the sim doesn't launch it automatically but of course, since (as I've said) I cannot be sure if your EXE.XML is correct, but It's surely wrong as you posted it, since it's missing an opening tag, what other options I have, other than suggesting a fixed based on what data YOU are supplying here ?
Please don't invert responsabilities.... and please work on your update program which cause these problems to finally fix them !
That's precisely the mistake you did: inverting responsibilities. I already clearly indicated a possible reason of the problem, which seems to be caused by a problem in the XML file, assuming you posted it as it is, which is not even certain.
And, as I've said, if you use P3D 3.x, the correct place for the file is the %PROGRAMDATA%\Lockheed Martin folder, not the %APPDATA%\Lockheed Martin folder, this just to be sure you are looking at the correct file.
-
Just updated to last version, same issue.
Once again, this problem came with your update.... My system worked perfectly before and supported previous updates, even with lots of other add-ons installed, setted up and so.
As usual, I'll do by myself and find alone what is wrong. Obviously, your program did (or didn't) changes in .xml or .cfg or whaterver other files.
As customer, I'm disappointed. Blaming your users is quite simple. Thinking about errors and word on fixing them could be better. Don't worry for me, I'll find a solution, goggle is my friend and hopefully the simmers community is really more objective. I just hoped that reporting bugs and errors could help you to fix your bugs and errors.
What a poor support....
Regards.
-
Just updated to last version, same issue.
What do you mean with "same issue" ? The "unknown program" error, or the fact the program doesn't start automatically with the sim ?
From your initial report, you said you ALREADY "updated to last version" and this should have fixed the first error (which was caused by the fact you never updated in the first place when notified).
If the "same issue" now is the program doesn't start automatically, but otherwise works if started manually, this WON'T be fixed by "updating to the last version", simply because it's nothing that we could or should fix in the first place so, if this is the issue, why you updated again, instead of posting your XML files, so we could check them ? The file WAS surely wrong as you posted it, but I already explained why it's best if you posted the actual file, not just copying it manually a part of it in the message.
Once again, this problem came with your update.... My system worked perfectly before and supported previous updates, even with lots of other add-ons installed, setted up and so.
Stop repeating this. You are again confusing the effect with the cause.
As usual, I'll do by myself and find alone what is wrong.
So you'll maybe find what you did wrong. Like having edited the xml file manually trying to fix the problem, for example.
Assuming your XML file IS really as you posted it, which I cannot possibly be sure of this unless you posted the ACTUAL file, instead of copying & pasting it on the forum message, since you might have simply made a mistake (it's easy to make mistakes...) copying it in the forum, but the file is otherwise fine.
So, again, I based my reply on what data YOU supplied, which was a corrupted XML file, and this is consistent with the issue you reported, that the program RUNS FINE when started manually, but doesn't start automatically.
Obviously, your program did (or didn't) changes in .xml or .cfg or whaterver other files.
"Obviously" not.
The installer surely changes the xml, but it will NOT corrupt it!! It only uses the official XML routines that are in Windows to add/remove sections from it, and it won't dare touching it if there's already a problem with it.
There has been several reports here of OTHER adons corrupting the xml files in the forum, but NOBODY ever reported an xml file corrupted by any of our installers.
As customer, I'm disappointed. Blaming your users is quite simple. Thinking about errors and word on fixing them could be better. Don't worry for me, I'll find a solution, goggle is my friend and hopefully the simmers community is really more objective. I just hoped that reporting bugs and errors could help you to fix your bugs and errors.
Everybody knows that we always fix what SHOULD be fixed by use. This problem is NOT something that has anything to do with any of our software.
Of course, if you took the time to post your XML files properly, which means ZIPPING them together, and ATTACH them to a post, I could have a look at them, and CONFIRM if this was really a "corrupted XML" file problem.
And as I've said, several times, we are not even sure that what you posted is the file *actually* used by the sim.
1) Be sure you are looking at the EXE.XML file in the %PROGRAMDATA%\Lockheed Martin folder
2) DO NOT copy it in a post. ZIP the file (perhaps together with the DLL.XML too), and use the "Attach" function of the forum to Attach it to a message, this way I can be sure I'm looking at your ACTUAL file, as it is, instead of the part that you copied it in the forum.
THEN, after we assessed whether the problem is a problem with the XML file OR it's something else, we can start CONTINUING in the Troubleshooting process, that will eventually find what's wrong in your system that is preventing the program to start automatically, assuming THIS is still the problem you are having now.
-
Of course, if you don't want to do all of this, we can always have the option to have a Teamviewer session, so I can check your system directly, and fix it in no time, and show you what the real problem was to begin with.
Send me a PM ( Private Message in the forum ) or an email, and we can arrange this.
-
Dear Support!
I have the same issue, since the last update the gsx is not working. It's unable to open the gsx window with the CTRL+SHIFT+F12, and from the Add-ons - GSX - Show GSX menu.
I tried to uninstall and reinstall, but nothing changed.
How can we solve this, what do you need from my side?
Thanks in advance
Charles
-
I have the same issue, since the last update the gsx is not working. It's unable to open the gsx window with the CTRL+SHIFT+F12, and from the Add-ons - GSX - Show GSX menu.
You don't have the "same" issue. The OP said it cannot get the Couatl program starting automatically with the sim, while you clearly have it running, otherwise you wouldn't have the GSX menu under "Addons", which clearly indicates everything started properly.
Instead, your issue is one that has been discussed so many times already on the forum and it's not a GSX problem. It's a P3D 3.x installation bug that is very well known but still hasn't been fixed yet.
If you upgrade P3D using the "Client" installer, NO 3rd party application with a menu will work, because the Client installer is missing some files in the sim that needs to be updated. To fix this, you must install the P3D "Content" or the FULL P3D installer.
-
Im having the exact same problem, i do favor its in the update, ive tried opening it manually still didnt work. i did just install AS2016 idk if that can be the problem
-
Is there a fix being made as I have the issue where its in my menu but CTRL F12 wont open anything? And I have checked all the content re done that used the full P3D installer. I am annoyed as I haven't been able to fly with realism since the new update.
-
i did just install AS2016 idk if that can be the problem
One user here reported a problem caused by AS2016, maybe a key conflict:
http://www.fsdreamteam.com/forum/index.php/topic,14071.0.html
Another user here reported the XML file being corrupted after installing AS2016:
http://www.fsdreamteam.com/forum/index.php/topic,14044.msg104015.html#msg104015
I haven't verified this, just linking what users are reporting.
-
Is there a fix being made
You mean a fix for P3D made by LM to fix the problem caused by the Client installer not updating the menu system ? We don't know, but we can only hope...
as I have the issue where its in my menu but CTRL F12 wont open anything? And I have checked all the content re done that used the full P3D installer.
With "won't open anything", you mean any 3rd party application with a menu ? That's precisely what the problem is.
I am annoyed as I haven't been able to fly with realism since the new update.
Sure, we are as annoyed as you, because users are mislead thinking this is something that has something to do with GSX, when in fact it's a P3D installation bug.
Assuming, of course, you REALLY have the SAME problem discussed here, which is:
- GSX menu visible under "Addons"
- No transparent in-game menu when pressing the default GSX hotkey or when selecting to start GSX from the "GSX" menu too.
If, instead, you don't even have the GSX menu under the "Addons" menu, that's an entirely different issue, and it indicates GSX hasn't started.
-
No transparent in-game menu when pressing the default GSX hotkey or when selecting to start GSX from the "GSX" menu too.
That is my issue :-)
If it helps this is what the panic log says
couatl v3.1 (build 3467)
panic log started on Wed Jul 20 11:36:18 2016
problem raised by engine or unspecified addon
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: Bad magic number in C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\fsdreamteam\couatl\wx\__init__.pyc
Application aborted because of a Python error
{}
-
No transparent in-game menu when pressing the default GSX hotkey or when selecting to start GSX from the "GSX" menu too.
That is my issue :-)
If it helps this is what the panic log says
couatl v3.1 (build 3467)
panic log started on Wed Jul 20 11:36:18 2016
Your version is outdated. Download and install the latest Stand-Alone Addon Manager or the latest GSX Full installer.
-
Ok and if it doest work I shall send you the panic log again :-)
-
Still not working. I honestly have no clue what is going on. I don`t even have a panic log file now... Just CTRL F12 doesn't open the menu I have tried updating Content in P3D and reinstalling it. I have tried firewall on and off I have tried changing the keys from CTRL f12. I have tried possible everything removed AS16 from my system. I am now stuck is there anyway you guys could come on teamviewer and give us a hand?
-
I don`t even have a panic log file now...
Which seem to indicate it's working now. Do you still have BOTH Couatl and GSX in the "Addons" menu ?
-
Yes but cant open the menu with the short cut keys CTRL F12 or via the menu
-
Yes but cant open the menu with the short cut keys CTRL F12 or via the menu
This clearly indicates the problem is the P3D Content not being installed. If you want further confirmation about this, try the following:
- Go to a Parking with the standard "Go To Airport" menu.
- Shut off the engines, but keep the Parking Brakes OFF.
- Presse CTRL+Shift+F12 to call GSX. If you see a message in red saying you must set the Parking Brakes, it means GSX IS WORKING, it's just the sim that cannot open the menu, because you haven't installed the Content.
-
Yes I am getting the message to set the parking breaks.
So what is the next step regarding content. I have already installed it via p3d :-/
-
I tried content again and it didnt work :-(
-
ok i got AS2016 to work since lcouds didnt appear. I went and checked every line for gsx that I can possibly think of that I can access through notepad, and everything looks correct. It may just be that gsx may not be compatible with V3.3.5, or there is a line that needs to be changed to make it compatible.
-
ok i got AS2016 to work since lcouds didnt appear. I went and checked every line for gsx that I can possibly think of that I can access through notepad, and everything looks correct. It may just be that gsx may not be compatible with V3.3.5, or there is a line that needs to be changed to make it compatible.
I dont know what is going on. It is a shame :-(
-
It may just be that gsx may not be compatible with V3.3.5, or there is a line that needs to be changed to make it compatible.
GSX is perfectly compatible with P3D 3.3.5, that's the version everybody at FSDT uses. Please try to do the test as I've indicated above.
-
Yes I am getting the message to set the parking breaks.
This a 100% clear confirmation that GSX is working correctly.
What is not working, is the P3D menu, which is not a "GSX menu", it's the standard P3D menu, which is broken because of the incomplete installation.
Want even more proof ? Is the SODE ( Use TAB-S to call it ) menu working ?
So what is the next step regarding content. I have already installed it via p3d :-/
Installing the Content is the only known solution that is confirmed to be working for everyone. If it's not working for you, try with the full 3.3.5 P3D installer.
-
I have the same issue, since the last update the gsx is not working. It's unable to open the gsx window with the CTRL+SHIFT+F12, and from the Add-ons - GSX - Show GSX menu.
You don't have the "same" issue. The OP said it cannot get the Couatl program starting automatically with the sim, while you clearly have it running, otherwise you wouldn't have the GSX menu under "Addons", which clearly indicates everything started properly.
Instead, your issue is one that has been discussed so many times already on the forum and it's not a GSX problem. It's a P3D 3.x installation bug that is very well known but still hasn't been fixed yet.
If you upgrade P3D using the "Client" installer, NO 3rd party application with a menu will work, because the Client installer is missing some files in the sim that needs to be updated. To fix this, you must install the P3D "Content" or the FULL P3D installer.
Thank you for your help, It worked until today. I got a message, that the couatl has a newer version, and I updated. After this I always get this error log, which I attached.
How can we solve this?
Thanks in advance
Charles
-
Same issue here. GSX worked fine prior to installing the latest update (I do not have AS2016).
When I load my flight, P3D starts building the scenery cache and then I receive an error message The addon <unknown> is causing the Couatl Scripting Enge to restart.
There error log is as follows:
couatl v3.1 (build 3487)
panic log started on Fri Jul 22 19:19:51 2016
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 1193, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 832, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 471, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 732, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 609, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 281, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\__init__.py", line 104, in onSimStart
NameError: global name 'getAvatarId' is not defined
None of the other suggestions seemed to have worked.
Any ideas?
-
Same problem got in sim message saying Couatl needed updating after updating and restarting couatl got this message.
couatl v3.1 (build 3516)
panic log started on Sat Jul 23 21:24:39 2016
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 1193, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 832, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 471, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 732, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 609, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\fsm.py", line 61, in switchToState
File "couatl\GSX\assistanceServices\__init__.py", line 281, in enter
File "couatl\GSX\assistanceServices\__init__.py", line 91, in setVarRequestable
File "couatl\common\__init__.py", line 104, in onSimStart
NameError: global name 'getAvatarId' is not defined
{}
Any help would be appreciated.
-
Same problem got in sim message saying Couatl needed updating after updating and restarting couatl got this message.
couatl v3.1 (build 3516)
NameError: global name 'getAvatarId' is not defined
Already discussed and answered here: you haven't updated the Stand-Alone Addon Manager when prompted:
http://www.fsdreamteam.com/forum/index.php/topic,14129.msg104368.html#msg104368
-
I will try this again tonight and see if it resolves the issue.
Regards,
-
I installed the stand alone manager and now when I start P3D, I get the following error message.
Couatl Scprting Engine for FSX/ESP has stopped working.
Problem signature:
Problem Event Name: APPCRASH
Application Name: couatl.exe
Application Version: 3.1.0.3527
Application Timestamp: 57923ce0
Fault Module Name: StackHash_0a9e
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 7ebd001c
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
-
I installed the stand alone manager and now when I start P3D, I get the following error message.
Couatl Scprting Engine for FSX/ESP has stopped working.
Problem signature:
Problem Event Name: APPCRASH
Application Name: couatl.exe
Application Version: 3.1.0.3527
Your version is newer that the one you had before, but is still outdated.
You must have installed the Stand-Alone Addon Manager earlier today, since we just had another update today, so you still got the outdated version.
That doesn't mean the old version you have was "supposed" to crash, because it generally didn't, but we found and fixed another possible chance of crashes (on exiting the sim), so it's possible that, even if we cannot replicate a crash on startup, it might be possible the current version fixes a crash on startup that, is happening on your system only.
So, install the Stand-Alone Addon Manager now, in order to get the current version.
-
As a matter of fact, it was earlier today.
Downloaded and installed again and everything seems to be working now. :)