Hi everyone, I have a quick question for the group. I’m flying the A350 in MSFS 2024 and I’m running into a specific issue. I use the Bravo Throttle Quadrant, but the USB-C cable connection is a bit loose. This causes the device to occasionally disconnect and reconnect for a split second.

Usually, this isn't a big deal, but in the A350, this brief disconnect completely resets the aircraft state. The engines shut down, the APU turns off, and various switches (like the landing lights) suddenly flip to different positions. Today, my engines cut out during short final on VATSIM, which was a huge problem.

Is this a known issue, and is there any way to prevent the aircraft state from resetting when a controller reconnects?

 

The attached image shows the aircraft state immediately after the disconnect

Hi,

I tested this with my own equipment (I don't have a Honeycomb) and I wasn't able to reproduce any failures/state changes when unplugging and re-plugging in any of my peripherals. Now that being said in most cases simulators don't like to be plugged and unplugged during operations and can result in simply nothing happening or the entire simulator crashing. I will still forward this along to the team but my strongest recommendation is to mitigate the chances of the simulator detecting a controller change/unplugging. Thank you.

 

58 minutes ago, IniJamir said:

Hi,

I tested this with my own equipment (I don't have a Honeycomb) and I wasn't able to reproduce any failures/state changes when unplugging and re-plugging in any of my peripherals. Now that being said in most cases simulators don't like to be plugged and unplugged during operations and can result in simply nothing happening or the entire simulator crashing. I will still forward this along to the team but my strongest recommendation is to mitigate the chances of the simulator detecting a controller change/unplugging. Thank you.

Thanks, I’ve done some further testing to see if this is specific to the Honeycomb hardware. It is not. I am experiencing the same issue with other hardware devices, such as my joystick and pedals.

I also noticed that the aircraft state doesn't reset when the device is disconnected, but rather the moment the hardware is plugged back in.

Update: I have removed all toggle switch assignments from my Honeycomb Bravo, and the issue is gone. It seems the A350 was indeed forcing a synchronization of all physical toggle positions upon reconnection, which caused the engines and systems to shut down. Deleting these assignments solved the problem for me.

12 hours ago, blackbird90 said:

Update: I have removed all toggle switch assignments from my Honeycomb Bravo, and the issue is gone. It seems the A350 was indeed forcing a synchronization of all physical toggle positions upon reconnection, which caused the engines and systems to shut down. Deleting these assignments solved the problem for me.

Glad you were able to get it sorted out 🙂