Products Support > GSX Support FSX/P3D

P3Dv5 CTD with FSL A320 **SOLVED**

<< < (4/6) > >>

DVA12924:
The last minute or 2 of the SODE log:

[16:41:01.655] INFO SODE.FSLOOP : [SEASONALOBJECTHANDLER] Refreshing Season/Time Data...
[16:41:02.679] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:06.666] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:10.668] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:14.670] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:18.673] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:22.660] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:26.693] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:29.237] DEBUG SODE.FSLOOP : [API::TRIGGER] Received Trigger Client Data: ObjID [126], DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1, Mode=1
[16:41:29.284] DEBUG SODE.FSLOOP : [API::TRIGGER] Received Trigger Client Data: ObjID [126], DoorDesignator='4L', OwnFlag=1, DoorDataOverrideFlag=1, Mode=1
[16:41:30.665] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:34.667] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:38.670] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:42.672] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:46.690] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:50.661] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:54.679] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:58.682] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0, Primary/Chained Jobs:{0/0}, Tracked Jobs: {0}
[16:41:58.713] DEBUG SODE.FSLOOP : [API::TRIGGER] Received Trigger Client Data: ObjID [126], DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1, Mode=0
[16:42:27.767] FATAL SODE.WATCHDOG : Sim Process running test failed!
[16:42:27.776] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[16:42:27.793] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[16:42:27.793] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[16:42:27.900] INFO  : Terminate SODE.


The only errors I see in the SODE log at all:
[16:27:44.262] WARN SODE.SETTINGS : Could not extract 'Debug::FastJetwaysEnable' setting! Feature is disabled!
[16:27:44.262] WARN SODE.SETTINGS : Not all Settings have been read successfully! See above...

[16:27:44.286] WARN SODE.SETTINGS : Could not extract 'Debug::FastJetwaysEnable' setting! Feature is disabled!
[16:27:44.286] WARN SODE.SETTINGS : Not all Settings have been read successfully! See above...

[16:27:44.290] ERROR SODE.XML : Environmental Data Probe SimObject 'EDP_UUEE' must have absolute value for altitude, not AGL! EDP not added!

[16:27:44.390] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\TropicalSim_TFFF.xml'
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 4'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 5'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 6'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 6'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 7'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 8'. Must be 'CustomDesignator;Number'!
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 8'. Must be 'CustomDesignator;Number'!
[16:27:44.390] DEBUG SODE.XML : Building List from File 'C:\ProgramData\12bPilot\SODE\xml\TropicalSim_TNCC.xml'
[16:27:44.390] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 1'. Must be 'CustomDesignator;Number'!
[16:27:44.391] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 2'. Must be 'CustomDesignator;Number'!
[16:27:44.391] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 3'. Must be 'CustomDesignator;Number'!
[16:27:44.391] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 4'. Must be 'CustomDesignator;Number'!
[16:27:44.391] WARN SODE.XML : <Stand> CustomDesignator Attribute invalid format 'Gate 5'. Must be 'CustomDesignator;Number'!


None of those seem to have any reason for causing a CTD at any airport, at any gate, using any type of jetway (Custom SODE or GSX SODE), and only in a specific aircraft, at a specific point in the function. Also, the last error message was logged 15 minutes before I called the jetway (I was looking over the aircraft options to make sure nothing there changed that could have been the cause).

I have a second copy of Windows that I use only for university class work and has virtually nothing installed on it. I'll see if I can download and install P3Dv5, GSX, and FSL A320 on that copy of windows and see what happens - That is as close as I am willing to come to "a full reinstall of windows and P3D"   ---- as I expected, I cannot activate P3D on the other copy of windows, so I cannot test this idea.

virtuali:

--- Quote ---[16:41:58.713] DEBUG SODE.FSLOOP : [API::TRIGGER] Received Trigger Client Data: ObjID [126], DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1, Mode=0
[16:42:27.767] FATAL SODE.WATCHDOG : Sim Process running test failed!

--- End quote ---

Apart from the usual mistakes in other sceneries SODE jetways definitions, which will cause those jetways not working when called from GSX but are surely not a possible reason for a crash, the above two lines indicates the following:

- In the first line, SODE received a command to trigger a jetway from GSX, and of course the command was correct and understood, since there are no errors reported about it. At this time the jetway started to move.

- The second line, which happened 30 seconds later, indicates SODE was also caught by surprise by the sim crashing, for reason that didn't had anything to do with GSX, since as you can see, no other commands came from GSX during the time the jetway was being moved.

This definitely prove GSX can't be the cause of the crash, for example if it mistakenly sent another jetway trigger command while SODE was still moving the jetway, which might possibly have confused it. Not that I wasn't sure of this ( it should happen with every airplane then ), but at least now you got another confirmation GSX didn't cause the crash, for example if it sent wrong commands to SODE, or at the wrong times.

About reinstalling P3D on a different PC for testing, it's extremely easy to do:

- Uninstall P3D from your main PC. This will NOT require any subsequent reinstallation of add-ons, provided you don't touch any folder after uninstalling it, but will RECLAIM your activation.

- Install P3D on a different PC, so it can be activated with the activation reclaimed from the 1st one.

- When you are done testing, uninstall P3D from the test PC, which will again reclaim its activation to be reused.

- Reinstall P3D and be absolutely sure you are reinstalling on the SAME folder it was installed before.

We do this uninstall\reinstall process like 10-15 times when a new Beta cycle for P3D starts, so I assure you it's safe and won't cause any issue to any installed add-ons, as long you keep reinstalling on the same folder.

DVA12924:
I will try that reinstall method shortly and see if I can get it to work. I am also posing on the FSL forums to see if they have any ideas but a FSL forum and google search turned up 0 results. I do not see a reason to post on SODE forums since SODE seems to be working fine also. If it is not GSX and not SODE, then it must be FSL and something conflicting with that aircraft. I cannot find a single error message anywhere - SODE log, GSX log, event viewer all come back clean.

virtuali:

--- Quote from: DVA12924 on May 06, 2022, 09:12:08 am ---If it is not GSX and not SODE, then it must be FSL and something conflicting with that aircraft.
--- End quote ---

Surely it's not GSX, not SODE and not FSL, otherwise it would have:

- Crashed for me ( that was the whole point of my first video )

- Crashed for somebody else, yet you can see yourself there are no similar threads.

So yes, it must be a combination with something else you installed.

DVA12924:
I have managed to get P3D reinstalled on the other Windows system, but I am struggling to get GSX installed - I either get an error in installation about not having access to the fonts folder or trying to launch GSX from P3D tells me that Live Update must be run but will never actually open (all AV and firewalls turned off during install, and install folder added to exclude lists). I've been extremely busy with work and classes so have not had time to really work on this much, but I will have time come Wednesday. I know the install issue is something I'm not doing right, just don't have the time right now to keep uninstalling and reinstalling to resolve the problem.

Navigation

[0] Message Index

[#] Next page

[*] Previous page