I tried KDFW at Gate B15 now, as in your last report, and there are no errors at all. See the attached screenshot. Are you *still* seeing such errors like "CREATE_OBJECT_FAILED" ?
Umberto, I believe I may have found the culprit. I reinstalled KDFW and tested the same scenario. Gate B15. All seemed to work just fine...at first. THEN...I reapplied Aerosoft's AES to KDFW...and that's when I got this:
couatl v3.1 (build 3527)
panic log started on Tue Jul 26 11:02:09 2016
problem raised by engine or unspecified addon
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Traffic_Cone2'
Traceback (most recent call last):
File "couatl\GSX\__init__.py", line 698, in onSimStart
File "couatl\GSX\__init__.py", line 682, in checkOnGroundState
File "couatl\GSX\assistanceServices\__init__.py", line 1380, in aircraftEngaged
File "couatl\GSX\assistanceServices\__init__.py", line 1439, in materializeTrafficCones
AssertionError: attempt to use an invalid SimObject instance
{'Airport': 'KDFW', 'User Pos': (32.902845069629784, -97.0451313535231, 187.415 m, 2.39023 m, 48.28200017609025)}
So I exited (had to use task manager) and removed the KDFW entries from the AES folder and restarted the sim. I immediately got a "coatl scripting error" and had to close the Coatl engine. This is the error detail from the Event Viewer: Log Name: Application
Source: Application Error
Date: 7/26/2016 11:05:07 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: EricsSim-PC
Description:
Faulting application name: couatl.exe, version: 3.1.0.3527, time stamp: 0x57923ce0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x7ebd001c
Faulting process id: 0x19ac
Faulting application start time: 0x01d1e74f18c9639a
Faulting application path: C:\MS FLIGHT SIM X\MSFSX\fsdreamteam\couatl\couatl.exe
Faulting module path: unknown
Report Id: 56a217d9-5342-11e6-990f-bcee7b726c13
Event 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="2016-07-26T15:05:07.000000000Z" />
<EventRecordID>9650</EventRecordID>
<Channel>Application</Channel>
<Computer>EricsSim-PC</Computer>
<Security />
</System>
<EventData>
<Data>couatl.exe</Data>
<Data>3.1.0.3527</Data>
<Data>57923ce0</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>7ebd001c</Data>
<Data>19ac</Data>
<Data>01d1e74f18c9639a</Data>
<Data>C:\MS FLIGHT SIM X\MSFSX\fsdreamteam\couatl\couatl.exe</Data>
<Data>unknown</Data>
<Data>56a217d9-5342-11e6-990f-bcee7b726c13</Data>
</EventData>
</Event>
And this: Log Name: Application
Source: Windows Error Reporting
Date: 7/26/2016 11:05:13 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: EricsSim-PC
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: couatl.exe
P2: 3.1.0.3527
P3: 57923ce0
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: 7ebd001c
P9:
P10:
Attached files:
These files may be available here:
C:\Users\Erics Sim\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_couatl.exe_f25e13dbd136e633d537a9eb04552c4d13fdfa5_0875cbc7
Analysis symbol:
Rechecking for solution: 0
Report Id: 56a217d9-5342-11e6-990f-bcee7b726c13
Report Status: 0
Event Xml:
<Event xmlns="
http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-07-26T15:05:13.000000000Z" />
<EventRecordID>9651</EventRecordID>
<Channel>Application</Channel>
<Computer>EricsSim-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>couatl.exe</Data>
<Data>3.1.0.3527</Data>
<Data>57923ce0</Data>
<Data>StackHash_0a9e</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>7ebd001c</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>C:\Users\Erics Sim\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_couatl.exe_f25e13dbd136e633d537a9eb04552c4d13fdfa5_0875cbc7</Data>
<Data>
</Data>
<Data>0</Data>
<Data>56a217d9-5342-11e6-990f-bcee7b726c13</Data>
<Data>0</Data>
</EventData>
</Event>
So I ran the latest Standalone Addon Manager (redownloaded this morning) and restarted the sim. That's when all h**l broke loose. Apparently there is a conflict between AES and Coatl. I'm not saying which is the cause, just pointing out the possible issue.
So I removed AES, GSX and KDFW. Tried to restart my sim. Turns out that during the 'conflict' between the two, my cfg became corrupted with a bunch of weird little symbols attached to each line of my cfg. No choice but to do a system restore to the day before.
So I've now reinstalled GSX and it seems to be functioning just fine. So I reinstalled KDFW (re-downloaded this morning) and this time....got the same errors at startup as above. "Coatl engine has stopped working". AES is not installed at this point. Just GSX and KDFW.
So I've uninstalled KDFW and have only GSX installed. Started the sim and no error on sim startup.
So my summary....I cannot get KDFW to install and function 100% without have the Coatl Engine crash on startup. And I cannot have both AES and KDFW installed at the same time either. This causes major issues.
Not sure if you can make something out of this mess but I'm just gonna run a freeware KDFW w/GSX until I can install without having a conflict completely rewrite my cfg and prevent me from flying. I've messed with this for two days now.
