Couatl crahes ---HELP---

[Justin133]

Hello,

I have problems with my GSX for months now, scince I installed the update for Aerosoft's Mega Airport Prague, my GSX crahes every time after starting it.

I deleted everything about Prague and also files into ProgramData folder and more.

GSX is up to date and I also installed the last standalone Addon Manager.

I even deleted the coutal folder into ProgramData under Virtuali more than once.


Please, please help me. I'm getting sad and angry...

[virtuali]

I have problems with my GSX for months now, since I installed the update for Aerosoft's Mega Airport Prague, my GSX crahes every time after starting it.

You mean you didn't had this before, and it started after that update ?

Does it happen if you are on another airport ?

Please, please help me. I'm getting sad and angry...

Well, I would be angry too, if installing an airport caused problems to another program...

[Justin133]

Right. I have this problem scince I installed it. This was last summer but I already deleted everythin of Prague.

It happens at every airport. With addon or without.

[virtuali]

This was last summer but I already deleted everythin of Prague.

Are you sure you removed everything ? I seem to recall that airport has its own software module, which cannot be removed by simply removing the scenery folder.

[Justin133]

Yes I looked once again, it's all clear.

Now does it show me the error even after starting a flight, before it shows me the error after selecting Deboarding or something like that.

[virtuali]

Now does it show me the error even after starting a flight, before it shows me the error after selecting Deboarding or something like that

Then it must be some other module, which cause a conflict similar to the one that came with the Prague airport. Do you have Ezdok camera maybe ? Some users reported that some versions of it conflicted with GSX, causing that error.

[virtuali]

Since the last update of the "Standalone Addon Manager" i get this message


  File "couatl\GSX\assistanceServices\__init__.py", line 825, in do
AttributeError: 'module' object has no attribute 'gsx'

[virtuali]

Since the last update of the "Standalone Addon Manager" i get this message

The problem is not caused by the update, it's caused because you must have disabled GSX from its menu.

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.

P.S.
I removed your post by mistake, that wasn't intentional, but I kept the quoted part.

[Matteng]

That was it  Thanks for the quick help.

Best regards  Matthias

[Justin133]

Now I get a new error 

SODE is already running. But when I open the Task-Manager, the SODE isn't running.

[virtuali]

SODE is already running. But when I open the Task-Manager, the SODE isn't running.

Yes it is, check better. Or maybe, it was, when it displayed that error, but then it crashed immediately. Best to restart Windows.

[Justin133]

I've restart windows and Task Manager SODE tells me, it's not running before open the sim, after the error is one SODE into the chart, after closing the sim, ´the SODE is closed too.

[virtuali]

I've restart windows and Task Manager SODE tells me, it's not running before open the sim, after the error is one SODE into the chart, after closing the sim, ´the SODE is closed too.

Maybe you have two copies of SODE installed in the EXE.XML file ? In any case, the problem it's totally unrelated to GSX. Maybe you installed an old version of SODE, which came with another scenery, so you must remove the extra one.

[Justin133]

I try it once again.

I deleted the exe.xml and dll.xml, also deleted Ezdok.
Next I restarted P3D (v3) again, and the SODE error is gone, but GSX still crashes after open the menu.

So Ezdok is not the problem. 

[virtuali]

I deleted the exe.xml and dll.xml, also deleted Ezdok. Next I restarted P3D (v3) again, and the SODE error is gone

So, this confirms the SODE error was a problem with your XML, that didn't had anything to do with GSX.

but GSX still crashes after open the menu.

That's ANOTHER, entirely different problem now. What do you mean with "crashes" ? Do you have an error log from GSX ? If yes, what does it says ?