January 23, 20215 yr Are 3rd party apps and software something to skip at the moment due to SimConnect related CTDs? I have been getting random crashes with OnAir, LNM and any other app which uses SimConnect, what is your experience on the matter? Iñigo Bildarratz
January 23, 20215 yr Affirmative! Intel i9-14900K, 64 GB RAM, MB ASUS ROG STRIX 790-E, NVIDIA GTX 4080 Super 16GB, 2 x 2 TB M.2, BE QUIET Pure Power 12 M 1000W, BE QUIET Silent Loop 3 360 AIO, BE QUIET Dark Base Pro 901, 4K-Monitor, Honeycomb Bravo Throttle Quadrant, Thrustmaster TCA Yoke, Streamdeck XL, Thrustmaster T.16000M Joystick, Saitek Rudder Pedals, WINCTRL PAP3, WINCTRL 3M PDC, JetMax 737 home cockpi
January 23, 20215 yr Commercial Member I have been doing a lot of SimConnect development, in fact, almost all Lorby apps use it. I have not seen any MSFS crashes that I could safely attribute to SimConnect itself. So it seems to be a very specific issue that only some apps exhibit. With the old sims there sometimes were problems like this with apps that were tracking AI traffic. But my copy of MSFS is all default, no mods whatsoever, so it seems likely that crashes could result from cross-compatibility issues (= several addons and/or mods conflicting with each other). What I can say though is, that MSFS is very sensitive to things happening on the USB ports, especially when HID devices are involved. I can make it stutter or even crash by starting any other application that deals with joysticks, mice, keyboards or other input devices. Best regards Edited January 23, 20215 yr by Lorby_SI LORBY-SI
January 23, 20215 yr A bug introduced in Sim Update II is indeed causing CTDs with SimConnect. Thread on MSFS forums (with an actual Asobo employee commenting): https://forums.flightsimulator.com/t/ctd-simconnect-failed-to-call-dispatch/349199/18 AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals
January 23, 20215 yr Commercial Member 1 minute ago, marsman2020 said: A bug introduced in Sim Update II is indeed causing CTDs with SimConnect. Thread on MSFS forums (with an actual Asobo employee commenting): https://forums.flightsimulator.com/t/ctd-simconnect-failed-to-call-dispatch/349199/18 That is about a very specific issue, it is not a blanket statement about SimConnect instability. The thread describes a crash hat occurs when a SimConnect client is forcing the sim to load a broken flight plan file (=one that is missing departure or arrival airport). And this is what Asobo says: Quote A known cause of this issue is SimConnect queries for missions/flightplans without origin and/or destination airports, independant of the source of the file. (...) external add-ons interacting with the flight plan could also trigger it. Until the fix is present in the live version, you might have to refrain from external add-ons interacting with the flight plan. Best regards LORBY-SI
January 23, 20215 yr 13 minutes ago, Lorby_SI said: That is about a very specific issue, it is not a blanket statement about SimConnect instability. The thread describes a crash hat occurs when a SimConnect client is forcing the sim to load a broken flight plan file (=one that is missing departure or arrival airport). And this is what Asobo says: Best regards There are several threads on the MSFS forums there the 'AFC Bridge' driver for the Honeycomb Bravo (which updates the gear lights) is triggering these as well. In addition to LittleNavMap (which sounds like it will be patched soon). Both of which are widely used items. And this one documented instance of a CTD shows that Asobo is likely not unit testing the SimConnect API with new patches, so there could be other stability issues with it as well. If the OP is seeing CTDs while using several different SimConnect tools it would be totally reasonable as a troubleshooting step try flying without them for a bit and see what happens. AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals
January 23, 20215 yr Author I have asked on OnAir discord for similar experiences and it doesnt´t seem to be the culprit. It looks like certain flightplans generated by LNM are triggering the CTD. I have the same exat crash in the same exact spot with a LNM generated flightplan,once with LNM conneceted via SimConnect and the other with LNM off but with a .pln generated by it. I am returning to the same spot with a MSFS generated flight plan and see what happens,... Iñigo Bildarratz
January 23, 20215 yr 1 hour ago, Lorby_SI said: ...What I can say though is, that MSFS is very sensitive to things happening on the USB ports, especially when HID devices are involved. I can make it stutter or even crash by starting any other application that deals with joysticks, mice, keyboards or other input devices. Yep, seen this one several times. Occasionally the key backlighting on my keyboard quits working and the only thing I've found that restores it is unplug/replug usb connector. Probably 50% of the times I've tried this it will crash MSFS. i7-6700k • Gigabyte GA-Z170X-UD5 • 32GB DDR4 2666 • EVGA FTW ULTRA RTX3080 12GB
January 23, 20215 yr Author Ok, no LNM this time at all. No Bravo hardware. SimConnect only thru OnAir. CTD on same spot. SimConnect is the only variable left. Sadly, no more flying for me until Asobo fixes it , hopefully, next week. Iñigo Bildarratz
January 23, 20215 yr There have been a couple of threads about scenery bugs causing CTDs in the exact same spot every time people fly by them. So if it's tied to your aircraft location it could be that. Example: https://forums.flightsimulator.com/t/100-reproducible-ctd-at-specific-coordinates-for-months-support-not-helping/324495/31 AMD 3950X | 64GB RAM | AMD 5700XT | CH Fighterstick / Pro Throttle / Pro Pedals
January 23, 20215 yr I was wondering if it was just me having issues lately. I've been trying to get to O'Hare since yesterday afternoon and every time, CTD (successfully landed once but then CTD while trying to get to a parking spot (should have just shut down on the runway so my OnAir job would have finished). No LNM or Honeycomb Bravo here. Using FSUIPC and Navigraph.
Archived
This topic is now archived and is closed to further replies.