Author Topic: coualt crash  (Read 10044 times)

gordon24

  • Newbie
  • *
  • Posts: 21
coualt crash
« on: April 03, 2012, 08:49:15 pm »
Hello,

I have all FSDT airport installed in FSX without problems but problems started when I tried to install GSX in trial mode.

It worked fine one day but now as soon as I start a flight, no matter the aiplane or airport, a few seconds later I have a popup telling me that coualt crashed....
I tried to reinstall GSX but same problem....

If I remove GSX completely (removing coualt and add-on manager) and then reinstall KLAX for exemple, no more crash, everything is back to normal....

Any ideas? I really would like to buy GSX once this problem will be solved...

http://img850.imageshack.us/img850/7135/coualt.jpg
« Last Edit: April 03, 2012, 09:54:45 pm by virtuali »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #1 on: April 03, 2012, 10:02:36 pm »
That's not a GSX problem, and the Couatl.exe that is installed with KLAX is exactly the same that is installed with GSX, since they are taken exactly from the same place so, there's no reason why it would crash with GSX and not with KLAX only.

The user in this thread:

http://www.fsdreamteam.com/forum/index.php?topic=6293.0

Had the same problem, it was related in some way with audio drivers, but he said that after disabling all security software (antivirus, antispyware, etc.) the problem was fixed.

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #2 on: April 03, 2012, 10:37:21 pm »
Thanks for your answer Umberto.

I have a hard time to understand why couatl is working fine with all my FSDT sceneries but crash as soon as I try to install GSX? Is there some functions only used by GSX that make it crash?

I followed the thread you mention but where can I find the error report that Robertoizzo is showing in his thread? Just to see if my problem is also related to an audio driver?
In fact I have that error popup telling me that couatl crashed but nothing else.... FSX is still working fine after the crash....

I tryed to uninstall the Realtek Audio driver but problem is still there...

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #3 on: April 03, 2012, 11:00:14 pm »
was able to get this, hope it helps.....

<?xml version="1.0" encoding="UTF-16" ?>
- <WERReportMetadata>
- <OSVersionInformation>
  <WindowsNTVersion>6.1</WindowsNTVersion>
  <Build>7601 Service Pack 1</Build>
  <Product>(0x1): Windows 7 Ultimate</Product>
  <Edition>Ultimate</Edition>
  <BuildString>7601.17727.amd64fre.win7sp1_gdr.111118-2330</BuildString>
  <Revision>1130</Revision>
  <Flavor>Multiprocessor Free</Flavor>
  <Architecture>X64</Architecture>
  <LCID>1033</LCID>
  </OSVersionInformation>
- <ParentProcessInformation>
  <ParentProcessId>4464</ParentProcessId>
  <ParentProcessPath>E:\Flight Simulator X\fsx.exe</ParentProcessPath>
  <ParentProcessCmdLine>"E:\Flight Simulator X\fsx.exe"</ParentProcessCmdLine>
  </ParentProcessInformation>
- <ProblemSignatures>
  <EventType>APPCRASH</EventType>
  <Parameter0>couatl.exe</Parameter0>
  <Parameter1>2.0.0.2303</Parameter1>
  <Parameter2>4f4e3d0d</Parameter2>
  <Parameter3>python25.dll</Parameter3>
  <Parameter4>2.5.2150.1013</Parameter4>
  <Parameter5>48832845</Parameter5>
  <Parameter6>c00000fd</Parameter6>
  <Parameter7>000cc537</Parameter7>
  </ProblemSignatures>
- <DynamicSignatures>
  <Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
  <Parameter2>1036</Parameter2>
  <Parameter22>4cbf</Parameter22>
  <Parameter23>4cbfc1f34ab826199dcbf5b097bad999</Parameter23>
  <Parameter24>4209</Parameter24>
  <Parameter25>420902ac53d2a6ee7992c96f09015894</Parameter25>
  </DynamicSignatures>
- <SystemInformation>
  <MID>FE406590-72F1-401C-8875-304BB9FE8572</MID>
  <SystemManufacturer>System manufacturer</SystemManufacturer>
  <SystemProductName>System Product Name</SystemProductName>
  <BIOSVersion>0808</BIOSVersion>
  </SystemInformation>
  </WERReportMetadata>

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #4 on: April 05, 2012, 08:10:34 pm »
Up!

No answer with the details I gave... Doesn't seems to be an issue with the audio drivers as a python.dll seems involved...

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #5 on: April 06, 2012, 01:47:14 am »
We don't have any idea of what might be, because it's a different issue than the audio drivers, it's Python itself that has crashed, and this is the first time we saw it.

Try to activate a log: open the Notepad and type the following on a new blank file:

logFile=couatl.log

(please note logFile is written beginning with a lower case l and a capital F )

Save the file as couatl.ini in the FSX\fsdreamteam\couatl folder, so it stays at the same level of the couatl.exe

Launch FSX, activate GSX, let it crash, and then exit from FSX, check if you have a Couatl.log file in the fsdreamteam\Couatl folder, and post its content here.

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #6 on: April 06, 2012, 09:57:46 pm »
here is the log Umberto:

