As per title, first on the FBW A380 on short final at OMDB a couple of days ago, and this morning again at VHHH just before taking off, both the PFC yoke and the pedals became inop (they were operating normally when I went through the preflight checklist).

I checked first on the MSFS Controls page and could see that both were correctly identified by MSFS, and using the Sensitivities page, both moved as they should. I also checked my Windows 11 Settings, and again both devices were correctly connected and identified... but none of the two were moving my airplane controls anymore.

I reloaded another aircraft, same results.

After restarting MSFS I was greeted with a question as to which settings I wanted to select: those of 08.00 or those of 08.12, I selected the former and same results. This is not a systematic issue (I made several flight in between the two occurrences, but this is the very first time I have such a problem in three years using MSFS.

Is this the classical "MSFS lost my settings" issue or something else? I moved all my axis to FSUIPC to avoid future issues.

Edited November 15, 20241 yr by Bernard Ducret

Yeah having similar issues. my throttles randomly don’t work on the pmdg 777 anymore. This game I swear…

Edited November 15, 20241 yr by UAL4life

Just an idea to check: Maybe there's another controller or another axis assigned to the same functions (roll / pitch / yaw)?

As long as the other controller is continually sending the same values, your intended controllers would function normally -- but if the other controller at some point starts becoming "jittery" (due to electronic noise), it would continually be overriding the values sent by your intended controllers.

I've seen the same issue periodically with PMDG 737 - Control response appears to be okay in MSFS controller menu, but no reaction in the aircraft. It rarely happens, but there seems no way to predict it or avoid it.

Just a shot in the dark suggestion, but it might be worth checking that the computer is not putting the USB ports the controllers are using to sleep.  Check your USB devices in the Win Device Manager, and make sure the option "Allow the computer to turn off this device to save power" is not checked. For some strange reason, it seems sometimes this option gets randomly turned on by the system.

Al

Edited November 15, 20241 yr by ark

22 hours ago, martinboehme said:

Maybe there's another controller or another axis assigned to the same functions (roll / pitch / yaw)?

Thank you, but no that is not the case.

7 hours ago, ark said:

it might be worth checking that the computer is not putting the USB ports the controllers are using to sleep.

Thank you, unfortunately not this either, all USB connections (I have quite a lot of them) are green in Windows 11 settings and MSFS control settings does show that the devices are recognised by MSFS (they are shown on the device list and properly identified as PFC yoke and PFC Rudder pedals), and active since I can see them moving correctly in the sensitivities. However that is not translated by any move in the sim itself, both yoke and rudder pedals are dead.

To simplify I deleted my MSFS control settings and moved yoke and rudder pedals to FSUIPC for all my planes, eliminating at least these from the list of potential future issues, however FSUIPC does not work well with the throttles of some planes like FBW A380, A320 and a few others. So I will only keep the throttles on MSFS settings and move everything else to FSUIPC that I had been using for my GoFlight modules (like AP, Gear, Radios. lights, trim, Track IR and so on). 

One thing which can cause this problem is keyboard input on an EFB (or something similar. It also happens with keyboard input on the WT G1000NXi). I've had it happen with the EFB in the FBW A32NX. If I use the keyboard to input data on the EFB, the EFB is programmed to block normal key assignments from triggering sim events while typing. But for whatever reason, ALL inputs are blocked during that time, including throttle and yoke controller inputs.