XBOX One / 360 controller not working with FSUIPC7 unless it has the focus

[Deltaflight84]

Hi, i purchase my FSUIPC for MSFS2020 and i have one problem, when i set the axis for the rudder in my xbox controller the windows of the software FSUIPC need to be active then when i switch to the windows of the SIM the commands sets does not work anymore. Only of i bring up the app of FSUIPC up works. Any advice of this? 

Thanks in advance

[John Dowson]

7 minutes ago, Deltaflight84 said:

Hi, i purchase my FSUIPC for MSFS2020 and i have one problem, when i set the axis for the rudder in my xbox controller the windows of the software FSUIPC need to be active then when i switch to the windows of the SIM the commands sets does not work anymore. Only of i bring up the app of FSUIPC up works. Any advice of this? 

Thanks in advance

This is a know issue with Xbox one and xbox 360 controllers. From the included README.txt:

Quote

Missing Functionality
=====================
The following functionality is not currently available in FSUIPC7. We may look at re-instating
some of these items at a later date, if and when such facilites are provided by the MSFS SDK:

1. Mouse Macros (and other mouse functionality, e.g “mouse look”, etc):  pending facilities to be provided
2. lVar access: pending facilities to be provided (if lVars still exist!)
3. AI Traffic management (Traffic Limiter and Zapper): pending facilities to be provided.
    Note that the offsets for AI traffic are populated.
4. Text display facilities: pending SimConnect functionality (some basic functionality may work)
5. Menu facilities: pending SimConnect functionality
6. Weather: apart from a few variables concerning ambient conditions at the aircraft, no other weather information
    is currently availablefor reading or updating
7. Assignments to Xbox One and Xbox 360 game controllers only take effect when FSUIPC7 has the window focus.
   Due to this, it is recommended to assign such controllers in MSFS.
 

This is because those controllers are not native DirectInput, but XInput devices.
I will be looking at this at some point, but I'm afraid its low priority so won't be available for quite a while. For the time being, its best to assign ion MSFS (or use the default MSFS profile) for those controllers.

John

P.S. And the title of this post is very misleading. I will update, but please give your posts a relevant title.

Edited March 20, 2021 by John Dowson
PS added

[Deltaflight84]

😵 Thanks anyway for the assistance.

If you are kind, Make it a priority i (like the most of rest of the people) don't have a budget to buy thousands of devices for the SIM.

Thanks again.

[John Dowson]

6 minutes ago, Deltaflight84 said:

Make it a priority i (like the most of rest of the people) don't have a budget to buy thousands of devices for the SIM.

Sorry, I can't at the moment. There are more important things I need to work on for the majority of FSUIPC users, such as access for up to 128 buttons (just released as a beta) amd lvar/hvar access, now part done (WASM module + API client).

Once thats done/completed, I am planning to make a survey (SurveyMonkey) for the remaining features that need to be implemented, and I will let you users decide on the priority.

John

[John Dowson]

For using the Xbox One/360 controller with FSUIPC, you could look into using this for the time being (although it looks rather complicated to set-up): https://github.com/samuelgr/Xidi. I'll take a look at this on more detail when I get a chance...and this would be an interim solution (if it works) to use before I add direct support in FSUIPC.

Edited April 26, 2021 by John Dowson
Further info added