Controller issues when Sim In Focus

[nbillo]

Hi John, Pete
I've purchased and downloaded FSUIPC7 to use with MSFS2020. I have installed the program and can connect to the sim and I create a new profile. I go through the set up to add my axis which appears in the program as per the manual. However, when I make the sim window active again, the axis do not work nor do any of the mapped buttons from my controller. If I have FSUIPC window in focus/on top, the aircraft control surfaces move, yet when I click back in the sim and FSUIPC is not in focus, the controls no longer function. Am I doing something wrong? I have read through the manual and everything seems to configure correctly, but when I have the sim window active, the controls stop working. I have tried this with the sim using full screen and in windowed mode but it's the same.

I have a complete clear profile set up within MSFS so there are no conflicts anywhere. I am using an XBOX1 controller, while working away and I use my gaming laptop for my flying. I have been using FSUIPC since v3 so I am certainly no novice when it comes to the FSUIPC program.

I also use FSUIPC6 with P3Dv5, on the same machine and I have no issues with assigning and calibrating my XBOX1 controller in that. It's just with FSUIPC7. I've also tried assigning another JOY ID number using JoyID but that doesn't make any difference.

I end up having to stop using FSUIPC and re-enable the axis back in MSFS, but that is just terrible, especially for rudder control. I've attached my log files in case they shed any light on the issue.
Have you any idea as to why this is happening?

Kind Regards

Nigel Bilton

FSUIPC7.log FSUIPC7.ini

[John Dowson]

Hi Nigel,

could you  remove the contents of the [General] section from your FSUIPC7.ini. This will be rebuilt with the updated defaults the next time you run FSUIPC7.

Your  ini shows that you only have assignments to your xbox controller. Are these not working?

Your log shows no other device is recognised, i.e. your X-55 Rhino stick was not connected. If you have installed the saitek software and/or drivers, you should remove these and try again.
You should also check the power management settings on your usb hubs, to make sure windows isn't putting them to sleep.

If you are still having problems getting your stick recognised, please show me your FSUIPC7.Joyscan.csv file.

[John Dowson]

Btw you have one profile called MSFS XBOX1 CONTROLLER. It is not a good idea to name your profiles after a controller, after all they apply to ALL your controllers. It is best to name them after a specific aircraft or an aircraft type (e.g. single prop, jet, etc).

Also, for the xbox controller, I find it better to use this as set-up by default in MSFS.

[nbillo]

Hi John,

Well, I deleted the ini file and started again. I've created a new profile without any reference to the controller, although I can't see why that would make any difference. 

I have a profile loaded using the MSFS built-in system, but that is using the view commands, which I am using for my left stick only.

I have set up a profile in FSUIPC for my right stick and that is assigned to the ailerons/elevator, and the triggers are set for the rudder. These are direct to FSUIPC, which is what I normally use in P3D.

If I have the FSUIPC window open and its in focus, I can see the controls moving quite normally. If I click into the sim and FSUIPC is not in focus, the controls stop working.

I had a similar issue when using AaO from Lorbi during the beta phase of MSFS and he very kindly did some testing and told me the XBOX1 Controller uses the Xinput API, and he was using DirectInput for his program. He did some changes and managed to get the XBOX1 controller working in the sim. I guess you will be using the same for FSUIPC, and so it won't ever work for my XBOX1 Controller. Do you think that is the reason?

Kind Regards

Nigel

FSUIPC7.JoyScan.csv

[John Dowson]

1 hour ago, nbillo said:

I've created a new profile without any reference to the controller, although I can't see why that would make any difference. 

It doesn't. But naming a controller after a profile indicates that you are not familiar with profiles or how they are used. Of course, you may perfectly understand how they work, but then its a strange name to give a profile...

2 hours ago, nbillo said:

I had a similar issue when using AaO from Lorbi during the beta phase of MSFS and he very kindly did some testing and told me the XBOX1 Controller uses the Xinput API, and he was using DirectInput for his program. He did some changes and managed to get the XBOX1 controller working in the sim. I guess you will be using the same for FSUIPC, and so it won't ever work for my XBOX1 Controller. Do you think that is the reason?

Ok, then we are talking about assignments to your xbox controller. FSUIPC also uses direct input, so it may be the same issue. I have an xbox controller so I'll take a look next week sometime. xbox controllers are handled pretty well in the default MSFS assignment profile, so why don't you use this?

I thought/assumed that you were trying to set up your Saitek Pro Flight X-55 Rhino Stick, but this seems no longer connected.

 

 

[nbillo]

Hi John,

