Controllers link to FSUIPC is lost temporarily

[bojote]

Hi Pete,

It's actually not a big problem, but I'm puzzled as to what might be causing this, let me describe it very briefly:

After a long flight it seems that 'some' of my USB controllers assignments become 'unresponsive' in FSX, yet.. if I pause FSX and open the control panel device panel I do see the controller there and it will work if you move the axis and use the buttons, so, fact #1: The controller IS connected and working and not in a sleep state.

The easy way to 'fix' this little annoyance is to simply go into the FSX top menu, select the FSUIPC option and when the FSUIPC dialog opens up I simply press 'OK' to return back to FSX, that does it. So, it seems that FSUIPC is doing some 'refreshing' that make the controllers work again. Any idea what this is or what can I do to prevent this from happening?

Now, the above is not really a problem unless it happens on final, I'm just wondering if you might know why this happens even when my computer is still seeing the USB devices operating normally outside of FSX.

All of my controllers AXIS assignments are configured exclusively for use with FSUIPC (in direct mode) and are 'disabled' in the native FSX axis assignment screen, meaning that if I were to 'remove' FSUIPC I could not use any controller AXIS in FSX. So i'm pretty sure this is an FSUIPC issue.

Probably if I re-enable native controller assignments in the FSX configuration screen it will fix things, but what I'm experiencing should not be happening, thats why I believe it to be some kind of glitch under my very specific configuration/scenario.

EDIT: The above information is related to AXIS assiggments and mouse macros ONLY! regular buttons in my controllers that are mapped natively inside FSX DO work perfectly fine.

Thanks Pete!

[Pete Dowson]

After a long flight it seems that 'some' of my USB controllers assignments become 'unresponsive' in FSX, yet.. if I pause FSX and open the control panel device panel I do see the controller there and it will work if you move the axis and use the buttons, so, fact #1: The controller IS connected and working and not in a sleep state.

Usually this is down to Windows' operating its power-saving management on the USB hubs in the PC. I've never heard of it happening once you switch all that off.

The easy way to 'fix' this little annoyance is to simply go into the FSX top menu, select the FSUIPC option and when the FSUIPC dialog opens up I simply press 'OK' to return back to FSX, that does it. So, it seems that FSUIPC is doing some 'refreshing' that make the controllers work again.

It's simply re-scanning the complete range of joystick possibilities to see if any have been connected or disconnected. I expect this makes Windows wake each up to get its config details.

Any idea what this is or what can I do to prevent this from happening?

Go into the Windows' device manage (Control Panel - System - Device Manager), and for all the entries listed as USB hubs of one sort or another, select them, right-click, select 'properties' and, in the power management tab, uncheck the place that allows Windows to turn it off.

Now, the above is not really a problem unless it happens on final, I'm just wondering if you might know why this happens even when my computer is still seeing the USB devices operating normally outside of FSX.

If they are in regular use Windows won't put them to sleep. If they are left for a while the power management kicks in and appears not to revert until something reconnects.

Regards

Pete