FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Justin133 on February 08, 2017, 05:28:28 pm
-
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...
-
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...
-
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.
-
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.
-
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.
-
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.
-
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'
-
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.
-
That was it :) Thanks for the quick help.
Best regards Matthias
-
Now I get a new error >:(
SODE is already running. But when I open the Task-Manager, the SODE isn't running.
-
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.
-
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.
-
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.
-
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. ???
-
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 ?
-
I wrote it down on the first post up here :D
-
Now I selected the parking position inflight and it shows "A marshaller...bla bla is ready or something like that" and after landing I get the error again.
-
Now I selected the parking position inflight and it shows "A marshaller...bla bla is ready or something like that" and after landing I get the error again
Your error shows GSX wasn't able to create an object which is of course included with it so, it cannot happen, unless your FSX.CFG file has been corrupted, with missing/corrupted SimobjectPaths, so you are missing hundreds of default library objects too, not just GSX.
See here for an explanation:
http://www.fsdreamteam.com/forum/index.php/topic,15300.msg110801.html#msg110801
-
I'm using P3D v3.4, is there a diffrent?
And what do you mean at last? Can I fix them now on anyway or have I really to wait for the next update?
-
I'm using P3D v3.4, is there a diffrent?
Only the affected file is called Prepar3D.CFG, instead of FSX.CFG, and it's located under %APPDATA%\Lockheed Martin\Prepar3d v3
And what do you mean at last? Can I fix them now on anyway or have I really to wait for the next update?
You should fix your problem regardless of GSX, since you are not just missing the GSX objects, but a whole lot of library objects, which might also create issues like stuttering, if some other scenery tried to use them.
But yes, we are planning to move over to use our own Simobject folder and configuration files, in future versions of our installers, so users with this problem (caused by other addons or having hand-edited a default file in the wrong way), won't assume it's a "GSX problem".
But you should fix this anyway, as explained in the linked thread.
-
This is how it lokks like in my P3D.cfg
[MAIN]
FIBER_FRAME_TIME_FRACTION=0.01
HideMenuFullscreen=1
HideMenuNormal=0
LabelsSupported=Airplane, Helicopter
Location=1685,145,2733,963,\\.\DISPLAY1
Maximized=2
ShowInfoText=0
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
SimObjectPaths.6=SimObjects\Countermeasures
SimObjectPaths.7=SimObjects\SkyTraffic
SimObjectPaths.8=Aerosoft\Mega Airport Zurich V2.0\simobjects
SimObjectPaths.9=SimObjects\Avatars
SimObjectPaths.10=SimObjects\Submersible
SimObjectPaths.11=SimObjects\Weapons
SimObjectPaths.12=SimObjects\IVAO_MTL
SimObjectPaths.13=C:\Program Files (x86)\12bPilot\SODE\data\SimObjects
SimObjectPaths.14=C:\ProgramData\12bPilot\SODE\SimObjects
User Objects=Airplane, Helicopter, Submersible, ExternalSim, Avatar
The Misc-path was missing and now, as always, it still doesen't work and I get the same error on and on...
-
The Misc-path was missing
So that confirms what I thought.
and now, as always, it still doesen't work and I get the same error on and on...
Those lines don't look wrong but, either you haven't modified the correct file, or have another error elsehwere in the file. In fact:
This is how it lokks like in my P3D.cfg
The correct file name is Prepar3D.CFG so, are you sure you are editing the correct file, and something really named Prepar3D.CFG and not, for example, Prepar3D.CFG.TXT or Prepar3D.CFG.BAK, which you can easily mistook as the actual file, if you turned off file extension view on Windows ?
If this was the case, you would add the missing Simobjects\Misc line, but to the wrong file, so the right one stil has the error.
Really, this is the only possible reason GSX would give you that error.
-
I'm not sure. So I only have the Prepar3D.cfg inside my %appdata% (Roaming) file. But there are two. Both with the same name. I've overwrote this with the same lines into MAIN.
But I looked inside the %ProgramData% file 12bPilot -> SODE -> simobjects, and this folder is empty is that normal?
Now I looked into %ProgramData% Lockheed Martin -> Prepar3D v3, and I have a "simobjects" and a "simobjects.cfg".
I added this file
[Entry.0]
PATH=C:\ProgramData\12bPilot\SODE\SimObjects
TITLE=SODE Common SimObjects
ACTIVE=true
REQUIRED=false
[Entry.1]
PATH=C:\Program Files (x86)\12bPilot\SODE\data\SimObjects
TITLE=SODE Main SimObjects
ACTIVE=true
REQUIRED=false
into the simobjects.
Now I can search for gates and runways, but when I try to Deobard or something like that, it still chrashs.
-
I'm not sure. So I only have the Prepar3D.cfg inside my %appdata% (Roaming) file. But there are two. Both with the same name.
That's what I suspected: you edited the wrong file.
But I looked inside the %ProgramData% file 12bPilot -> SODE -> simobjects, and this folder is empty is that normal?
SODE is not related to this problem.
Now I can search for gates and runways, but when I try to Deobard or something like that, it still chrashs.
What crash ? I'm sure you have a different error now.
-
That's what I suspected: you edited the wrong file.
And wich one is the correct?
I looked on my pictures I took with on the sim. The error exists, scince I installed the first update for Mega Airport Prague >:(
-
And wich one is the correct?
As I've said, the one which is REALLY named "Prepar3D.CFG", and nothing else. No P3D.CFG, or Prepar3D.CFG.BAK or something like Prepar3D.CFG.TXT.
But it might be possible to confuse them, if you have the "Hide known file extension" option enabled in the View options of Windows File Explorer.
The error exists, scince I installed the first update for Mega Airport Prague >:(
As I told you, these errors are either caused by having edited the file by hand, of by installers with bugs, or even a combination of both: installers that tried to add their own lines, on an already corrupted file, causing a mess.
-
for the first time since I have GSX, same problem here after intalling Aerosoft Pisa x for FSX; GSX doesn't work any more!
Found the solution! Some files in CFG gone somewhere ...
-
for the first time since I have GSX, same problem here after intalling Aerosoft Pisa x for FSX; GSX doesn't work any more!
these errors are either caused by having edited the file by hand, of by installers with bugs
Seems we found one...
-
GSX works day before the update about Prague, and on the picture you see Prague after the update, scince this it dosen't work anymore.
I followed your instructions but it's possible that I missed some little things because my english is not the best.
So please I need an answer, do you know a solution for this?
---HELP MEEEEEEE---
-
GSX works day before the update about Prague, and on the picture you see Prague after the update, scince this it dosen't work anymore.
Another bugged installer ??? I think it's easier if we had a Teamviewer session, so I can fix the file for you. Contact me in private to arrange that.
-
Hello again, with the same problem now for many, many months.
I deleted EzDok for ChasePlane and it still dosen't work
Does anyone have new information???
-
Couatl constantly crashes for me too, and for no apparent reason. Seems like I have to keep re-installing the stand alone, and then it starts working again.
-
It's not normal that reinstalling the Stand-Alone Addon Manager would "fix" any Couatl crashes, because it will just reinstall the same set of files.
However, what the installer also does, is to reset some settings you might have changed in the wrong way, or some other 3rd party app might have wrongly set, like any of the Compatibility modes for the simulator executable (it shouldn't be set, which is how the sim is installed by default), and it will remove some tweaks in the FSX.CFG which are known to be dangerous, such as the Poolsize set to 0.
That would explain why you think Couatl was the cause, when the problem where the wrong settings, and why launching the installer again seemed to fix, until you or some other product re-set the settings wrong again.
-
This is my P3D.cfg
Can you find any problems?
-
This is my P3D.cfg
Can you find any problems?
I was replying to a post that asked why reinstalling the Addon Manager would make the program working again. Is this your case ?
-
I don't know why it dosen't show the .cfg
Here you can perfectly see what happends after install the standalone manager (same as always) and the "Pool size" is set to 0
-
Here you can perfectly see what happends after install the standalone manager (same as always) and the "Pool size" is set to 0
The Pools Size should NOT be set to 0, that's one of the most dangerous settings you can have. So yes, it's possible that, if your crashes goes away after you reinstall the Addon Manager, it's because the installer has removed that dangerous setting for you, and if the crash reappear, it's because you put set it again.