October 23, 20214 yr Hello Gang! I haven't had any CTD's in a very long time until now after installing SU6. All my CTD's so far have happened with the Aerosoft CRJ and flying out of DD's KDCA. Same error - CTD Simconnect Failed to CallDispatch. I updated to SU6 yesterday and so far it's been a very solid update until this started to happen. Any ideas? Sincerely, Dennis D. Müllert System Specs: MoBo: MSI MAG X870 Tomahawk WiFi ATX AM5. CPU: AMD Ryzen 7 9800X3D. Memory: 128GB Corsair Vengeance DDR5-5600 CL-40. GPU: 24GB Asus TUF Gaming OC GeForce RTX 4090. Monitor: LG UltraGear+ 45" curved OLED. Power Supply: Corsair 1500 Watt 80+ Platinum ATX. HD: 2TB Sabrent Rocket NVME SSD. Windows 11 Pro. Flight Sim Hardware: Joystick: Thrustmaster T16000M. Rudder Pedals: Thrustmaster TPR Pendular Pedals. Yoke: Honeycomb Alpha. Throttles: Honeycomb Bravo. Controller: XBox Controller
October 24, 20214 yr Commercial Member 16 hours ago, DMullert said: Simconnect Failed to CallDispatch. That Exception is usually thrown by a SimConnet client, not the simulator program itself. Can you share a screeshot of what the error message looks like? In this case it could be the CRJ, or any other additional program that is running as a WASM module or connecting to the sim from the outside. The CRJ has a fairly large WASM module that no doubt uses SimConnect, but - the whole point about going WASM was that a failing module would not bring down the entire simulator. Same for an external process, if SimConnect fails, normally only the client program would crash, not the sim. Unless you have a massive case of SimConnect flooding, or something is calling an invalid procedure that is crashing the sim. In that case the error message is just a by-product, not the actual cause (="somehting" crashes the sim, which is why SimConnect suddenly fails, which prompts the error message by an otherwise not involved process or module). Edited October 24, 20214 yr by Lorby_SI LORBY-SI
Archived
This topic is now archived and is closed to further replies.