I might be able to fix it myself but it is not worth the time for now, as I said, as long as I don’t touch the cable during flight it does not disconnect, it is only when moving the quadrant around or when touching the cable that it does.
Yes I know but just remember that Zendesk can’t fix faulty hardware 
That is not the point here, disconnecting any device causes a crash, I just noticed because this TCA does it more often, but you can crash the game by disconnecting and connecting any device.
That is an issue that has to be fixed by Zendesk.
1 Like
Is your hardware plug and play?
Change in peripheral status inflight = CTD.
A powered hub will not solve the issue other than help make management easier. But what it will do is ensure your peripherals are getting enough juice. Honeycomb are even launching their own powered hub to address the needs of flight simmers.
I run the saitek panels and I found that even with then running through a powered hub, voltage fluctuations were causing CTDs. I resolved this by using SPAD.next drivers instead of the Logitech plugin as amongst other things it will change the power settings for the usb port/device. You can also do this through Device Management in Windows manually without needing to buy SPAD.
Thank you for this advice.
Maybe you would like to explain in some detail, how this is done ?
Does wiggling the cable etc cause any other programs, games etc to crash or hang?
I don’t think they fixed that issue. I have KVM switch and anytime I go back and forth between two computers, it crashes. Another annoyance is the total loss of control whenever focus is lost on the MSFS. I.e. move a mouse away from the sim window to a second monitor yoke, pedals throttle quadrants stop working. I don’t think it’s caused by not enough power on USB since hubs are powered and getting enough juice. I think it has something to do with the old legacy FS code still lurking somewhere. My P3D goes a little weird on KVM switch by flipping a random switch here and there but it never crashes and it keeps on flying whenever focus is lost on the mouse.
They fixed the bug a couple of udpates ago. If there was ANY hardware change (via USB plugin) to your system, even a piece of hardware that wasn’t being used by the sim (like a USB drive), it would CTD. I think this was fixed in either SU4 or SU5? I can’t remember which one, but it was one of the recent updates.
However, the issue is now back again. Not sure when it reappeared exactly, but it’s back for me as well. Any hardware change while the sim is running results in CTD, even if it’s something unrelated to the sim. Like @Flying2Night said above, I do my pre-MSFS walkaround / checklist now before starting up. I make sure everything is connected and running properly. I ensure my wireless mouse is charged enough and plug it in if it isn’t, because plugging it in mid-flight is a guaranteed crash. And of course, I make sure nothing gets connected / disconnected while MSFS is running. Only then will I fire up the sim.
1 Like
I’ll test this later to be sure but I don’t think I have the problem. However I don’t use any peripherals that use non Windows drivers or any external software but I suspect some that do might need an update from their makers or possibly a fix by Zendesk.
This is still an issue. I use a lot of USB KVM switch to hop between two computers and it takes about 3 minutes of freeze time for the simulator to catch on. You can see the cursor move around the screen, but none of the simulator controls (whether during flight or in the menu) are active until the three minutes passes. If you are insistent on clicking around, the sim will CTD.
They have been struggling with this since alpha/beta and actually got it right somewhere around SU2/SU3, but it’s broken again.
Xbox controller (USB connected) uses a native Windows driver.
If I turn that on / plug it in after the sim starts, there’s 2 things that will happen every time:
-
MSFS will CTD
-
On restart of the sim, I will find it overwrote and reset my Xbox controller profile (even my custom profiles) to all default Xbox controller settings.
Yup … that sounds like a bug alright
Like I said, they fixed that - at least the CTD part - a couple of updates back. Since then, the bug has returned. I don’t know which recent update caused it.
I first noticed it after the last world update. My wireless mouse died while the sim was running. Caused a CTD when it lost connection. A couple of days later, I noticed my mouse was low, so plugged it in while MSFS was running. Caused a CTD.
Then I had it happen with the Xbox controlle last week. I had a moment of the stupids. My cockpit is on a movable flight stand and just requires me connecting up power and USB to get working. By default my Xbox controller is off and I need to hit the Xbox button on it to power it on. I forgot and did so after the sim was starting, knowing that bug had been “fixed” prior (tested and confirmed it had been fixed).
Yeah, it wasn’t fixed any more. I had the crash / reset of settings as a result. I decided to try again just to test, and it did it again.
That’s why now I do my “walkaround” to make sure everything is connected and powered on before opening the sim.
I know it can be done - but I’ve not done it myself (I used SPAD to sort it), so I can’t offer a walk through. Sorry.
Having sIaid that, I believe it is when a USB device is assigned a ‘managed power’ setting by windowsand this can lead to voltage fluctuations and then CTD. By going into device manager via the control panel you can find all your connected devices and start to manually adjust them. Personally I found it easier to pay the $21 to let SPAD do it. And then you get all the amazing functions of SPAD too.
I have a wireless Xbox controller - but as it powers down after so long it always causes a CTD. Now I keep it plugged in with a USB C and always turn it on before launching the SIM. Although this then makes the SIM think I’m playing on Xbox and changes all the UI menu shortcuts… Ah there are more bugs in the UI than in a flop house mattress.
1 Like
Correct, this is still a source of CTD’s for me as well. Everything must be plugged in and powered up prior to launching, else high chance for CDT. Even my headset will do it…
In addition, if I don’t CTD, the preriferials will probably not work or be reconized.
3 Likes
There is certainly someting flakey with the USB code in MSFS.
Not only does MSFS randomly crash when some USB devices are connected when it is running, other USB devices, (such as the Thrustmaster TOP GUN FF Joystick) ALWAYS case it to CTD, even when it is already plugged in before MSFS is started.
As promised I have tested all my usb connections to see if this affects everyone generally although it’s hard to be certain as I’m using Windows 11
Thrustmaster joystick out and back in … no problem, not even a glitch
Thrustmaster pedals the same result
USB printer the same too
USB wireless mouse and keyboard (not bluetooth) unplugged, Froze the screen. Plugged back in they worked again but the screen remained frozen and esc key did nothing. However as soon as I called up task manager the sim unfroze instantly and everything worked again.
Xbox controller. plugged it in, immediately the sim paused and a box appeared asking me if I wanted to customize settings or keep default, I chose default, closed the box and unplugged the controller without a hitch.
You do NOT have a Thrustmaster “Top Gun” Force Feedback Joystick.
If you did, you would find you cannot use it.
1 Like