Code: [Select]
couatl v2.0 (build 2303)
log started on Fri Apr 06 21:55:19 2012

connecting to SimConnect...
connected to FSX
bglmanx non ready yet, waiting.
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 16 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX loaded
Loading addon JFK
Addon JFK loaded
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 loaded
Loading addon KFLL
Addon KFLL loaded
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW loaded
Loading addon HAWAII1
Addon HAWAII1 loaded
Loading addon HAWAII2
Addon HAWAII2 loaded
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output(Optical) (Realtek High Definition Audio)
Created OpenAL device: Generic Software on Speakers (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
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 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 FsDreamTeam/ZurichX (layer 121)
  using FsDreamTeam/LSGG (layer 122)
  using FsDreamTeam/OHareX (layer 123)
  using FsDreamTeam/JFK (layer 124)
  using FsDreamTeam/KLAS (layer 125)
  using FsDreamTeam/KFLL (layer 126)
  using FsDreamTeam/kdfw (layer 127)
  using FsDreamTeam/PHLI (layer 128)
  using FsDreamTeam/PHTO (layer 129)
  using FsDreamTeam/PHOG (layer 130)
  using FsDreamTeam/PHKO (layer 131)
  using FsDreamTeam/KLAX_V2 (layer 132)
Airport cache not valid: scenery.cfg has changed since last time
Regenerating airport cache, looking for scenery files under E:/Flight Sim X/
Worker thread started
Addon GSX loaded
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
Starting system monitors
SharedMemInterface connected
GSX is in trial mode (state=0, activation=-25006)
Loading aircraft data from Airplanes\C172
aircraftDb.py provides aircraft data with priority 0
Using aircraft data from aircraftDb.py
Section [contact_points] contains invalid data at entry point.4

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #7 on: April 06, 2012, 10:01:11 pm »
Have you modified the C172 aircraft.cfg file ? The error log:

Quote
Section [contact_points] contains invalid data at entry point.4

Seems to indicate there's a problem with it, in the [contact_points] section, can you post its content ? Just the lines under the [contact_points] section should be enough.

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #8 on: April 06, 2012, 10:53:47 pm »
Code: [Select]
[contact_points]
point.0 = 1,  0.90,  0.00, -4.09, 1500, 0, 0.5, 22.0, 0.25,2.5, 0.7, 0.0, 0.0, 0
point.1 = 1, -4.70, -4.50, -4.01, 3500, 1, 0.5,  0.0, 0.3, 2.5, 0.7, 0.0, 0.0, 2
point.2 = 1, -4.70,  4.50, -4.01, 3500, 2, 0.5,  0.0, 0.3, 2.5, 0.7, 0.0, 0.0, 3
point.3 = 2, -3.90, -18.0,  3.00, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 5
point.4 = 2, -3.90   18.0,  3.00, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 6
point.5=  2,-20.23,   0.0,  0.30, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 9
point.6=  2,  1.48,   0.0, -2.17, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 4
point.7=  2,-22.80,   0.0,  5.83, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 7
point.8=  2, -4.90,   0.0, -2.00, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 8

max_number_of_points = 21

static_pitch=3.02                //degrees, pitch when at rest on the ground (+=Up, -=Dn)
static_cg_height=3.765           //feet, altitude of CG when at rest on the ground

Here it is....
But doing some investigations, I uninstalled and then reinstalled FSX completely from scratch today.
I then installed all my FSDT sceneries then GSX.... I changed nothing else

So the c172 file is fresh from a new FSX install.

I chose the fsx because this is the the default plane on the start menu. If I try to change it, then couatl crash as soon as I exit the aircraft selection screen.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #9 on: April 07, 2012, 12:09:23 pm »
So the c172 file is fresh from a new FSX install.

point.4 = 2, -3.90   18.0,  3.00, 1800, 0, 0.0,  0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 6

As the message said, there was an error in the 4 entry and yes, there is an error: as you can see the comma between the -3.90 and the 18.0 parameters is missing, this creates an illegal string, you might not notice in FSX because it's not a visual point, it's just one of the crash detection points, I guess that FSX is just ignoring it.

It wouldn't be the first time we find a mistake in a file supplied with FSX, for example, the GSX fixes the default 737 and 747 cfg files to enable the service doors, this might have slipped by, but it's still an error.

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #10 on: April 07, 2012, 01:10:22 pm »
I put the comma back and did the same with other default aircraft as some other commas were missing in the contact point sections but unfortunately, the problems remains....

And the log file is not giving much details

Code: [Select]
connected to bglmanx
Loading addons
requesting AddOn list to bglmanx
bglmanx list contains 16 AddOn(s)
Loading addon ZurichX
Addon ZurichX loaded
Loading addon OHareX
Addon OHareX loaded
Loading addon JFK
Addon JFK loaded
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 loaded
Loading addon KFLL
Addon KFLL loaded
Loading addon PHNL
Addon PHNL not installed or missing one or more files, skipping
Loading addon KDFW
Addon KDFW loaded
Loading addon HAWAII1
Addon HAWAII1 loaded
Loading addon HAWAII2
Addon HAWAII2 loaded
Loading addon KLAX
Addon KLAX loaded
Loading addon ParkMe
Addon ParkMe loaded
Loading addon GSX
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio)
  Generic Software on Realtek Digital Output(Optical) (Realtek High Definition Audio)
