sound device switched / changed ( because e.g. over USB , but not special realted to USB )
any other USB device disconnected ( joystick, throttle , etc )
Feelt the reports with the sound-devices are a little bit less compared with first ages, but I think it is still not stable in case “somewhat is changed with the sound-device”. Handling of dynamicly switching sound-devices is not as easy as its sounds, but of course we all assume that an app not crash. I assume most players have a stable sound-device over the time and so the issue is not soooo often mentioned ( but still remember some issues where users use e.g. sound over hdmi and switching monitor off , etc. ).
Disconnecting e.g. a Joystick should of course each application can handle. But each time when I tried a redo what a user reported and disconnect wildly my joystick, throttle, etc. , the sim does at least not crash ( of course these handling with “determined new hardware dialog” is a bit , let’s say needs to be optimizated ). I start MSFS usually with all my devices connected ( its like a pre-flight-check ) and so may be I come not so often into the situation.
And yes… USB vs WIFI is a change… I think you have also two different devices within the sound-settings-dialog.
But I wanted too mention only, thats the sound-switch-issue is different as (re)connect e.g. a normal joystick/throttle/controller/ device. This are two different topics ( needs different changes in implementation ).
Thank you for clarifying. I indeed confirm that in my case switching off my headset will result in a sim CTD systematically. I do not recall it was always the case.
Mine freezes as well under the same situations - - when unplugging any USB device. It also froze after disconnecting/connecting bluetooth headset during flight. I’ve had 3 flights freeze in a row because of this.
I have a KVM switch to control mouse/keyboard between two PC’s, I also control sound with the PC that isn’t the flight sim one. I am totally unable to use two PC’s in this scenario, or I will not finish the flight and CTD.
The USB input/output has been a problem with this simulator since Alpha. How much longer should we wait to get this sorted out?
I remember somewhere a post on reddit… In special these (very) old saitek is known trouble maker and crashs nearly all games ( dcs, msfs, warthunder, etc… ) or more exact “the system”.
PS: and simple plug your controllers before you start the game… easy thing…
I’ve gotten away with it a few times. On a few occasions I have forgotten to plug in my yoke, and I’m sitting there moving it wondering what is going on. If I plug it in, and just wait, it won’t crash. But if you start trying to do anything with that device, it will cause a crash. Or if you plug in multiple devices at once it will fall over, when I found I had not enabled my USB3 hub, and when I turned it on the sim saw 10 devices appear all at one, and the sim promptly fell over in shock.
The one that doesn’t seem to work is my Tobii 5 eye tracker. It doesn’t cause the sim to crash, but it just doesn’t do head tracking. I have to close the sim down entirely if I have done that.
an intressting scenario… think that was never mentioned and not much tested
But these Saitek Cyborg Evo Force issue is so often mentioned, in so many forums from so many games over more than 15 years with the exact same pid.dll error message. Its just not a msfs issue related to that device.
I can plug what I want and when I want and MSF will not crash ( and I can fly ). The only thing what happens if I forget to open the trackir application is, that I have no head-tracking and msfs needs to restart.
This issue is far from being fixed. As soon as I hear the USB disconnect sound the sim freezes. If im lucky it will come back to normal state or it will end in a CTD without error message. As it did today during take off. Not fun when this happens after a 7-8 hour flight.
Log from todays USB ctd;
Felet uppstod i programmet med namn: FlightSimulator.exe, version 1.26.5.0, tidsstämpel 0x00000000
, felet uppstod i modulen med namn: FlightSimulator.exe, version 1.26.5.0, tidsstämpel 0x00000000
Undantagskod: 0xc0000005
Felförskjutning: 0x0000000001fa8f90
Process-ID: 0x544
Programmets starttid: 0x01d8ba122cc65d30
Sökväg till program: E:\Spel\Steam\steamapps\common\Chucky\FlightSimulator.exe
Sökväg till modul: E:\Spel\Steam\steamapps\common\Chucky\FlightSimulator.exe
Rapport-ID: ea07218c-c30c-45d1-87ea-d163f56d2963
Fullständigt namn på felaktigt paket:
Program-ID relativt till felaktigt paket:
I haven’t had a crash from this in a while, but the game still freezes for 30 seconds when unplugging/plugging in USB peripherals. This is still a big issue.
) and so may be I come not so often into the situation.
