I also have the T.16000M setup and I've had that happen before. I think a PC re-boot fixed it. If that doesn't work, have you recently plugged your controllers into a different USB port? If so, try to plug them back into the original USB ports.
I also have the T.16000M setup and I've had that happen before. I think a PC re-boot fixed it. If that doesn't work, have you recently plugged your controllers into a different USB port? If so, try to plug them back into the original USB ports.
I did previously try a reboot, and it made no difference. I'm certain the usb port didn't change, but I tried a few others anyway, and no difference. I plugged in my old Logitech Attack 3 to try, Windows found it fine, but still Aerofly didn't. Not sure if it would or not, but it definitely used to work no problem with my T.16000M
When was the last time it worked? They made an update about a week ago that erased the joystick config so everyone had to re-map their joystick controls.
Someone else posted a similar problem with CH controllers - may want to try 1) disconnect controllers, 2) cold reboot, 3) reconnect controllers, 4) start Aerofly, 5) cross fingers ...
I did not have to re-install Aerofly the last time my controllers didn't show up. I think I just did the disconnect, cold boot, reconnect.
Or this might be helpful ...
I've noticed a situation where my Logitech Extreme 3D Pro is detected about 75% of the time. The other 25% I need to unplug and replug before it is detected. Some sort of race condition on startup??
Stu
If you are using Windows 10 a recent update changed how USB devices are connected. This may cause problems with Aerofly seeing a controller. W10 now uses priorities for USB devices so your controller may lose priority before Aerofly runs.
The only fix right now would be to unplug and replug your controller prior to running Aerofly.
Or this might be helpful ...
This fixed the issue for me.
In Steam controller settings, "Generic Gamepad Configuration Support" must be unchecked. In the same menu, my T.16000M is shown there either way as a detected controller, but the Generic controller option must be unchecked. Looks like an Aerofly bug.
Hi..i would like to understand your problem in detail, are you saying they don't respond in the settings menu or in the aircraft itself? As per my knowledge you need to assign settings to the axis to tell XP what action you want that controller movement to effect. If these were previously set, the configuration may have gotten corrupt and you need to reselect the appropriate input/output mapping.
