There is no listing in either DLL.XML, as would be expected, since this is a new P3DV4 installation, and I used all the new V4-compatible installers for my FSDT and Flightbeam airports.
The only entries in the two DLL.XML files are for the PMDG aircraft, and ASP4. I will inactivate those one at a time to see if it makes a difference.
I do know that the P3D process does not close immediately after exiting the sim and returning to the Windows desktop. It keeps running in the background for a few moments - I presume it is doing some post-run housekeeping tasks.
If I watch the active processes in Microsoft Process Explorer, when P3D is active, I see three other processes attached to P3D.exe: couatl, sode, and as_bstp, which is part of Active Sky.
In a normal exit from P3D, the couatl and sode processes disappear first, then after about 5 seconds, the P3D.exe process exits. The last to go is as_bstp (which appears to be running under cmd.exe), which ends once P3D.exe is done.
I see no real difference when exiting P3D when parked at a FSDT airport. The couatl and sode processes end first as usual. It is at the point where P3D.exe itself would normally stop running that the error message pops up relating to bglmanx64_unloaded. Until I acknowledge the error, P3D.exe keeps running. As soon as I acknowledge the error, P3D.exe finally exits, followed by as_btsp
Sent from my iPhone using Tapatalk
