FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Morten on August 09, 2013, 01:41:45 pm
-
Suddenly my GSX is crashing regardless of any command, any airport and any aircraft. The issue seems to have started from implementation of the latest Addon Manager.
I have tried tons of reinstalls - including, clean installs, reinstalls over existing installation with and without existing ini.file and so on - still same old error appears.
I haven't altered any settings whatsoever - only changed the key assignment for starting up GSX to ctrl+11, which has been working fine.
Could you please help me to detect what the heck is going on?
Coutatl.err:
couatl v2.0 (build 2348)
panic log started on Thu Aug 08 01:22:25 2013
Traceback (most recent call last):
File "couatl\common\__init__.py", line 22, in <lambda>
RuntimeError: Couatl.Application already showing a dialog
Couatl.log:
couatl v2.0 (build 2348)
log started on Fri Aug 09 03:31:30 2013
connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
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 loaded
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 Højttalere (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e2048f86a7474616c65726520285265616c74656b204869676820446566696e6974696f6e20417564696f29)
Created OpenAL device: Generic Software on Højttalere (Realtek High Definition Audio)
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 B:/FSX
Looking for scenery.cfg in C:/ProgramData/Microsoft/FSX/scenery.cfg
using Scenery/World (layer 1)
using Scenery/BASE (layer 2)
using Scenery/0000 (layer 3)
using Scenery/0001 (layer 4)
using Scenery/0002 (layer 5)
using Scenery/0003 (layer 6)
using Scenery/0004 (layer 7)
using Scenery/0005 (layer 8 )
using Scenery/0006 (layer 9)
using Scenery/0007 (layer 10)
using Scenery/0100 (layer 11)
using Scenery/0101 (layer 12)
using Scenery/0102 (layer 13)
using Scenery/0103 (layer 14)
using Scenery/0104 (layer 15)
using Scenery/0105 (layer 16)
using Scenery/0106 (layer 17)
using Scenery/0107 (layer 18)
using Scenery/0200 (layer 19)
using Scenery/0201 (layer 20)
using Scenery/0202 (layer 21)
using Scenery/0203 (layer 22)
using Scenery/0204 (layer 23)
using Scenery/0205 (layer 24)
using Scenery/0206 (layer 25)
using Scenery/0207 (layer 26)
using Scenery/0300 (layer 27)
using Scenery/0301 (layer 28)
using Scenery/0302 (layer 29)
using Scenery/0303 (layer 30)
using Scenery/0304 (layer 31)
using Scenery/0305 (layer 32)
using Scenery/0306 (layer 33)
using Scenery/0307 (layer 34)
using Scenery/0400 (layer 35)
using Scenery/0401 (layer 36)
using Scenery/0402 (layer 37)
using Scenery/0403 (layer 38)
using Scenery/0404 (layer 39)
using Scenery/0405 (layer 40)
using Scenery/0406 (layer 41)
using Scenery/0407 (layer 42)
using Scenery/0500 (layer 43)
using Scenery/0501 (layer 44)
using Scenery/0502 (layer 45)
using Scenery/0503 (layer 46)
using Scenery/0504 (layer 47)
using Scenery/0505 (layer 48)
using Scenery/0506 (layer 49)
using Scenery/0507 (layer 50)
using Scenery/0600 (layer 51)
using Scenery/0601 (layer 52)
using Scenery/0602 (layer 53)
using Scenery/0603 (layer 54)
using Scenery/0604 (layer 55)
using Scenery/0605 (layer 56)
using Scenery/0606 (layer 57)
using Scenery/0607 (layer 58)
using Scenery/0700 (layer 59)
using Scenery/0701 (layer 60)
using Scenery/0702 (layer 61)
using Scenery/0703 (layer 62)
using Scenery/0704 (layer 63)
using Scenery/0705 (layer 64)
using Scenery/0706 (layer 65)
using Scenery/0707 (layer 66)
using Scenery/0800 (layer 67)
using Scenery/0801 (layer 68)
using Scenery/0802 (layer 69)
using Scenery/0803 (layer 70)
using Scenery/0804 (layer 71)
using Scenery/0805 (layer 72)
using Scenery/0806 (layer 73)
using Scenery/0807 (layer 74)
using Scenery/0900 (layer 75)
using Scenery/0901 (layer 76)
using Scenery/0902 (layer 77)
using Scenery/0903 (layer 78)
using Scenery/0904 (layer 79)
using Scenery/0905 (layer 80)
using Scenery/0906 (layer 81)
using Scenery/0907 (layer 82)
using Scenery/1000 (layer 83)
using Scenery/1001 (layer 84)
using Scenery/1002 (layer 85)
using Scenery/1003 (layer 86)
using Scenery/1004 (layer 87)
using Scenery/1005 (layer 88)
using Scenery/1006 (layer 89)
using Scenery/1007 (layer 90)
using Scenery/1100 (layer 91)
using Scenery/1101 (layer 92)
using Scenery/1102 (layer 93)
using Scenery/1103 (layer 94)
using Scenery/1104 (layer 95)
using Scenery/1105 (layer 96)
using Scenery/1106 (layer 97)
using Scenery/1107 (layer 98)
using Scenery/AFRI (layer 99)
using Scenery/ASIA (layer 100)
using Scenery/AUST (layer 101)
using Scenery/EURE (layer 102)
using Scenery/EURW (layer 103)
using Scenery/NAMC (layer 104)
using Scenery/NAME (layer 105)
using Scenery/NAMW (layer 106)
using Scenery/OCEN (layer 107)
using Scenery/SAME (layer 108)
using Scenery/Cities/Oshkosh (layer 109)
using Scenery/Cities/StMaarten (layer 110)
using Scenery/Cities/Rio (layer 111)
using Scenery/Cities/LasVegas (layer 112)
using Scenery/Global (layer 113)
using Scenery/Props (layer 114)
using Addon Scenery (layer 115)
using MyTraffic (layer 116)
using Scenery/UtExcl (layer 117)
using Scenery/UtEurLights (layer 118)
using Scenery/UtLcVeg (layer 119)
using Scenery/UtLcCity (layer 120)
using Scenery/UtLcCustEur (layer 121)
using Scenery/UtEurRoad (layer 122)
using Scenery/UtEurRail (layer 123)
using Scenery/UtEurWater (layer 124)
using Scenery/UtEurStream (layer 125)
using Scenery/UtEurGP (layer 126)
using Scenery/UtObjRepo (layer 127)
using Scenery/UtWc (layer 128)
using Scenery/UtEurAirports (layer 129)
using Aerosoft/PBY_Catalina (layer 130)
using OZx_World/Grand_Canyon_KGCN (layer 131)
using Addon Scenery/Vagar Airport FSX & FS9 (layer 132)
using B:/FSX/Addon Scenery/Bornholm Island 2011 X/EKRN (layer 133)
using B:/FSX/aerosoft/Mega Airport Paris-Orly X (layer 134)
using Addon Scenery/FlightRivieraBP (layer 135)
using Addon Scenery/Riviera JetSet (layer 136)
using Aerosoft/Approaching LOWI X (layer 137)
using Aerosoft/Mega Airport London Heathrow (layer 138)
using B:/FSX/aerosoft/Mega Airport Frankfurt_LC (layer 139)
using aerosoft/German Airports 2_LC (layer 140)
using B:/FSX/aerosoft/Mega Airport Munich (layer 141)
using B:/FSX/aerosoft/Mega Airport Frankfurt (layer 142)
using aerosoft/German Airports 2 (layer 143)
using B:/FSX/Aerosoft/Madrid Barajas 2008 (layer 144)
using B:/FSX/aerosoft/Afd (layer 145)
using FsDreamTeam/ZurichX (layer 146)
using aerosoft/Mega Airport Budapest/LHBP_CITY (layer 147)
using aerosoft/Mega Airport Budapest/LHBP_AIRPORT (layer 148)
using Aerosoft/Santorini X (layer 149)
using Aerosoft/Venice X (layer 150)
using aerosoft/Amsterdam Schiphol X (layer 151)
using Aerosoft/Mega Airport Brussels X (layer 152)
using Aerosoft/Arlanda X (layer 153)
using B:/FSX/aerosoft/Mega Airport Oslo X (layer 154)
using Aerosoft/Mega Airport Barcelona X (layer 155)
using Aerosoft/Lisbon X (layer 156)
using aerosoft/Mega Airport Athen_LC (layer 157)
using aerosoft/Mega Airport Athen_SC (layer 158)
using aerosoft/Bari X (layer 159)
using Addon Scenery/FlyLogic_LSZA_Lugano (layer 160)
using Addon Scenery/FlyTampa-Vienna (layer 161)
using aerosoft/Corfu X (layer 162)
using OZx_World/PNG_mesh (layer 163)
using B:/FSX/Addon Scenery/EPKK Krakow Balice 2012 X (layer 164)
using B:/FSX/Addon Scenery/Polish Airports vol.2/EPLL_X (layer 165)
using B:/FSX/Addon Scenery/Polish Airports vol.2/EPSC_X (layer 166)
using B:/FSX/Addon Scenery/Polish Airports vol.2/EPZG_X (layer 167)
using B:/FSX/Addon Scenery/Polish Airports vol.3/EPPO_X (layer 168)
using B:/FSX/Addon Scenery/Polish Airports vol.3/EPBY_X (layer 169)
using B:/FSX/Addon Scenery/Polish Airports vol.3/EPWR_X (layer 170)
using aerosoft/Airport Toulouse (layer 171)
using Aerosoft/Mallorca X Ground (layer 172)
using Aerosoft/Mallorca X SC (layer 173)
using aerosoft/Heraklion X/Heraklion X_3_LC (layer 174)
using aerosoft/Heraklion X/Heraklion X_2_Scenery (layer 175)
using aerosoft/Heraklion X/Heraklion X_1 (layer 176)
using aerosoft/VILNIUS Airport (layer 177)
using aerosoft/VILNIUS city (layer 178)
using aerosoft/Mega Airport Helsinki (layer 179)
using Addon Scenery/Billund Airport X (layer 180)
using B:/FSX/SimMarket/EKCH Copenhagen Kastrup X/EKCH-TERRAIN (layer 181)
using B:/FSX/SimMarket/EKCH Copenhagen Kastrup X/EKCH-X (layer 182)
using ORBX/FTX_OLC/OLC_AA (layer 183)
using ORBX/FTX_OLC/OLC_EU1 (layer 184)
using ORBX/FTX_NZ/FTX_NZSI_08_CUSTOM (layer 185)
using ORBX/FTX_NZ/FTX_NZSI_07_MESH (layer 186)
using ORBX/FTX_NZ/FTX_NZSI_06_CVX (layer 187)
using ORBX/FTX_NZ/FTX_NZSI_05_SCENERY (layer 188)
using ORBX/FTX_NZ/FTX_NZNI_08_CUSTOM (layer 189)
using ORBX/FTX_NZ/FTX_NZNI_07_MESH (layer 190)
using ORBX/FTX_NZ/FTX_NZNI_06_CVX (layer 191)
using ORBX/FTX_NZ/FTX_NZNI_05_SCENERY (layer 192)
using ORBX/FTX_NA/FTX_NA_SAK08_CUSTOM (layer 193)
using ORBX/FTX_NA/FTX_NA_SAK07_MESH (layer 194)
using ORBX/FTX_NA/FTX_NA_SAK06_CVX (layer 195)
using ORBX/FTX_NA/FTX_NA_SAK05_SCENERY (layer 196)
using ORBX/FTX_NA/FTX_NA_PNW08_CUSTOM (layer 197)
using ORBX/FTX_NA/FTX_NA_PNW07_MESH (layer 198)
using ORBX/FTX_NA/FTX_NA_PNW06_CVX (layer 199)
using ORBX/FTX_NA/FTX_NA_PNW05_SCENERY (layer 200)
using ORBX/FTX_NA/FTX_NA_PFJ08_CUSTOM (layer 201)
using ORBX/FTX_NA/FTX_NA_PFJ07_MESH (layer 202)
using ORBX/FTX_NA/FTX_NA_PFJ06_CVX (layer 203)
using ORBX/FTX_NA/FTX_NA_PFJ05_SCENERY (layer 204)
using ORBX/FTX_NA/FTX_NA_NRM08_CUSTOM (layer 205)
using ORBX/FTX_NA/FTX_NA_NRM07_MESH (layer 206)
using ORBX/FTX_NA/FTX_NA_NRM06_CVX (layer 207)
using ORBX/FTX_NA/FTX_NA_NRM05_SCENERY (layer 208)
using ORBX/FTX_NA/FTX_NA_CRM08_CUSTOM (layer 209)
using ORBX/FTX_NA/FTX_NA_CRM07_MESH (layer 210)
using ORBX/FTX_NA/FTX_NA_CRM06_CVX (layer 211)
using ORBX/FTX_NA/FTX_NA_CRM05_SCENERY (layer 212)
using ORBX/FTX_EU/FTX_EU_WLS_08_CUSTOM (layer 213)
using ORBX/FTX_EU/FTX_EU_WLS_07_MESH (layer 214)
using ORBX/FTX_EU/FTX_EU_WLS_06_CVX (layer 215)
using ORBX/FTX_EU/FTX_EU_WLS_05_SCENERY (layer 216)
using ORBX/FTX_EU/FTX_EU_SCO_08_CUSTOM (layer 217)
using ORBX/FTX_EU/FTX_EU_SCO_07_MESH (layer 218)
using ORBX/FTX_EU/FTX_EU_SCO_06_CVX (layer 219)
using ORBX/FTX_EU/FTX_EU_SCO_05_SCENERY (layer 220)
using ORBX/FTX_EU/FTX_EU_ENG_08_CUSTOM (layer 221)
using ORBX/FTX_EU/FTX_EU_ENG_07_MESH (layer 222)
using ORBX/FTX_EU/FTX_EU_ENG_06_CVX (layer 223)
using ORBX/FTX_EU/FTX_EU_ENG_05_SCENERY (layer 224)
using ORBX/FTX_NA/FTX_AA_WA56 (layer 225)
using ORBX/FTX_NZ/FTX_AA_NZMF (layer 226)
using ORBX/FTX_NA/FTX_AA_KORS (layer 227)
using ORBX/FTX_NA/FTX_AA_KJAC (layer 228)
using ORBX/FTX_NA/FTX_AA_KCMW (layer 229)
using ORBX/FTX_EU/FTX_AA_EGFF (layer 230)
using ORBX/FTX_NA/FTX_AA_CZST (layer 231)
using ORBX/FTX_NA/FTX_AA_CYBD (layer 232)
using ORBX/FTX_NA/FTX_AA_3W5 (layer 233)
using ORBX/FTX_NA/FTX_AA_1S2 (layer 234)
using ORBX/FTX_AU/FTXAU48_CUSTOM (layer 235)
using ORBX/FTX_AU/FTXAU46_SHORES (layer 236)
using ORBX/FTX_AU/FTXAU45_SCENERY (layer 237)
using ORBX/FTX_AU/FTXAU38_CUSTOM (layer 238)
using ORBX/FTX_AU/FTXAU36_SHORES (layer 239)
using ORBX/FTX_AU/FTXAU35_SCENERY (layer 240)
using ORBX/FTX_AU/FTXAU28_CUSTOM (layer 241)
using ORBX/FTX_AU/FTXAU26_SHORES (layer 242)
using ORBX/FTX_AU/FTXAU25_SCENERY (layer 243)
using ORBX/FTX_AU/FTXAU18_CUSTOM (layer 244)
using ORBX/FTX_AU/FTXAU16_SHORES (layer 245)
using ORBX/FTX_AU/FTXAU15_SCENERY (layer 246)
using ORBX/FTX_AU/FTXAU05_ROADS (layer 247)
using ORBX/FTX_AU/FTXAA_YMML (layer 248)
using ORBX/FTX_AU/FTXAA_YBCS (layer 249)
using ORBX/FTX_AU/FTXAA_YBBN (layer 250)
using ORBX/FTX_AU/FTXAA_YBAS (layer 251)
using ORBX/FTX_AU/FTXAA_ORBXLIBS (layer 253)
using FsDreamTeam/LSGG (layer 252)
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 Danish_Denmark.1252
SharedMemInterface connected
Loading aircraft data from Airplanes\b747_400
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Loading airport KDEN from B:/FSX/Scenery/0202/scenery/APX20170.bgl
Loading aircraft data from Airplanes\CS_B767-300
intelliscene.cfg provides aircraft data with priority 1
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Loading airport LIMC from B:/FSX/Scenery/0601/scenery/APX50150.bgl
-
Suddenly my GSX is crashing regardless of any command, any airport and any aircraft. The issue seems to have started from implementation of the latest Addon Manager.
The Addon Manager doesn't have anything to do with this.
couatl v2.0 (build 2348)
Are you SURE you tried a reinstall ? This shows you don't have the very latest version, you are one version behind, and the most current one, is supposed to prevent exactly the error you are listing here, the "RuntimeError: Couatl.Application already showing a dialog"
Please reinstall NOW, and it should be working.
-
Aha..!!
Interesting and promising!
But how would I be able to specificly install the latest Couatl version. From inside FSX it tells me that I have the latest version and offer to do a reinstall of that, which I've tried a million times now. Also, as I wrote, I tried a clean uninstall and install from the latest setup version downloaded from your site. Could it possibly be some evil left over in the registry or perhaps some folders?! - If so, how would I get rid of that, once and for all?!!
-
But how would I be able to specificly install the latest Couatl version
Just follow what I've said. I've said "reinstall NOW", which means it's the only thing you have to do. The Couatl.exe is DOWNLOADED online, each time you run any of our installers. That's why I've said to reinstall. If you had to do something more, I would said so.
From inside FSX it tells me that I have the latest version
You are confusing again GSX, Couatl and the Addon Manager. Even if you have the most current GSX minor update, or the latest Addon Manager, it doesn't mean you also have the latest Couatl.exe. This becasue, Couatl.exe can be obtained only by reinstalling, because it's not possible to update it while FSX is running, so the self-update can't update the running Couatl.exe, while it's running.
which I've tried a million times now.
Have you tried it NOW ? Your error log it's from yesterday, and it shows the previous version. The newest one is online exactly from yesterday, that's why I've said "reinstall NOW".
-
I certainly appreciate your help very much Virtuali, but please stop your arrogant tone! - remember that it's not me causing all these problems - it originally comes from a faulty script made from you!
My approach to you has always been positive and gentle until now, that is, therefore I would appreciate the same approach from you!
Secondly you don't seem to read my post profoundly enough - as I wrote, among many other things, I have already downloaded and installed the latest "gsx_fsx_setup.exe" and tried to do a clean install with this, leaving me with same problems as usual.
If this install still didn't make it right, it is obviously completely out of my hands to know how to get on from here!
Thirdly if I with my knowledge and skills is about to misunderstand anything here it would clearly come from an unhandy and confusing install procedure and nothing else!
Thank you
-
1. I have right NOW downloaded gsx_fsx_setup.exe from your website and reinstalled the application.
2. The Couatl.exe inside FSX\fsdreamteam\couatl says NOW: 2.0 Build 2348
3. I have NOW tried FSX, enabled logging, and tried to execute GSX and the problem is still present and has not been solved.
4. When I then look into the Couatl.err log the newly error incidence has NOT been logged at all. Only the same old log from yesterday evening is present which I already has presented i the forum.
5. What I asked you about before and in which you didn't answer me, was if some "evil stuff" eventually was left behind and if I should get rid of all that before reinstalling. As there don't seem to be any proper deep cleaning uninstaller present, I will now anyway try and delete all traces of the program - that is, all the folders and so on before I try and make another reinstall, however not from the registry which will leave to you to explain me later if things still not work out.
So I just did and the problem STILL exists! I emptied all folders, including FSX\fsdreamteam\couatl with the couatl.exe 2.0 Build 2348. As I wrote I have just downloaded gsx_fsx_setup.exe now from your website and installed it and still is says couatl.exe 2.0 Build 2348, so I really can't understand what you just should have renewed here..?! I enabled the Panic log, but there has been no log.err created at all...
I give up! Can't do anything more from here...
Would you mind to mail or give me a direct link to your very new coautl.exe as your gsx_fsx_setup installer obviously doesn't provide the newest coautl.exe version?! - It still provides the old faulty version 2.0 Build 2348..!!!
As this wasn't enough, if I then put the aircraft to Geneva or Zurich the application crashes with your whole addon section gone even before I touch anything, resulting in immediate disappearance of all buildings!
-
Coutatl.err:
couatl v2.0 (build 2348)
panic log started on Thu Aug 08 01:22:25 2013
Traceback (most recent call last):
File "couatl\common\__init__.py", line 22, in <lambda>
RuntimeError: Couatl.Application already showing a dialog
Couatl.log:
couatl v2.0 (build 2348)
log started on Fri Aug 09 03:31:30 2013
<omissis>
Couatl.err is always appended to, while Couatl.log is overwritten with each execution, so unless you truncated Couatl.err, the banners show that these two logs have been produced at different times. Assuming you provided us with unmodified logs, this means that the crash you experienced on Friday 9 is unrelated with the crash you experienced on Thursday 8. The Thursday problem described in Couatl.err should be fixed with our latest build, which is 2350. The Friday problem described in Couatl.log is a mistery, however, because the log doesn't show any anomaly whatsoever that provides a hint about the reason Couatl crashed.
If you are still not getting version 2350, there may be reasons that don't depend on us, like caching and proxying. We'll double check the file on our servers, but in the meantime you could try downloading Coualt again, making sure your browser is not using a proxy. It would also help to delete the couatl.err to check if it gets regenerated correctly after a crash.
PS: by the way, even the problem on Thursday is kind of a mistery. The code that triggers the message has been there since the first release of Couatl (which predates the release of GSX, so we are talking about three years ago) and has never been a source of crashes. There must be something new and unforeseen that is happening on your machine that is triggering a dialog while another dialog is currently shown. The new version gracefully handles the "double dialog" case, yet we should investigate further about why this case is actually occurring, because it may be a symptom of another problem.
-
Would you mind to mail or give me a direct link to your very new coautl.exe as your gsx_fsx_setup installer obviously doesn't provide the newest coautl.exe version?! - It still provides the old faulty version 2.0 Build 2348..!!!
The 2348 version is not "faulty", it's working perfectly for all users since many months. It didn't worked on YOUR system, which is why we made an update that should hopefully fix YOUR specific problem that doesn't happen to anybody else.
Try to update using the Stand-Alone Addon Manager instead.
-
Thanks for help - The only way I could get the new Couatl.exe 2.0 build 2350 was through installing from the latest Stand alone addon manager.
However the problem still exists!!!
Could it eventually be some lack of Microsofts stupid "rights" to certain folders or XML files. Even though my UAC is turned off, certain incidences of that kind turns up now and then. However, other addons, as REX, Sim Psychics, etc works alright though...
-
However the problem still exists!!!
And does your error log shows any difference now ?
-
No new error log has been created!
So I guess it's the same old script problem that causes the crash....
-
PS: by the way, even the problem on Thursday is kind of a mistery. The code that triggers the message has been there since the first release of Couatl (which predates the release of GSX, so we are talking about three years ago) and has never been a source of crashes. There must be something new and unforeseen that is happening on your machine that is triggering a dialog while another dialog is currently shown. The new version gracefully handles the "double dialog" case, yet we should investigate further about why this case is actually occurring, because it may be a symptom of another problem.
Thanks indeed Ganesh for your involvement here with Umberto...
Is there anything I can do from here? - other log files to examine, registry editing perhaps..anything?!
-
Still no clue...or what??!!
Yesterday, after backing up my harddisk, I went back to the time when the problem started and uninstalled all non-FSX applications (already tried to unistall any FSX application with no success) but the GSX crash remains anyway with the same error cause!
Also updated any possible system files - Graphic drivers, sound drivers, chip set. No difference!
Also I noticed that, at the time when the crash started a windows update had just implemented quite a few updates - among these several NET framework additions, involving NET 3.5.1, 4 and 4,5.
In my eyes the Couatl (memory) error log COULD potentially indicates a possible NET Framework conflict, caused either by Couatl incompatibility with new NET Framework files OR a faulty installation from Windows Update of the new NET files..??
Error log:
Lognavn: Application
Kilde: Application Error
Dato: 25-08-2013 00:52:50
Hændelses-id: 1000
Opgavekategori:(100)
Niveau: Fejl
Nøgleord: Klassisk
Bruger: I/T
Computer: Morten-pc
Beskrivelse:
Navn på program med fejl: couatl.exe, version: 2.0.0.2348, tidsstempel: 0x511a6b6c
Navn på modul med fejl: couatl.exe, version: 2.0.0.2348, tidsstempel: 0x511a6b6c
Undtagelseskode: 0xc0000005
Forskydning med fejl 0x00002916
Proces-id 0x1578
Programmets starttidspunkt 0x01cea11c6a107578
Programsti: B:\FSX\fsdreamteam\couatl\couatl.exe
Modulsti: B:\FSX\fsdreamteam\couatl\couatl.exe
Rapport-id: e66b3516-0d0f-11e3-8891-6cf04952d000
Hændelses-Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-24T22:52:50.000000000Z" />
<EventRecordID>134670</EventRecordID>
<Channel>Application</Channel>
<Computer>Morten-pc</Computer>
<Security />
</System>
<EventData>
<Data>couatl.exe</Data>
<Data>2.0.0.2348</Data>
<Data>511a6b6c</Data>
<Data>couatl.exe</Data>
<Data>2.0.0.2348</Data>
<Data>511a6b6c</Data>
<Data>c0000005</Data>
<Data>00002916</Data>
<Data>1578</Data>
<Data>01cea11c6a107578</Data>
<Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data>
<Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data>
<Data>e66b3516-0d0f-11e3-8891-6cf04952d000</Data>
</EventData>
</Event>
-
You're claiming that my error is unique and no one else has had this problem.
But as I has noticed looking through the forum I can see that another of your customers has a similar unsolved problem:
http://www.fsdreamteam.com/forum/index.php?topic=8900.0
His Couatl error log looks like this:
couatl v2.0 (build 2348)
panic log started on Sun Jul 14 21:12:47 2013
Traceback (most recent call last):
File "couatl\GSX\__init__.py", line 199, in <lambda>
RuntimeError: Couatl.Application already showing a dialog
And here is mine:
couatl v2.0 (build 2348)
panic log started on Thu Aug 08 01:22:25 2013
Traceback (most recent call last):
File "couatl\common\__init__.py", line 22, in <lambda>
RuntimeError: Couatl.Application already showing a dialog
(By now my Couatl version is 2352 - but the problem is still the same)
So really, how do we eliminate this conflict..?!
-
You're claiming that my error is unique and no one else has had this problem. But as I has noticed looking through the forum I can see that another of your customers has a similar unsolved problem:
1 or 2 users doesn't make the slightest difference.
The only possible explanation is, that one only other user that had this, has by some chance, installed the same external non-GSX related product which is causing the problem to you. The issue is, you need to find what's doing it.
We were never been able to replicate this in ANY way (and NO other user except TWO), and replicating it is the only way to be able to fix it.
Without being able to replicate it, we can only tell you to proceed by exclusion, and remove EVERY possible running program, one by one, then re-enable them one by one, until you find the offending one.
-
Umberto, for crying out loud....I've done every possible thing now!
Disabled ALL FSX addons (as you know)
Unistalled ALL FSX addons (nevertheless)
Reinstalled GSX (a thousand times..)
Uninstalled ALL non-fsx programs around the time the error occurred out of nowhere..!
Uninstalled ALL Windows updates around the time the error occurred
Updated ALL graphic, sound and chip drivers
Deep scanned my harddisks for any possible virus, mallware, bad programs, everything!
Manually removed ALL known bad uninstalled program entries in my registry
Uninstalled/reinstalled ALL VS2005 packages according to your instructions.
FSX with each and EVERY OTHER addon is working perfectly here!
Not that I'm accusing you or anything, but what is possibly left anymore to check..?!
The only thing I possible can think of, if anything, is a new Logitech mouse I installed around the error-time and a silly FSX Booster application-tryout which I immediately uninstalled again - and bringing my old FSX.CFG back in place!
(Also I haven't yet tried a FSX SP2 repair - which I'm NOT prepared to do just because of a Couatl.exe not working for me for the time being - It took me 3 years to build up my present 10 monitor cockpit setup, so with a repair for the only sake of a non working Couatl I would be back to zero!)
-
Umberto, for crying out loud....I've done every possible thing now!
Then some of those products Uninstallers don't probably everything, so what's causing this, is still there.
Uninstalled ALL non-fsx programs around the time the error occurred out of nowhere..!
This sentence SEEMS to indicate that GSX USED to work on your system, at one time. If this is the case, maybe you can try to remember what changes you made to your system about that time.
It took me 3 years to build up my present 10 monitor cockpit setup, so with a repair for the only sake of a non working Couatl I would be back to zero!)
Are you using 10 monitors on a SINGLE PC ? If yes, that might be an issue, since nobody of us ever tested GSX in such configuration and, as you might say, chance we'll ever do this, is even less than zero...
If, instead, you are not running 10 monitors on the same system and you are using a network, then why mentioning them in the first place ? GSX is not network-aware, it always run on a single system so, the only work you'll have to do, would be on the one that runs GSX, not the others in the network.
-
Then some of those products Uninstallers don't probably everything, so what's causing this, is still there.
Good point - just don't no where to look for any further left overs
This sentence SEEMS to indicate that GSX USED to work on your system, at one time. If this is the case, maybe you can try to remember what changes you made to your system about that time.
Yes indeed, Umberto! I've had GSX all the way from the time you introduced it!!
"Try to remember what changes you made.." But what do you think I was doing..?! that is exactly what I've already done and described to you in details above and via mail!
Are you using 10 monitors on a SINGLE PC ? If yes, that might be an issue, since nobody of us ever tested GSX in such configuration and, as you might say, chance we'll ever do this, is even less than zero...
Arhh okay how silly of me, should never have mentioned that, bringing things out of focus - it was just meant to emphasize how much I take flying seriously and how important GSX is in that context. No problems with the monitor setup, whatsoever! FSX with GSX is only installed on the server PC with 8 of the monitors hooked up through 2 x Tripleheads2go and 2 x graphic boards. The other client PC in network has 2 monitors and ONLY deals with FSCommander and a moving map through Google maps. In other words, GSX is ONLY on the main PC with its dedicated monitors and everything has worked flawlessly until now!
If, instead, you are not running 10 monitors on the same system and you are using a network, then why mentioning them in the first place ? GSX is not network-aware, it always run on a single system so, the only work you'll have to do, would be on the one that runs GSX, not the others in the network.
As mentioned above GSX is NOT running in network. Please forget all about the setup - not an issue in this context!
-
Are you really sure you're fully compatible with newish REX update and so forth?!! This is really a drag, that you don't have any idea what the heck is going on!
If it just was GSX suffering - but all of my addons, Zürich and Geneva are totally dead because of this malfunctioning Couatl.exe...!
until you invent some kind of patch for this error, overruling obvious things - it seems that my only alternative is Aerosoft and their blackmail bullshit point AES system!
Come on now!!!
-
Are you really sure you're fully compatible with newish REX update and so forth?!!
We don't have the slightest idea about REX compatibility. REX is known to have caused issues with many products in the past. One of their installers, by mistake, completely wiped out the DLL.XML files for example.
But that's not the point. The point is that we can't never, ever, test our products with anything that's out there. There are too many FSX products that can cause problems, that if we really had to test all of them, we would have to stop developing products, and transform us into a full time testing company.
Assuming the latest REX update IS the cause, how do you expect US to fix something that has started by THEIR update, after you said yourself that Couatl and all our products USED to work without any problems BEFORE ?
If it just was GSX suffering - but all of my addons, Zürich and Geneva are totally dead because of this malfunctioning Couatl.exe...!
Not exactly. All your FSDT Add-ons are totally dead because some OTHER (still unknown) product has CAUSED Couatl to stop working.
until you invent some kind of patch for this error
It's not easy to patch something without being able to replicate the error in any way. As I've said, until today, out of the several THOUSANDS of GSX customers, there are only TWO reported cases.
So, it's obvious that, you two guys, are being unlucky enough to have installed the same troublesome combination of software, which doesn't seem to be very common.
-
Yesterday, after backing up my harddisk, I tried to unistall each and every program, FSapp, MS update, EVERYTHING from around the time when the error started - NO difference. GSX still crashes!
In order to help me sort this out I would like you to please consider these aspects:
In this my MS error log, why the heck are there 2 identical instances of <Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data> right after each other?! As if the problem not directly comes from another app interference, but simply because the Couatl.exe for some reason is being executed twice at the same time, which in my simple eyes could be the actual reason for the crash?:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-24T22:52:50.000000000Z" />
<EventRecordID>134670</EventRecordID>
<Channel>Application</Channel>
<Computer>Morten-pc</Computer>
<Security />
</System>
<EventData>
<Data>couatl.exe</Data>
<Data>2.0.0.2348</Data>
<Data>511a6b6c</Data>
<Data>couatl.exe</Data>
<Data>2.0.0.2348</Data>
<Data>511a6b6c</Data>
<Data>c0000005</Data>
<Data>00002916</Data>
<Data>1578</Data>
<Data>01cea11c6a107578</Data>
<Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data>
<Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data>
<Data>e66b3516-0d0f-11e3-8891-6cf04952d000</Data>
</EventData>
</Event>
So if the double execution of the Couatl.exe is the actual reason for the crash (Please confirm about agreeing or not), could it then be because of:
1. a somehow corrupted user account?
2. perhaps two user accounts in conflict?
3. the fact that I sometimes have been reinstalling GSX as an administrator and sometimes not?
-
Yesterday, after backing up my harddisk, I tried to unistall each and every program, FSapp, MS update, EVERYTHING from around the time when the error started - NO difference. GSX still crashes!
As I've said in my previous message:
Then some of those products Uninstallers don't probably everything, so what's causing this, is still there.
What's the point of taking the time to backup your harddisk, and just uninstalling ? Uninstalling won't fix a problem in your Windows setup. Since you already took the step of doing a backup, just reinstall Windows, and the problem will surely go away.
In this my MS error log, why the heck are there 2 identical instances of <Data>B:\FSX\fsdreamteam\couatl\couatl.exe</Data> right after each other?! As if the problem not directly comes from another app interference, but simply because the Couatl.exe for some reason is being executed twice at the same time, which in my simple eyes could be the actual reason for the crash?:
Couatl.exe surely doesn't start twice by itself. So, the most likely issue is, there's something in your system that is causing it to start twice. But, do you SEE two instances of it in the Task Manager ?
-
Just to recall, we already been through checking the process list and you don't see 2 Couatl.exe processes inside there - perhaps because the Couatl process crash immediately when any command is executed within GSX.
Reinstalling Windows is no option! - as I wrote you before it took me years to build up this setup which is quite complex but never has suffered from something so stupid as this.
When you're not answering me on the possibility of an user account conflict - is that because you don't agree or is it because you don't know?!
Another thing, when I run through your GSX update history I notice Jun 15th 2013: "Added support for Flightbeam KIAD and initial support for Majestic Q400 and cargo loading from left side" This is in fact about this time when my problem started. Do you by any chance still have some "install ingredients" before this update, so I could test it?
-
Hmmm...never seem to get any qualified answer from here!
Anyway, as from reading through this forum and from what I learned elsewhere this Couatl app is simply too unstable to do the job!
As if this wasn't enough you've also chosen to tie up all of your airport products to this wobbling app, which means that whenever the app is out of order all your airports turns dead in the same instance with crippled and missing buildings all over the place - in my case, both Zürich and Geneva airports which I bought from you in good faith are now totally useless!
So instead of one product from you not working I now have 3 products that I paid you for - all crippled with errors.
Now how can you possibly justify such a bad arrangement?!
As things turns out I'll obviously expect a refund from you, at least for the airports!
-
Anyway, as from reading through this forum and from what I learned elsewhere this Couatl app is simply too unstable to do the job!
It obviously isn't, and reasons for this have been clearly explained and proved, here and on other places too.. And YOU said yourself that it USED to work before so, how could possibly be a "Couatl problem" ? As usual, Couatl is AFFECTED (=is the victim) of something else in your Windows install.
As things turns out I'll obviously expect a refund from you, at least for the airports!
You should ask a refund to the software that you installed at a certain point, which caused this. You can't just but the blame on our software, which has proven to work on YOUR system already, just because you can't remember what you installed, and you are not prepared to reinstall Windows, which you should do only because you can't find or remember what the problem was.
As I've said, doing a backup and uninstalling was a complete waste time. Uninstalling a software will NOT fix a problem in your Windows installation. And why taking the time to do a backup in the first place, if you are not prepared to do a restore, which means reinstalling Windows and restoring from that backup ? You could have saved your time doing a backup, if you never intended to restore. Uninstalling and reinstalling can be done by the installers, a backup is made when reinstalling Windows.
-
I took the (harddisk image) backup in order not needing to reinstall all the suspected applications and updates I would later uninstall in a test analyze session.
But never mind if you don't agree or understand the purpose of that!
And why taking the time to do a backup in the first place, if you are not prepared to do a restore, which means reinstalling Windows and restoring from that backup?
Don't get that...or perhaps we're not talking about backup to the same extend here?
As I see it, If I took a full 1:1 image backup now, including the Couatl conflict, system files and everything as it is - then reinstalled Windows - and THEN on top of that did a complete 1:1 image restore from the image backup, then in my eyes everything would be completely overwritten back to the old status including the Couatl conflict and everything.
-
As I see it, If I took a full 1:1 image backup now, including the Couatl conflict, system files and everything as it is - then reinstalled Windows - and THEN on top of that did a complete 1:1 image restore from the image backup, then in my eyes everything would be completely overwritten back to the old status including the Couatl conflict and everything.
Of course. A 1:1 image backup is not what you should do in preparation for a Windows reinstall, it's only useful if you want to test something you think it might be dangerous, and want to be sure you can go back to a working system.
But that's the point. Right now, you don't have a "working" system that you want to go back to, you are trying to get rid of an issue which will surely be fixed by a Windows reinstall so, you shouldn't do a disk image, but rather a backup of your files and documents that you don't have an installer and that can't be downloaded.
But before doing that, what about trying a remote assistance session over Teamviewer ? Your problem is so unusual, that I would like to have a look at it. PM/email me if this is ok for you.
-
Of course. A 1:1 image backup is not what you should do in preparation for a Windows reinstall, it's only useful if you want to test something you think it might be dangerous, and want to be sure you can go back to a working system.
EXACTLY! That's the procedure I have been doing all a long and been trying to tell you! - TESTING by uninstalling all sorts of suspicious things from the period when problems started (with no luck) - and then back again restoring the 1:1 image. But perhaps I haven't explained myself well enough...
Yesterday, sort of against my principles, I tried to use ASE which worked fine - except for some occasionally g3d.dll error (again as the Couatl an 05 memory exception error) but after unplugging/plugging in my yoke the problem disappeared and everything worked fine again.
GSX was still not working, so uninstalled it but leaved on the Couatl.exe for your Geneva and Zürich addons. Then went to check these airports and saw that buildings still where missing only jetways where present..
But before doing that, what about trying a remote assistance session over Teamviewer ? Your problem is so unusual, that I would like to have a look at it. PM/email me if this is ok for you.
Hi hi, yes so unusual that it almost has become interesting! I appreciate your teamviewer offer and will send you an email soon so we can schedule a suitable time for it. :)