I have a bluetooth gaming mouse and when it is not moved it goes into a power saving mode. When the mouse is moved again, the flight simulator stops for a while. Then nothing can be done. The program continues after a short waiting period. If I connect the same mouse via the 2.4 Ghz USB adapter, this problem does not arise. Kind regards, S. Sultainski
For some users it helped to disable these bt energy options in windows hardware settings. There is a thread in this forum you could search. It finally did not help me so I changed back to a cable connected mouse and keyboard.
This seems a common theme with BT peripherals (although my audio is OK) and I suspect it’s something that’s unlikely to be fixed in the short term. In the meantime either turn off energy saving or use a different mouse.
Found the thread for you: MSFS Long random freezes at all stages 1.13.16.0 - #22 by FederFlyer
This has been a problem since day one, when the sim used to crash each time any peripheral, either bluetooth or not, was (dis)connected. It took me a while to figure out why it was crashing continuously, then I realised the BT mouse losing signal for a fraction of a second was the one to blame.
Luckily it’s very mitigated right now, it freezes but doesn’t die
Personally I can’t see why any delay should cause freezes in the game itself because surely that can be coded out so that the only delay is for the mouse pointer to move or buttons to work? … there again it is a gaming mouse
I think it’s because the game is detecting the bluetooth hardware itself is “disconnected”. The thing about MSFS is that every hardware that is connected to your PC, they all have individual profiles stored in your Microsoft/Xbox Account in the cloud. So when the bluetooth is on low power mode, your hardware literally disconnected itself from the PC so that it stops sending the signal which uses battery. Only when you move them, it re-initialise itself and do a new “handshake” with the PC as if it’s a new hardware being connected.
On the MSFS side, this new connection means it needs to build and load any existing profile by checking your online account, retrieving the profile from the cloud, and assigning them to the hardware. A whole lot of overhead processes for the CPU to do, this load might be what’s causing the freezes and the occasional CTDs.
Either you turn off the power saving mode, which allows the hardware to be constantly connected to the PC at the expense of more battery usage. Or you get another wireless hardware that uses a USB dongle instead. This is because even on low power mode where the mouse disconnects itself from the USB, the USB itself is still connected to the PC, so MSFS is still detecting the Dongle itself as the mouse. So from the MSFS perspective, it’s still connected so there’s no need to do all that profile retrieval process.
I have the same behaviour each time I forgot to switch ON my Xbox controller. When it connects, MSFS freeze and I fell scared it crashed
Many thanks for the answer. Now I can at least understand why MSFS is doing this. I don’t understand what this is about … but that doesn’t matter … luckily the mouse also has the option to connect it via a USB dongle … only with the number of USB ports it is a thing … they are not infinitely available … that’s why I use the mouse over BT… so that USB ports can be used for other things … it’s not that you still have a bunch of other peripheral devices …
Ever thought of a USB hub ?