September 25, 20214 yr Strictly Speaking, this is not about CTD, but the aftermath of that, so I think it deserves it's own topic. On my system, after a CTD of P3D(v4.5), it's very likely after a restart, some external software having problem on connecting to new started P3D, as if they are connected to the "ghost" of the crashed one. Those most prone to this phenomena on my system, is TrackIR, and LittleNavMap, also LINDA, FSX2ACMI..etc.... Activesky used to be one, but with the new ASP3D version, it almost never did that again. For TrackIR sometimes I neede to restart the TrackIR software after new P3D is running, it I restart it after CTD but before staring new P3D, it doesn't work, and the software almost always crash itself when new P3D is running and I try t shut TIR software down.... Also have instance that restart TIR alone doesn't work, I have to restart P3D for more times to get TIR working. LNM sometimes would connects fine, or works fine just try reconnecting, but if that doesn't work, restart LNM doesn't help, have to restart P3D. One annoying side effect I don't fully understand, is if LNM or FSX2ACMI stays open after P3D's CTD or even sometimes normal shutdown, after a few hour, it'll staring to prevent my internet connecting working, browser (both firefox and chrome on my system) even didn't try to refresh any page. but simply close the left over software would bring back my internet. If those phenomenons are just annoying, since I need to restart P3D again and maybe even again, I recently got into a series of event that cause 2nd CTD: Somehow TrackIR stopped working in pre-flight, TIR software shows it's still connected, but no luck try reconnect or restart TIR software. Restart P3D, Activesky, AirManager, FSCaptain, LINDA works fine, but still no TrackIR even after restart TIR software, and no LittleNavMap and no AI Companion. Restart P3D again, everything seems working again. AI Companion connects again. 1hour into per-flight and all fine. After TO, when climb to FL200, CTD. My AI Companion are set to remove all ground traffic when above FL200, normally it works fine, but in this series of event, I highly suspect it's the cause. But I'm not sure what causes the first TIR non-connecting, I wonder if there are way to see if there are ghost "simconnect" or "FSUIPC" left behind (I'm sure it's not shown on task manager or Process Explorer), and how to reset them if possible. Of Course restart my system would be a good way, but that's not always practical....
Archived
This topic is now archived and is closed to further replies.