FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: lionking on April 29, 2013, 07:17:24 pm
-
Hi,
I've recently changed to Prepar3D but I'm having a bit trouble with GSX at the moment.
With every aircraft at any airport I get an error message telling me that the couatl engine has just crashed and when I click OK, all the typical GSX objects are immediately gone and I can restart the service over and over again it keeps on sending errors.
I especially use the Airbus and Boeing packages from Overland and mostly standard airports. But how I've already said, it happens with every plane at every airport.
In FSX, I had exactly the same planes but never any crash, so I was sure it had something to do with P3D but, since you said, GSX is fully compatible, I thought that's weird.
Thanks for support!
-
You should enable logging in the Troubleshooting section of the "GSX Settings" page, and check the produced Couatl.LOG and Couatl.ERR files that might contain hints about the crash. Post them here when you have them.
-
That's what the couatl.err indicates.
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 15:01:35 2013
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:49:36 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:50:35 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:52:27 2013
SimConnect exception: <unknown error>
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 14:32:48 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 14:34:50 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 18:59:31 2013
Traceback (most recent call last):
File "couatl\common\audioManager.py", line 181, in crossFade
OverflowError: long int too large to convert
-
Nobody ever reported such problem so far. Could you please post your Couatl.LOG too ?
-
I'm baffled. I really can't make any sense out of it. There are no computations that involve integers neither in crossFade (line 181) nor in setObjectData (line 317). Moreover, the first (15:01:35) and the fourth (19:52:27) reports suggests that there is something very fishy happening, as they show the problem occurring before the simulation engine actually starts. The best idea I have is that there must be something very wrong happening during the C++/Python bindings. I concur with Umberto that having the Couatl.log might be helpful, but my humble opinion is that either the Couatl EXE or the python DLLs are corrupt or there is some sort of DLL conflict with something that is installed on your machine. You said that you have both FSX and P3D installed on your machine: are the FSDreamTeam products shared between the two installations? If you have two different installations, check that both are up to date?
-
You said that you have both FSX and P3D installed on your machine
No, it's a completley new computer and I right installed P3D and FSX has here never been installed.
How can I create the couatl.log file?
(I mean, the messages says at the that I would have to update the addon manager and I did, but still the same.)
-
Now it gets even more frustrating...
It either crashes just like before or it works in a way I don't want it to work. (See picture)
When I realized this time it will likely not crash, I edited the plane as it had too less stairs and unloaders. So I set the unloader as being chosen by GSX, but it showed up the wrong ones and they overlapped each other. Same with stairs. Catering I didn't test yet.
Just to remind, in FSX it worked with every Overland plane, of course with the right unloader truck and without overlapping.
What could be the mistake?
-
It either crashes just like before or it works in a way I don't want it to work. (See picture)
This is not very clear: what do you mean, it crashes randomly, or it crashes when you do something specific ?
I edited the plane as it had too less stairs and unloaders. So I set the unloader as being chosen by GSX, but it showed up the wrong ones and they overlapped each other. Same with stairs. Catering I didn't test yet.
The problem is surely something you did wrong in the airplane config, perhaps that caused the crash too. Try to RESET the airplane config, and try it without any customization: this will try to use the airplane.cfg as a source of data, exit will be probably off, but at least they should *roughly* work.
Then, adjust only a door at time, and test, until you find what caused the problem.
-
It crashes thoroughly in every new try, still when all plane customizations are deleted. But it was clear that the problem is still going to occur as this had already happened before I just edited a single plane.
Please tell me how to create the log file.
-
You posted a screenshot with GSX working (even if vehicles were misplaced), this means sometimes GSX doesn't crash, so you should be able to enable logging in the Troubleshooting section of the GSX Settings menu.
-
Yes, it did crash after about one minute or slightly more.
This is the couatl.log content:
couatl v2.0 (build 2348)
log started on Tue Apr 30 23:36:59 2013
connecting to SimConnect...
connected to Prepar3D
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 19 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon KLAS
Addon KLAS not installed or missing one or more files, skipping
Loading addon KFLL
Addon KFLL not installed or missing one or more files, skipping
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX not installed or missing one or more files, skipping
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
Generic Software on Speakers (Logitech USB Speaker) (47656e6572696320536f667477617265206f6e20537065616b65727320284c6f6769746563682055534220537065616b657229)
Generic Software on Digital Audio (S/PDIF) (High Definition Audio Device) (47656e6572696320536f667477617265206f6e204469676974616c20417564696f2028532f504449462920284869676820446566696e6974696f6e20417564696f2044657669636529)
Created OpenAL device: Generic Software on Speakers (Logitech USB Speaker)
Device info:
Major version: 1
Minor version: 1
Frequency: 44100
Refresh: 40
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX
Context info:
Vendor: Creative Labs Inc.
Version: 1.1
Renderer: Software
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current directory is D:/Programme/Flugsimulation/Prepar3D/Prepar3D
Looking for scenery.cfg in C:/ProgramData/Lockheed Martin/Prepar3D/scenery.cfg
using Scenery/World (layer 1)
using Scenery/BASE (layer 2)
using Addon Scenery/Chprox/CHPROX_apts_d (layer 3)
using Scenery/0000 (layer 4)
using Scenery/0001 (layer 5)
using Scenery/0002 (layer 6)
using Scenery/0003 (layer 7)
using Scenery/0004 (layer 8)
using Scenery/0005 (layer 9)
using Scenery/0006 (layer 10)
using Scenery/0007 (layer 11)
using Scenery/0100 (layer 12)
using Scenery/0101 (layer 13)
using Scenery/0102 (layer 14)
using Scenery/0103 (layer 15)
using Scenery/0104 (layer 16)
using Scenery/0105 (layer 17)
using Scenery/0106 (layer 18)
using Scenery/0107 (layer 19)
using Scenery/0200 (layer 20)
using Scenery/0201 (layer 21)
using Scenery/0202 (layer 22)
using Scenery/0203 (layer 23)
using Scenery/0204 (layer 24)
using Scenery/0205 (layer 25)
using Scenery/0206 (layer 26)
using Scenery/0207 (layer 27)
using Scenery/0300 (layer 28)
using Scenery/0301 (layer 29)
using Scenery/0302 (layer 30)
using Scenery/0303 (layer 31)
using Scenery/0304 (layer 32)
using Scenery/0305 (layer 33)
using Scenery/0306 (layer 34)
using Scenery/0307 (layer 35)
using Scenery/0400 (layer 36)
using Scenery/0401 (layer 37)
using Scenery/0402 (layer 38)
using Scenery/0403 (layer 39)
using Scenery/0404 (layer 40)
using Scenery/0405 (layer 41)
using Scenery/0406 (layer 42)
using Scenery/0407 (layer 43)
using Scenery/0500 (layer 44)
using Scenery/0501 (layer 45)
using Scenery/0502 (layer 46)
using Scenery/0503 (layer 47)
using Scenery/0504 (layer 48)
using Scenery/0505 (layer 49)
using Scenery/0506 (layer 50)
using Scenery/0507 (layer 51)
using Scenery/0600 (layer 52)
using Scenery/0601 (layer 53)
using Scenery/0602 (layer 54)
using Scenery/0603 (layer 55)
using Scenery/0604 (layer 56)
using Scenery/0605 (layer 57)
using Scenery/0606 (layer 58)
using Scenery/0607 (layer 59)
using Scenery/0700 (layer 60)
using Scenery/0701 (layer 61)
using Scenery/0702 (layer 62)
using Scenery/0703 (layer 63)
using Scenery/0704 (layer 64)
using Scenery/0705 (layer 65)
using Scenery/0706 (layer 66)
using Scenery/0707 (layer 67)
using Scenery/0800 (layer 68)
using Scenery/0801 (layer 69)
using Scenery/0802 (layer 70)
using Scenery/0803 (layer 71)
using Scenery/0804 (layer 72)
using Scenery/0805 (layer 73)
using Scenery/0806 (layer 74)
using Scenery/0807 (layer 75)
using Scenery/0900 (layer 76)
using Scenery/0901 (layer 77)
using Scenery/0902 (layer 78)
using Scenery/0903 (layer 79)
using Scenery/0904 (layer 80)
using Scenery/0905 (layer 81)
using Scenery/0906 (layer 82)
using Scenery/0907 (layer 83)
using Scenery/1000 (layer 84)
using Scenery/1001 (layer 85)
using Scenery/1002 (layer 86)
using Scenery/1003 (layer 87)
using Scenery/1004 (layer 88)
using Scenery/1005 (layer 89)
using Scenery/1006 (layer 90)
using Scenery/1007 (layer 91)
using Scenery/1100 (layer 92)
using Scenery/1101 (layer 93)
using Scenery/1102 (layer 94)
using Scenery/1103 (layer 95)
using Scenery/1104 (layer 96)
using Scenery/1105 (layer 97)
using Scenery/1106 (layer 98)
using Scenery/1107 (layer 99)
using Scenery/AFRI (layer 100)
using Scenery/ASIA (layer 101)
using Scenery/AUST (layer 102)
using Scenery/EURE (layer 103)
using Scenery/EURW (layer 104)
using Scenery/NAMC (layer 105)
using Scenery/NAME (layer 106)
using Scenery/NAMW (layer 107)
using Scenery/OCEN (layer 108)
using Scenery/SAME (layer 109)
using Scenery/Cities/Oshkosh (layer 110)
using Scenery/Cities/StMaarten (layer 111)
using Scenery/Cities/Rio (layer 112)
using Scenery/Cities/LasVegas (layer 113)
using Scenery/Global (layer 114)
using Scenery/Props (layer 115)
using Scenery/Cities/Reno (layer 116)
using Scenery/Cities/Istanbul (layer 117)
using Scenery/Cities/Longleat (layer 118)
using Scenery/Cities/Berlin (layer 119)
using Scenery/Cities/Edwards_AFB (layer 120)
using Scenery/Cities/Norfolk (layer 121)
using Scenery/Cities/Eglin (layer 122)
using Scenery/Cities/KORL_OrlandoExecutive (layer 123)
using Scenery/Cities/KLFI_Langley_AFB (layer 124)
using Scenery/Cities/FortRucker (layer 125)
using Scenery/Bathymetry (layer 126)
using Addon Scenery (layer 127)
using FsDreamTeam/ZurichX (layer 128)
using D:/fsgx2010/oce (layer 129)
using D:/fsgx2010/eur (layer 130)
using D:/fsgx2010/asi (layer 131)
using D:/fsgx2010/csa (layer 132)
using D:/fsgx2010/afr (layer 133)
using D:/fsgx2010/ant (layer 134)
using D:/fsgx2010/nam (layer 135)
using D:/fsgx2010/LocalMeshes (layer 136)
using D:/Programme/Flugsimulation/Prepar3D/Prepar3D/Addon Scenery/FlyTampa-Dubai/ (layer 137)
using Addon Scenery/Chprox/CHPROX_elev (layer 138)
using Addon Scenery/Chprox/CHPROX_scen (layer 139)
using Addon Scenery/Chprox/CHPROX_apts (layer 140)
using Addon Scenery/Chprox/CHPROX_LANDMARKS (layer 141)
using D:/Programme/Flugsimulation/Addons/FS Real Time/TzFiles04 (layer 142)
Airport cache loaded
Addon GSX loaded
Loading addon CYVR
Addon CYVR not installed or missing one or more files, skipping
Loading addon JFK2
Addon JFK2 not installed or missing one or more files, skipping
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Loading addon KPHX
Addon KPHX not installed or missing one or more files, skipping
Starting system monitors
Current locale is German_Switzerland.1252
SharedMemInterface connected
Loading aircraft data from Airplanes\Mooney_Acclaim
Using aircraft data from aircraft.cfg file
Section [contact_points] contains invalid data at entry point.4
Loading airport LSZH from D:/Programme/Flugsimulation/Prepar3D/Prepar3D/FsDreamTeam/ZurichX/scenery/APX_LSZH.BGL
Using airport customization from GSX.airports.lszh_fsdt
disconnected from SimConnect.
connected from SimConnect.
I've never had any problems with those aircrafts before nor can I remember that it had ever crashed because of something else.
The duration until it crashes is variable, sometimes the bagagge unloades can reach their position, sometimes they just go for a few seconds and sometimes before the message shows up, the screen freezes and I have to press the "Esc" key and then the objects are gone and the exe. restarts.
-
Did it crash in the session the log was taken? I see "disconnected from SimConnect." at the end, which usually means that Couatl was shut down regularly. (I assume that the "connected from SimConnect." that follows is just a wrong cut&paste). A log where things went wrong would be more helpful. Anyway, the hypothesis of a DLL SideBySide conflict is now my best guess.
-
There's now the error file and the couatl file, both are up to date after having taken another try which crashed.
couatl.err
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 15:01:35 2013
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:49:36 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:50:35 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Sun Apr 28 19:52:27 2013
SimConnect exception: <unknown error>
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 14:32:48 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 201, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 14:34:50 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\passengerStairs.py", line 161, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Mon Apr 29 18:59:31 2013
Traceback (most recent call last):
File "couatl\common\audioManager.py", line 181, in crossFade
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Tue Apr 30 13:32:28 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Tue Apr 30 14:52:21 2013
Traceback (most recent call last):
File "couatl\common\audioManager.py", line 181, in crossFade
OverflowError: long int too large to convert
couatl v2.0 (build 2348)
panic log started on Tue Apr 30 21:40:54 2013
Traceback (most recent call last):
File "couatl\common\fsm.py", line 67, in executeDoFuncToCompletion
File "couatl\GSX\assistanceServices\baggageTrain.py", line 210, in do
File "couatl\GSX\assistanceServices\baseAssistanceVehicle.py", line 205, in do
File "couatl\common\simObjectMoverIK.py", line 291, in run
File "couatl\common\simObjectMoverIK.py", line 317, in setObjectData
OverflowError: long int too large to convert
couatl.log
couatl v2.0 (build 2348)
log started on Wed May 01 10:07:44 2013
connecting to SimConnect...
connected to Prepar3D
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 19 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX not installed or missing one or more files, skipping
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping
Loading addon KLAS
Addon KLAS not installed or missing one or more files, skipping
Loading addon KFLL
Addon KFLL not installed or missing one or more files, skipping
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW not installed or missing one or more files, skipping
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping
Loading addon KLAX
Addon KLAX not installed or missing one or more files, skipping
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
Generic Software on Speakers (Logitech USB Speaker) (47656e6572696320536f667477617265206f6e20537065616b65727320284c6f6769746563682055534220537065616b657229)
Generic Software on Digital Audio (S/PDIF) (High Definition Audio Device) (47656e6572696320536f667477617265206f6e204469676974616c20417564696f2028532f504449462920284869676820446566696e6974696f6e20417564696f2044657669636529)
Created OpenAL device: Generic Software on Speakers (Logitech USB Speaker)
Device info:
Major version: 1
Minor version: 1
Frequency: 44100
Refresh: 40
Sync: 0
Mono sources: 255
Stereo sources: 1
Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX
Context info:
Vendor: Creative Labs Inc.
Version: 1.1
Renderer: Software
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Current directory is D:/Programme/Flugsimulation/Prepar3D/Prepar3D
Looking for scenery.cfg in C:/ProgramData/Lockheed Martin/Prepar3D/scenery.cfg
using Scenery/World (layer 1)
using Scenery/BASE (layer 2)
using Addon Scenery/Chprox/CHPROX_apts_d (layer 3)
using Scenery/0000 (layer 4)
using Scenery/0001 (layer 5)
using Scenery/0002 (layer 6)
using Scenery/0003 (layer 7)
using Scenery/0004 (layer 8)
using Scenery/0005 (layer 9)
using Scenery/0006 (layer 10)
using Scenery/0007 (layer 11)
using Scenery/0100 (layer 12)
using Scenery/0101 (layer 13)
using Scenery/0102 (layer 14)
using Scenery/0103 (layer 15)
using Scenery/0104 (layer 16)
using Scenery/0105 (layer 17)
using Scenery/0106 (layer 18)
using Scenery/0107 (layer 19)
using Scenery/0200 (layer 20)
using Scenery/0201 (layer 21)
using Scenery/0202 (layer 22)
using Scenery/0203 (layer 23)
using Scenery/0204 (layer 24)
using Scenery/0205 (layer 25)
using Scenery/0206 (layer 26)
using Scenery/0207 (layer 27)
using Scenery/0300 (layer 28)
using Scenery/0301 (layer 29)
using Scenery/0302 (layer 30)
using Scenery/0303 (layer 31)
using Scenery/0304 (layer 32)
using Scenery/0305 (layer 33)
using Scenery/0306 (layer 34)
using Scenery/0307 (layer 35)
using Scenery/0400 (layer 36)
using Scenery/0401 (layer 37)
using Scenery/0402 (layer 38)
using Scenery/0403 (layer 39)
using Scenery/0404 (layer 40)
using Scenery/0405 (layer 41)
using Scenery/0406 (layer 42)
using Scenery/0407 (layer 43)
using Scenery/0500 (layer 44)
using Scenery/0501 (layer 45)
using Scenery/0502 (layer 46)
using Scenery/0503 (layer 47)
using Scenery/0504 (layer 48)
using Scenery/0505 (layer 49)
using Scenery/0506 (layer 50)
using Scenery/0507 (layer 51)
using Scenery/0600 (layer 52)
using Scenery/0601 (layer 53)
using Scenery/0602 (layer 54)
using Scenery/0603 (layer 55)
using Scenery/0604 (layer 56)
using Scenery/0605 (layer 57)
using Scenery/0606 (layer 58)
using Scenery/0607 (layer 59)
using Scenery/0700 (layer 60)
using Scenery/0701 (layer 61)
using Scenery/0702 (layer 62)
using Scenery/0703 (layer 63)
using Scenery/0704 (layer 64)
using Scenery/0705 (layer 65)
using Scenery/0706 (layer 66)
using Scenery/0707 (layer 67)
using Scenery/0800 (layer 68)
using Scenery/0801 (layer 69)
using Scenery/0802 (layer 70)
using Scenery/0803 (layer 71)
using Scenery/0804 (layer 72)
using Scenery/0805 (layer 73)
using Scenery/0806 (layer 74)
using Scenery/0807 (layer 75)
using Scenery/0900 (layer 76)
using Scenery/0901 (layer 77)
using Scenery/0902 (layer 78)
using Scenery/0903 (layer 79)
using Scenery/0904 (layer 80)
using Scenery/0905 (layer 81)
using Scenery/0906 (layer 82)
using Scenery/0907 (layer 83)
using Scenery/1000 (layer 84)
using Scenery/1001 (layer 85)
using Scenery/1002 (layer 86)
using Scenery/1003 (layer 87)
using Scenery/1004 (layer 88)
using Scenery/1005 (layer 89)
using Scenery/1006 (layer 90)
using Scenery/1007 (layer 91)
using Scenery/1100 (layer 92)
using Scenery/1101 (layer 93)
using Scenery/1102 (layer 94)
using Scenery/1103 (layer 95)
using Scenery/1104 (layer 96)
using Scenery/1105 (layer 97)
using Scenery/1106 (layer 98)
using Scenery/1107 (layer 99)
using Scenery/AFRI (layer 100)
using Scenery/ASIA (layer 101)
using Scenery/AUST (layer 102)
using Scenery/EURE (layer 103)
using Scenery/EURW (layer 104)
using Scenery/NAMC (layer 105)
using Scenery/NAME (layer 106)
using Scenery/NAMW (layer 107)
using Scenery/OCEN (layer 108)
using Scenery/SAME (layer 109)
using Scenery/Cities/Oshkosh (layer 110)
using Scenery/Cities/StMaarten (layer 111)
using Scenery/Cities/Rio (layer 112)
using Scenery/Cities/LasVegas (layer 113)
using Scenery/Global (layer 114)
using Scenery/Props (layer 115)
using Scenery/Cities/Reno (layer 116)
using Scenery/Cities/Istanbul (layer 117)
using Scenery/Cities/Longleat (layer 118)
using Scenery/Cities/Berlin (layer 119)
using Scenery/Cities/Edwards_AFB (layer 120)
using Scenery/Cities/Norfolk (layer 121)
using Scenery/Cities/Eglin (layer 122)
using Scenery/Cities/KORL_OrlandoExecutive (layer 123)
using Scenery/Cities/KLFI_Langley_AFB (layer 124)
using Scenery/Cities/FortRucker (layer 125)
using Scenery/Bathymetry (layer 126)
using Addon Scenery (layer 127)
using FsDreamTeam/ZurichX (layer 128)
using D:/fsgx2010/oce (layer 129)
using D:/fsgx2010/eur (layer 130)
using D:/fsgx2010/asi (layer 131)
using D:/fsgx2010/csa (layer 132)
using D:/fsgx2010/afr (layer 133)
using D:/fsgx2010/ant (layer 134)
using D:/fsgx2010/nam (layer 135)
using D:/fsgx2010/LocalMeshes (layer 136)
using D:/Programme/Flugsimulation/Prepar3D/Prepar3D/Addon Scenery/FlyTampa-Dubai/ (layer 137)
using Addon Scenery/Chprox/CHPROX_elev (layer 138)
using Addon Scenery/Chprox/CHPROX_scen (layer 139)
using Addon Scenery/Chprox/CHPROX_apts (layer 140)
using Addon Scenery/Chprox/CHPROX_LANDMARKS (layer 141)
using D:/Programme/Flugsimulation/Addons/FS Real Time/TzFiles04 (layer 142)
Airport cache loaded
Addon GSX loaded
Loading addon CYVR
Addon CYVR not installed or missing one or more files, skipping
Loading addon JFK2
Addon JFK2 not installed or missing one or more files, skipping
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping
Loading addon KPHX
Addon KPHX not installed or missing one or more files, skipping
Starting system monitors
Current locale is German_Switzerland.1252
SharedMemInterface connected
Loading aircraft data from Airplanes\SMS_A330-300
Using aircraft data from SimConnect
Loading airport LSZH from D:/Programme/Flugsimulation/Prepar3D/Prepar3D/FsDreamTeam/ZurichX/scenery/APX_LSZH.BGL
Using airport customization from GSX.airports.lszh_fsdt
disconnected from SimConnect.
-
There was a problem in your first session here:
Section [contact_points] contains invalid data at entry point.4
But that's because you had the Mooney, which is not really considered a relevan airplane for GSX. However, it seems that session didn't had any errors.
Do you have other products related to Python (such as Blender) or other copies of the Python language installed ?
-
No, there are only FSDT products using Python on my system.
Yeah, with the Mooney you've been right, but you saw the A330 hadn't been configured at all as there was only one truck and it crashed though.
-
Yeah, with the Mooney you've been right, but you saw the A330 hadn't been configured at all as there was only one truck and it crashed though.
Ok, what's happening if you start directly with creating a configuration, without calling any other GSX function ? Does the editor works ?
-
Just tested: The configuration mode is working properly and 3D configuration as well, but as soon as I started to use the services, it crashed. It's never mind if the aircraft has got a wrong config or an adjusted one.
Any ideas?
-
What can I do? GSX is pretty useless at the moment...
-
I'm having a similar issue, do you have FSUIPC and if so, is it registered? I read that it's a possible solution to scenery problems as registered versions have more features. Wondering before I drop $30 more. Thanks
-
@jpmclees, you are having an entirely different problem, and I'm following you via email already, please don't post in this thread, because the issue discussed here is really different (and unique), and I don't think you can fix anything with FSUIPC, I've replied to you via email with some possible solutions.
-
Now there's another issue going on: Just started P3D and the couatl menu isn't at the addon sub-bar anymore. I didn't change anything and the addon-manager as well as other addons still appear, but couatl is gone. I downlaoded the latest Addon-Manager but it was still gone, is it possible that it works again by reinstalling all FSDT products? Because otherwise I can not make me rhyme it.
-
Check your antivirus, disable it when downloading and installing, and exclude the Prepar3D\Fsdreamteam\couatl\Couatl.exe from scanning. Better yet, exclude the whole P3D folder from scanning, that will speed up loading times too.
-
Disabling antivirus worked.
Anyway; I found out only the deboaring procedure doesn't work and forces couatl to stop, all the other services do as they are supposed to do.
BTW: It's an entirely different subject, but it's on the way so: Here's my Airbus A340-500 config, the second door stair and the stair at the rear door go just thourgh the plane and then they dock at the other side where the catering trucks are supposed to be. I looked out for any mistaken or forgotten minus signs but I didn't see anything suspicious.
[aircraft]
nosegear = 26.95
refueling = 1
[exit1]
pos = -2.41 27.58 -1.32 10.80
code = 1
[exit2]
pos = -2.97 14.44 -1.38 178.00
code = 1
[exit3]
remove = 1
[exit4]
pos = -2.21 -21.33 -1.15 167.00
code = 1
[service1]
pos = 2.53 27.41 -1.20 -8.00
code = 0
[service2]
pos = 2.27 -21.61 -0.85 10.90
code = 0
[cargo1]
pos = 1.61 23.70 -3.41 -2.00
code = 2
uldcode = AUTO
[cargo2]
pos = 1.39 -15.03 -3.48 5.00
code = 2
uldcode = AUTO
-
Hey! :-\
What's now!?!
-
It looks like you reversed the doors. The green arrow should always point outside the airplane.
-
I think, I had that time just a lucky day, because now it crashes with every option from GSX.
Please help me! I paid for it and I want to have a fully functional software.
-
I think, I had that time just a lucky day, because now it crashes with every option from GSX.
And the Couatl.LOG still shows the same "Overflow" error ?
Please help me! I paid for it and I want to have a fully functional software.
GSX it's fully functional for everybody, and you are the only one with that problem (assuming the crash is again the problem you initiallty reported before), and of course since we sell GSX in Trial mode, you could have verified how it worked on your system before purchasing it.
Since nobody else reported this before, so it's 100% sure caused by some other product you installed which is interfering, and that's the whole point of offering a Trial, so you can verify if anything else installed in your system can cause any problems.
However, this doesn't obviously mean that you will not be continually followed up in this, because you have been so far, and you will be as long as you keep reporting problems. It only means you should use the "I paid for it" argument, because there's nothing more we could do, other than offering a Trial to ensure you don't risk paying for something that might "not work".
-
Of course there's the demo version, but when I purchased GSX I had been using FSX. And then I read your comment that P3D is fully compatible with GSX.
Yes, it's still the same...
-
Of course there's the demo version, but when I purchased GSX I had been using FSX. And then I read your comment that P3D is fully compatible with GSX.
What makes you think this is a problem related to P3D ?
I've asked if the error log still show the "Overflow" error as before, but you haven't replied. You said it didn't worked, then you said it was the antivirus and then it started working again, then you posted a configuration with an error, which I've suggested how to fix, now you are saying it's crashing again.
Since the GSX program is always the same, it's fairly obvious that all those different outcomes are a result of something you are doing (using the antivirus or not, editing the configuration in a wrong or in a correct way, etc.) which is why I've asked if you are still getting the original error, or something different.
-
Yes, it's still the same...
What makes you think this is a problem related to P3D ?
With FSX I never had any problems in past.
-
Hey FSDreamteam, what are you doing on my system??
Neither Los Angeles nor XPOI have ever been installed by me. And everyone can cleary see that it isn't listed in programs.
What's it all about??
-
With FSX I never had any problems in past.
That doesn't mean P3D it's the problem. I'll ask it again, for the 3rd time: are you STILL getting the SAME error you had initially ? The Overflow error ?
-
For the 3rd time: Yes, it's still the same... ::)
And explain me what you do on my system, mentioning KLAX and XPOI!
-
For the 3rd time: Yes, it's still the same... ::)
That's the 1st time you finally replied that you are now having the ORIGINAL "Overflow" message. Your subsequent messages after the first one show entirely different issues, which were clearly a result of your editing (the reversed doors was obviously a entirely different thing, and sure it didn't caused an overflow error) and you never said you are now back to the original "Overflow" error.
About the "Overflow" error, you have been answered about it already, and it doesn't have anything to do with the difference between P3D or FSX, NOBODY has ever reported THIS problem before, and we don't have the slightest idea what is causing, other than it's surely an external cause, such as external program (even not related to flight simulation) that is interfering.
We had reports of unusual situations such as power management programs or video card tweakers causing problems, but this (the "Overflow" error) is the FIRST and ONLY report of such specific error.
The only possible solution, is to proceed by exclusion, and trying to quit all running programs one at time, until you find the culprit.
And explain me what you do on my system, mentioning KLAX and XPOI!
The problem with KLAX is caused by a free scenery from Ray Smith you have installed, that by unfortunate chance has a file with exactly the same name ( KLAX_OBJ.BGL ) and a very similar size to one of the KLAX files, so the Addon Manager believes KLAX is installed, but "outdated", because that file is not what is expect it to be.
You can fix this by simply renaming that file to anything you like, provided it keeps the .BGL extension.
Not that this has anything to do with your "Overflow" problem, the only result it will cause a bogus "Trial for fsdreamteam KLAX V2 has started" message.
What about XPOI ?
-
When I said "Yes, it's still the same" at first place, I meant the Overflow.
However, yes, XPOI is indicated being installed too.
-
However, yes, XPOI is indicated being installed too
Where ? In the Addon Manager ? If yes, just ignore it: that label in the Addon Manager has some significance only for sceneries that comes with an AFCAD. Since XPOI it's not a scenery, it can't be detected that way, so that information is not really meaningful for non-sceneries products.
However, this doesn't have any relationship with your Overflow error, which basically shouldn't exists in the first place. And it's not related at all to the fact you are running P3D (well, it might be marginally related to it, if an external program which is causing it, it's a P3D add-on)
-
I'll try to do an entire reinstall of all FSDT products. What entries do I have to delete in addition to the normal deinstallation procedure?
-
I'll try to do an entire reinstall of all FSDT products
Will not change anything, because the cause it's surely external. You can save a lot of time by just reinstalling the Stand-Alone Addon Manager, this will update/fix everything.
What entries do I have to delete in addition to the normal deinstallation procedure?
The uninstaller uninstalls everything that needs to be uninstalled, especially if you reply Yes to the questions "do you want to remove the Addon Manager" and "Do you want to remove the Couatl engine".
What the uninstaller doesn't uninstalls, are your activation (not related, at all, to your issue) and your preferences, which might cause errors if you had some airplane or scenery that you edited in the wrong way.
They can be removed by removing the following folders:
%APPDATA%\Virtuali
This will result in all your scenery and airplane customization and your preferences being lost.
-
Still having the problem... :-\
-
I've recently remarked I had not installed .NET Framework version 4.5. Now I've updated it.
Haven't tested yet, but do you think it might be the undiscovered solution?
-
Haven't tested yet, but do you think it might be the undiscovered solution?
Difficult to think a solution, when you are the one and only that reported this problem. In case a solution will eventually be found (but you'll likely fix it anyway when reformatting, so you might never know what was it), it will surely you that will find it.
Again, I'm only referring to your Overflow error, if you are having other issues now, that might be different.
In any case, we don't use .NET framework, but each time you install a new framework, it usually updates the VC++ runtimes too, that we require for all our products (and FSX requires them too).
-
Yep, it isn't the hoped solution.
-
It seems the error has been identified but not fixed yet.
Namely I'd tested a few planes from other developers before I recognized only theOverland planes force GSX to crash. And I think with "addon unknown" Overland is supposed to be.
In FSX both worked together well in P3D, GSX and Overland work well, but only if not used at the same time.
Do you know how to fix?
-
Namely I'd tested a few planes from other developers before I recognized only theOverland planes force GSX to crash. And I think with "addon unknown" Overland is supposed to be.
That indicates your configuration for it is wrong. Try to Reset the configuration and create a new one, being sure all data is inserted correctly.
-
Do you imply deletion like shown in the picture?
-
Do you imply deletion like shown in the picture?
You removed our entire local preferences folder, which is supposed to store preferences for all our products. That's obviously wrong, and not what I've said. Doing this, you lost all your customized GSX airplanes, and all your customized GSX airports, on top of any other preferences by other FSDT products too, such as CYVR, XPOI, etc.
I've said to Reset the airplane configuration for the airplane that didn't work. There's an option for that in the airplane configuration editor.
Now, it's best if you reinstall GSX and any other FSDT products, since you removed all their preferences, and some of them are created at install time.
-
Found the error:
I deleted the entire folder and additional the "intelliscene.cfg" file. I used it for every Overland plane since I was too lazy to customize every single plane on my own. Well, former in "FSX times" it did a great job, but I suspect it is somehow not compatible with P3D.
The good thing in that way I didn't lose any preferences as there haven't been any.
Seems to be working.
Ps: Does anyone own configurations for the "Overland" planes?