Created OpenAL device: Generic Software on Speakers (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
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 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 FsDreamTeam/ZurichX (layer 121)
  using FsDreamTeam/LSGG (layer 122)
  using FsDreamTeam/OHareX (layer 123)
  using FsDreamTeam/JFK (layer 124)
  using FsDreamTeam/KLAS (layer 125)
  using FsDreamTeam/KFLL (layer 126)
  using FsDreamTeam/kdfw (layer 127)
  using FsDreamTeam/PHLI (layer 128)
  using FsDreamTeam/PHTO (layer 129)
  using FsDreamTeam/PHOG (layer 130)
  using FsDreamTeam/PHKO (layer 131)
  using FsDreamTeam/KLAX_V2 (layer 132)
Airport cache not valid: scenery.cfg has changed since last time
Regenerating airport cache, looking for scenery files under E:/Flight Sim X/
Worker thread started
Addon GSX loaded
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
Starting system monitors
SharedMemInterface connected
GSX is in trial mode (state=0, activation=-25006)
Loading aircraft data from Airplanes\Aircreation_582SL
Using aircraft data from SimConnect

What is really strange is the fact that as long as I only install my FSDT scenes, everything is fine, no couatl problems at all... But as soon as I install GSX, then it crash....
Another strange thing is that the first time I installed GSX, it worked fine for one day (trial version). But the next day, it started to crash as it is doing right now... And it never came back as normal...
« Last Edit: April 07, 2012, 02:24:37 pm by gordon24 »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #11 on: April 07, 2012, 04:48:21 pm »
And the log file is not giving much details

In fact, the log doesn't indicate any errors right now. Are you sure you run it when Couatl crashed ?

Quote
What is really strange is the fact that as long as I only install my FSDT scenes, everything is fine, no couatl problems at all... But as soon as I install GSX, then it crash...

If the crash is caused by an illegal command in the aircraft.cfg, it's not strange at all it would appear with sceneries only, since they don't need to read that information.

Quote
Another strange thing is that the first time I installed GSX, it worked fine for one day (trial version). But the next day, it started to crash as it is doing right now... And it never came back as normal...

I'm sorry, but the log indicates it's not crashing anymore. So, either it's not, or you are not producing a log in the correct moment so, it's not possible to understand now what the problem is.

It's not strange that it crashed when you had the errors in the aircraft.cfg files, but it's simply shouldn't crash now, unless the log is incomplete.

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #12 on: April 07, 2012, 06:48:44 pm »
yep, the log was on but as indicated doesn't seem to report any problem. But couatl still crash as soon as my flight start or as soon as I exit the menu to select a new aircraft.....

I really don't know where the problem could be as I made many tries to solve it....

It is really unfortunate.... The good thing is that I can still use my FSDT scenes without troubles.... but right now, I can't convert my trial use of gsx into a purchase as nothing indicate the problem could be solved using the full version....

I will continue my investigations, maybe reinstalling W7 one day if I find enough courage... I will also try any new couatl version released in the future to see if by miracle my problems could be solved....

gordon24

  • Newbie
  • *
  • Posts: 21
Re: coualt crash
« Reply #13 on: April 08, 2012, 05:16:45 pm »
I'm stunned!!!!!

This afternoon, I again spent a few hours trying to deal with this problem and I found this thread, especially reply #26....
http://www.fsdreamteam.com/forum/index.php?topic=5536.15

So, I checked "Run this program as administrator" to couatl.exe and started FSX again.... To my surprise, no more couatl crash with the usual Microsoft Visual C++ runtime error window....

Unfortunately, no couatl menu in FSX and no answer when I pressed CTL+F12

So I exited FSX, turn off explicit admin rights to couatl.exe, started FSX again and guess what? No error and GSX was working perfectly at Milan Linate....

Ok that is a miracle but as I'm quite logical, I would like to know if you have an explanation for this Umberto?
Why do the fact to turn on and off "Run this program as administrator" suddenly solved my problem?

Anyway, I'm going to reinstall some add-ons ans see how it goes... The first time, it worked one day only so I'm just praying it will last longer that time....

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: coualt crash
« Reply #14 on: April 08, 2012, 10:01:19 pm »
Ok that is a miracle but as I'm quite logical, I would like to know if you have an explanation for this Umberto? Why do the fact to turn on and off "Run this program as administrator" suddenly solved my problem?

Is your user account of the "standard" (which really means "limited") type ? If yes, then you will likely need to run almost every FSX addon "As Administrator"

If, instead, your user account if of the "admin" type, you don't need to run anything as Administrator. NOTE, running "As Administrator" is NOT the same thing as setting up your user account with "Admin" type!

Normally, none of our products requires to run "As Administrator", unless your user account is of the limited type.