Thanks for your time.

10 hours ago, John Dowson said:

Ok, then we are talking about assignments to your xbox controller. FSUIPC also uses direct input, so it may be the same issue. I have an xbox controller so I'll take a look next week sometime. xbox controllers are handled pretty well in the default MSFS assignment profile, so why don't you use this?

I could use the MSFS built in system, but it will not allow me to utilise the rudder axis to the triggers on the Xbox1 controller for some reason. I can only assign digital yaw inputs which are just terrible and virtually uncontrollable. This is the main reason why I wanted to use FSUIPC in MSFS, apart from the fact, I've been using it for many years and I am just so used to liking the flexibility it brings.

I do use the Saitek X-55 Rhino stick and rudder combo, but that is while I am somewhere else which is usually shorter periods. Where I spend most of my working time, I don't have these items with me.

It looks like this is the same issue that I had previously and to do with the Xinput api. You mention that you have an Xbox1 controller and will test it this week. I would certainly appreciate if you would consider using both api's, I'm sure there are plenty of people who own these and use them in the other sims and would like to use them in MSFS. Because of my work and travel, I find using this controller much more easy to carry about, and I guess I have gotten quite used to using it, giving me the option to pan and view with one stick and control the aircraft with the other, is so nice.

Kind Regards

Nigel

[John Dowson]

Hi Nigel,

ok, I can see the issue. With my xbox game controller, connecting via bluetooth its reported as:

Quote

 

      391 Product= Xbox Bluetooth Gamepad
      391    Manufacturer= Microsoft Corporation
      391    Serial Number= c83f26b19496
      391    Vendor=045E, Product=02E0 (Version 0.0)
      391    GUIDs returned for product: VID_045E&PID_02E0:
      391       GUID= {A31C8E90-4851-11EA-8002-444553540000}
      391       Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535

...

      422 Device acquired for use:
      422    Joystick ID = 2 (Registry okay)
      422    2=Bluetooth XINPUT-compatible input device
      422    2.GUID={A31C8E90-4851-11EA-8002-444553540000}

whereas cabled:

Quote

      672 Product= Controller (Xbox One For Windows)
      672    Vendor=045E, Product=02FF (Version 0.0)
      672    GUIDs returned for product: VID_045E&PID_02FF:
      672       GUID= {B08472C0-274C-11EB-8001-444553540000}
      672       Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U65535,V65535,X65535,Y65535,Z65535

...

      703 Device acquired for use:
      703    Joystick ID = 2 (Registry okay)
      703    2=Controller (Xbox One For Windows)
      703    2.GUID={B08472C0-274C-11EB-8001-444553540000}

However, in both cases it suffers from the problem that FSUIPC7 only recognises inputs from this device when FSUIPC7 has the focus.

I'll look into it and get back to you, although this may take a while. I'll also talk to Oliver/Lorby.

Thanks for reporting this, regards,

John

[John Dowson]

Just checked this in P3Dv4/5 and FSUIPC5/6. Its the same problem there, but as FSUIPC5/6 is a dll rathe rthan a separate application, the controller works when P3D has the focus but not when other applications have the focus.

As I said, I will look into this but it may take a while.

 

[nbillo]

Hi John,

Thank you for your interest in this issue.

10 hours ago, John Dowson said:

Just checked this in P3Dv4/5 and FSUIPC5/6. Its the same problem there, but as FSUIPC5/6 is a dll rathe rthan a separate application, the controller works when P3D has the focus but not when other applications have the focus.

Okay, I understand now why I haven't had any problems running the controller with either P3Dv4/5

10 hours ago, John Dowson said:

As I said, I will look into this but it may take a while

Thanks for your time.

Kind Regards

Nigel

[John Dowson]

Just to close this issue, when using XINPUT devices, such as the xbox one and xbox 360 controllers, input is only recognised by FSUIPC when FSUIPC has the focus. In versions of FSUIPC before FSUIPC7, this will be when the FS has the focus (as FSUIPC is an embedded dll in the FS), but as FSUIPC7 is an external application it will only receive the controller input when it has the focus.

The only way around this is to use an additional program:  XInput Plus. This is noted in the README,txt:

Quote

XINPUT devices, such as the XBox One and XBox 360 controllers do not work natively with FSUIPC7.
If you want to use FSUIPC7 with such devices, you will need to install and configure a conversion utility called XInput Plus.
Please see the following tutorial:
    https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/
It has been reported that the UI for this utility is also now available in English.
Also note that you need to point this utility to the FSUIPC7.exe, not the MSFS.exe.

John