On 2/24/2020 at 9:43 AM, Ray Proudfoot said:

I’m happy to report the cause has been found and fixed. Last Friday Andrew Wilson at FSL recommended I uninstall GSX and SODE. Instead of uninstalling them I foolishly just disabled the two processes from running in the EXE.XML thinking it was the same.

But the CTDs persisted. Lefteris reminded me this morning that it was almost certainly scenery related as the CTDs happened at specific locations. So today I uninstalled both and a message appeared twice during the GSX uninstall stating default files would be restored.

Clearly that was the critical thing because two flights since were error free. Two benefits to this approach rather than the wipe and reinstall option. 1) loads of time saved and 2) the problem application has been identified.

A salutary lesson even to this old hand. I was barking up the wrong tree because of a coincidence. So even when you install a clean P3D do not forget any add-ons as those could be the cause.

I'd forward this to FSDT and SODE developers.

 

Where you using the new v1.6.6 version of SODE?

 

Version 1.6.6

• General
  • Fixed wrong page number display in the text menu
  • Fixed application crash when an (illegal) 5-letter ICAO airport designator was detected
  • Fixed handling of relative SimObject folders in add-on.xml, where the folder is defined just by its raw name and not with ‘.\’
• Jetway Control System
  • Fixed bug where SODE to GSX communication was lost when GSX resets the jetway while it was still moving
• VDGS
  • Changed the way how the aircraft type is detected. Now only the ICAO type designator in the aircraft.cfg is relevant.

Edited March 6, 20206 yr by udidwht

1 minute ago, udidwht said:

I'd forward this to FSDT and SODE developers.

I suspect it was a FSDT GSX file and did contact Umberto about it. He didn't seem bothered. Doubt SODE was to blame but no way of checking now.