Fixing joystick connections not seen by FSUIPC

[Pete Dowson]

Sometimes the installation program for a joystick does not fill in all of the Registry entries, with one entry important for the way FSUIPC works omitted. This is the Windows joystick ID number, a value from 0 to 15.

This seems to be more prevalent on Windows 8 and 10, but wherever it occurs the following might help:

Download JoyIDs here http://airgroup51.ne...hp?topic=2435.0

Install the program then run it. You should see your connected joystick(s).

Double click on the problem one (should highlight green) and click on a different Id# to move it there. This will fix the entry in the Registry. You can move it back again if you wish. It won't affect anything else.

Pete

[Tom747]

Thank you very much.

Great information.

Now everything works fine again.

[Erikviktor1]

Hello Pete,

 

I have a similar problem as the one described in this forum topic.

 

My saitek yoke is not recognized in FSUIPC4 on a networked PC running widefs.

 

Symptoms;

 

NO ID nr. or joystick ID appears in FSUIPC on networked pc running with updated WIDEFS.

 

I tried creating a Joystick ID nr- with the "Joyids" software as you suggested and my device appears as "SAITEK ID nr.#1" on this software table,  but it doesn't change anything. Still no joystick or axis control in FSUIPC4 on network PC.

 

I tried the same procedure connecting the Yoke to the Server PC running FS and yes it does registrer on FSUIPC when activating the yoke axis.

 

 

On the network PC I can program button functions in the "Buttons and keys" window but no axis control,

Moving the yoke produces no signal at all nor any ID.

 

I also reviewed my FSUIPC4 and WIDEFS versions and upgraded both as they weren't up to date and rebooted the system twice but

this did not solve the problem.

 

I am running out of options on my side.

Your expert advise is required.

 

Erik

 

[Erikviktor1]

Hello,

 

I have the same problem with a SAITEK pro flight yoke installed on a networked PC running updated WIDEFS (registered).

I can asign buttons and keys on FSUIPC4 installed on server PC but no axis.

FSUIPC and WIDEFS are up to date. I had an older version but installed the latest version from Shiratti.com (version 4.954).

This did not solve the problem, nor did "Joyids" software. It did asign an ID nr. and "saw" the yoke but this did not help FSUIP in registering my yoke on the client PC.

 

I tried also to connect the yoke to the server and FSUIPC was able to register the yoke's ID and axis.

I hope this might help recognize the yoke on the client PC but no luck there.

As I am running out of ideas I think I need your help.

 

Erik

[Pete Dowson]

Please always post support questions in the Support Forum.  You are lucky I saw these posts!

 

Axes are not read nor transmitted by WideFS, only buttons and switches. This is documented. If you want to send axes from a client PC you'd need to write a Lua plug-in to do it.

 

Pete

[Erikviktor1]

Hi Pete,

 

Thanks for the quick reply-

I ignored that Widefs didn't control joystick axis inputs over a client PC. Must have missed that in the docs.  I expect that I got confused as many users use FSUIPC to overcome such glitches with their controls running directly on FS (server).

I learned something here.

 

Cheers!

 

Erik

[hydbyr]

With a similar situation, I tried to download JoyID from the site above and it was blocked by Norton. Is there a problem with the program from this site?

[Pete Dowson]

With a similar situation, I tried to download JoyID from the site above and it was blocked by Norton. Is there a problem with the program from this site?

 

No. It'll be a false positive I should think.

 

Withrecent versions of FSUIPC4 you shouldn't really need to use JoyIDs, as I've now built code into FSUIPC4 to do similar things, assign IDs where none can be found in the REgistry.

 

Pete

[Nico Weesjes]

Hello Pete,

I’m building a cockpit B737 www.ph-nic.eu

With:

Fs 2004

FSUIPC             

Interface: Leobodnar BU0836

I have some problems with my axis assignments.

5 analogue axis are placed on the following positions.

X-axis                  Aileron                no problem      

Y-axis                  Elevator             no problem

Z -axis                 Flaps                   no problem      

U-axis                  Throttle 1          no problem

R-axis                  Throttle 2          no problem

V-axis                 Spoiler               big problem!

 

I have tried to connect the spoiler but it gives no response.

On the interface I have 8 analogue connections.

Three of them do not  reacted.

 

How can I make connection so I see them in de FSUIPC window? 

 

With kind regards,

Nico Weesjes

 

 

 

[Pete Dowson]

It would really be better to post support questions to the Support Forum. They'd be seen earlier, usually.

FSUIPC3 sees any axis which can be read using the original Windows joystick API.  There are only 6 of these -- X Y Z R U V.  It sounds like what you think of  as "V" is actually one of those only supported by DirectInput, which is used in FSUIPC4.

FSUIPC4, using DirectInput instead, supports 12 axes: X Y Z R U V, plus sliders S  T,  and POVs P Q M and N.  Maybe the Bodnar board puts yuor missing 3 onto one of these latter ones. See if any of the three are recognised in the Buttons & Switches tab -- FSUIPC3 did support two POVs as sets o 8 switches.

Pete

[Nico Weesjes]

Dear Pete,

Can I use FSUIPC4 in FS2004? Or only FSUIPC3?

KR, Nico

[Pete Dowson]

Can I use FSUIPC4 in FS2004? Or only FSUIPC3?

 

FSUIPC4 is only for FSX and P3D. FSUIPC3 is for FS98, CFS1, CFS2, FS2000, FS2002 and FS2004. They are totally different internally.

 

Pete

[C2615]

Happend to have this problem with FSUIPC6 when adding an new device, and one of my old one gone, tried this trick, and confirmed it still works!

[LelandHogan]

On 9/7/2015 at 11:23 AM, Pete Dowson said:

Sometimes the installation program for a joystick does not fill in all of the Registry entries, with one entry important for the way FSUIPC works omitted. This is the Windows joystick ID number, a value from 0 to 15.

This seems to be more prevalent on Windows 8 and 10, but wherever it occurs the following might help:

Download JoyIDs here http://airgroup51.ne...hp?topic=2435.0

Install the program then run it. You should see your connected joystick(s).

Double click on the problem one (should highlight green) and click on a different Id# to move it there. This will fix the entry in the Registry. You can move it back again if you wish. It won't affect anything else.

 

To address this issue, you can follow these steps:

1. Download the JoyIDs tool
2. Install the program on your computer.
3. Run JoyIDs, and you should see a list of your connected joysticks.
4. Identify the joystick that is causing the problem (it may be highlighted in red or not showing the correct ID).
5. Double-click on the problematic joystick, which should highlight it in green.
6. Choose a different ID number for the joystick by clicking on a different ID# in the list.
7. This action will fix the entry in the Windows registry for that joystick.
8. If you want, you can move the joystick back to its original ID# afterward without affecting anything else.

Following these steps should help resolve the issue of missing or incorrect registry entries for the joystick, enabling FSUIPC to function properly.