Jump to content
The simFlight Network Forums

X56 Z axis is not detected in FSUIPC7


Stevan
 Share

Recommended Posts

Hi Pete,

I'm having a an issues with MSFS2020 steering tiler not working with the grip twist (z axis). The Windows game controller shows that the twist is responding when It turn the left or right of the stick. So I know the that windows is is receiving the output. But it seems that FSUIPC is not detecting the output. When I scan for the axis movement in FSUIPC, it does not detect the turn of the stick.

Turn to the right

image.png.db1d5837c8616ec58548ca9ce0a7c138.png

Turn to the left

image.png.176b133dfb6cc317cc4db6e5ad4424ff.png

Does not detect the turns of the stick

image.png.08b215ad84434ef0b9fff7df6576ca3d.png

Have you seen this issue before?

 

Steve

 

FSUIPC7.ini

Link to comment
Share on other sites

28 minutes ago, jaxx said:

Do you have MSFS running and a flight loaded? If I remember correctly you can only assign new axis when you're in a flight.

You can assign without MSFS running, although better to have it running (I think a warning is displayed if not running). Its the calibration thats a problem without MSFS running, but this should also be ok if assigned 'Direct to FSUIPC Calibration'. But we always recommend doing this with the FS running.

@Stevan Could you unplug your device, reboot your PC, reconnect and try again. If you get the same issue, please attach your JoyScan.csv file, as well as you ini and log files, all located in your FSUIPC installation folder.

Thanks,

John

Link to comment
Share on other sites

Hi guys,

Thanks for the quick reply.

I have tried to set the axis while in MSFS 202 and while out too. The axis is not saved in MSFS 2020 setup. Its seems the issue is communication between Windows 10 OSFSUIPC7.ini and FSUIPC7.

 

I've also did the following:

Clear calibration device settings for the X-56 when that was completed I unplugged the stick

Reboot the PC

Plugin the stick. This cleared out old configuration setting and eliminated some axis drift. But the issue was not fixed.

HidScanner.log FSUIPC7.JoyScan.csv FSUIPC7.log

Link to comment
Share on other sites

2 hours ago, Stevan said:

Did the logs reveal anything?

Yes. They reveal a few things. First, you have some registry issues with you X-56 Rhino Stick:

Quote

  1704421    WARNING: Joystick ID 2 is duplicated in Registry
  1704421    WARNING: Joystick ID 2 is duplicated in Registry

This may nor be an issue, but if you are having issues best to resolve that to take it out of the equation....more on that later.

You scanner and joyscan logs show that the stick has no axis: you scanner log shows:

Quote

 

  Value 0x20 at index 0, range 0 -> 255, using 8 bits

 

which is strange - one axis with a hex value - not sure why this is, but should show the axis letters if found, e.g. for your rudder:

Quote

  Value Z at index 0, range 0 -> 1023, using 16 bits
  Value Y at index 1, range 0 -> 1023, using 16 bits
  Value X at index 2, range 0 -> 1023, using 16 bits
  Value 0x20 at index 3, range 0 -> 1023, using 8 bits

Are you running additional software for the X56? If so, please remove that and try again. Also, if you have installed any saitek drivers, uninstall those and let windows install the default drivers, and try again.

I have just noticed the images in your original post - those are not from the windows game controller panel (or not that I recognise). Please try to see if your axis is recognised by the windows game controller application. If those images are from some sort of saitek config program, you need to remove that.

Link to comment
Share on other sites

8 hours ago, Stevan said:

I still have the duplicated in Registry errors. How do I eliminate them?

You can do that using regedit. However, if they are not causing issues, you can leave them. As you are using JoyLetters, the correct entries should be used.
If you still want to remove them, then make sure you back up the registry first (you can do this from regedit). Then, disconnect the two devices that have duplicate entries, then delete all registry entries with matching product and vendor ids for thos devices, reboot and then re-connect you devices.
If you still want to do this, if you show me your latest JoyScan.csv file I can provide you with a regedit file that you can use to remove the entries.

Link to comment
Share on other sites

Ok. Then
  - disconnect your X56 throttle and stick
  - remove any additional saitek drivers and software if you have any installed
  - reboot (leavung devices disconnected)
  - start regedit, and make a back-up of your registry
  - create a ,reg file (e.g. removeDevs.reg) with the following content:

Quote

Windows Registry Editor Version 5.00

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_A221]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_A221]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0738&PID_2221]

[-HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0738&PID_2221]

   - run the regedit file (i.e. double click it in windows explorer)
   - connect your devices and r-install anything you removed in the second step above
    - start MSFS/FSUIPC7

This may change the device letters, so once you've done that, show me your FSUIPC7.log and FSUIPC.ini files again.

Link to comment
Share on other sites

14 hours ago, Stevan said:

Follow your steps, but it looks like that (duplicated in Registry)

Hmm. Strange, Did you install any additional drivers or software after running the regedit file?
Either the regedit entries weren't removed correctly, or additional software/drivers you are installing is creating additional registry entries.

 If its the latter, you can do the procedure again but this time to do not install any additional drivers or software - just try with the windows drivers. I should have advised this first, sorry. If its the former, there may be an issue with the file you created, you should check the registry to see if those entries have been removed, and if not you can manually remove them.

Have you manually changed your ini? And added new assignments? You shouldn't really have touched it. Your C device is now missing, has been replaced by D, and you have new assignments to it. You can correct by changing your [JoyNames] section to the following:

Quote

[JoyNames]
AutoAssignLetters=Yes
0=X56 H.O.T.A.S. Throttle
0.GUID={7CCBF530-0A68-11EB-800C-444553540000}
1=T-Rudder
1.GUID={7CCBF530-0A68-11EB-800E-444553540000}
2=X56 H.O.T.A.S. Stick
2.GUID={7CCBF530-0A68-11EB-800B-444553540000}
A=X56 H.O.T.A.S. Throttle
A.GUID={7CCBF530-0A68-11EB-800C-444553540000}
B=T-Rudder
B.GUID={7CCBF530-0A68-11EB-800E-444553540000}
C=X56 H.O.T.A.S. Stick
C.GUID={7CCBF530-0A68-11EB-800B-444553540000}
 

You can also delete this entry under [Axis]:
    6=DR,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
Or maybe replace it with this:
    6=CU,256,F,66818,0,0,0    -{ TO SIM: STEERING_SET }-

(which was your previous assignment to that axis).

And the delta in your steering tiller assignment seems very large...to correct this, change your SteeringTiller assignemnt:
    5=CR,16383,D,36,0,0,0    -{ DIRECT: SteeringTiller }-
to
    5=CR,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-

John

Link to comment
Share on other sites

I reinstalled the device drivers after running removeDevs.reg and rebooting the system. The x56 will not be recognized with installing the software and drivers. I will play around with this until I get it right. Thanks far getting me this far.

Link to comment
Share on other sites

Ok I found the issue was the reg entries that were to be delete were not being deleted. So I removed them out that fix the duplicate message.  In my .ini file under joystick I'm getting "missing joystick" message but everything else is ok. I image its one of my reg entries for joystick but I can't tell which one it is.

[JoyNames]
AutoAssignLetters=Yes
0=X56 H.O.T.A.S. Throttle
0.GUID={0F856C10-889C-11EB-8001-444553540000}
1=T-Rudder
1.GUID={7CCBF530-0A68-11EB-800E-444553540000}
2=X56 H.O.T.A.S. Stick
2.GUID={0F856C10-889C-11EB-8003-444553540000}
A=X56 H.O.T.A.S. Throttle
A.GUID={0F856C10-889C-11EB-8001-444553540000}
B=T-Rudder
B.GUID={7CCBF530-0A68-11EB-800E-444553540000}
C=X56 H.O.T.A.S. Stick
C.GUID={0F856C10-889C-11EB-8003-444553540000}
D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>

image.thumb.png.3acacf75e4016b6fd96ae153cb803904.png

 

 

 

********* FSUIPC7, Version 7.0.6 (10th March 2021) by John Dowson *********
Checking for FS path in 'C:\Users\steva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\UserCfg.opt'
FS path found = E:\Games\Microsoft Flight Simulator 2020\
WebSocket server found: E:\Games\Microsoft Flight Simulator 2020\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "E:\Games\Microsoft Flight Simulator 2020\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
       79 System time = 19/03/2021 10:15:43
       79 FLT path = "C:\Users\steva\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\"
      110 -------------------------------------------------------------------
      125 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      157 FS path = "E:\Games\Microsoft Flight Simulator 2020\"
      157 ---------------------- Joystick Device Scan -----------------------
      157 Product= T-Rudder
      157    Manufacturer= Thrustmaster
      157    Vendor=044F, Product=B679 (Version 1.16)
      204    GUIDs returned for product: VID_044F&PID_B679:
      204       GUID= {7CCBF530-0A68-11EB-800E-444553540000}
      204       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X1023,Y1023,Z1023
      219 Product= Saitek Pro Flight X-56 Rhino Throttle
      219    Manufacturer= Mad Catz
      219    Serial Number= k0003507
      219    Vendor=0738, Product=A221 (Version 1.0)
      219    GUIDs returned for product: VID_0738&PID_A221:
      219       GUID= {0F856C10-889C-11EB-8001-444553540000}
      219       Details: Btns=36, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X1023,Y1023,Z255
      219 Product= Saitek Pro Flight X-56 Rhino Stick
      219    Manufacturer= Mad Catz
      219    Serial Number= k0023297
      219    Vendor=0738, Product=2221 (Version 1.0)
      219    GUIDs returned for product: VID_0738&PID_2221:
      219       GUID= {0F856C10-889C-11EB-8003-444553540000}
      219       Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U255,V255,X65535,Y65535,Z0
      219 -------------------------------------------------------------------
      219 Device acquired for use:
      219    Joystick ID = 1 (Registry okay)
      219    1=T-Rudder
      219    1.GUID={7CCBF530-0A68-11EB-800E-444553540000}
      219 Device acquired for use:
      219    Joystick ID = 0 (Registry okay)
      219    0=X56 H.O.T.A.S. Throttle
      219    0.GUID={0F856C10-889C-11EB-8001-444553540000}
      219 Device acquired for use:
      219    Joystick ID = 2 (Registry okay)
      219    2=X56 H.O.T.A.S. Stick
      219    2.GUID={0F856C10-889C-11EB-8003-444553540000}
      219 -------------------------------------------------------------------
      282 LogOptions=00000000 00000001

 

Link to comment
Share on other sites

1 hour ago, Stevan said:

I'm getting "missing joystick" message but everything else is ok. I image its one of my reg entries for joystick but I can't tell which one it is.

[JoyNames]
AutoAssignLetters=Yes
0=X56 H.O.T.A.S. Throttle
0.GUID={0F856C10-889C-11EB-8001-444553540000}
1=T-Rudder
1.GUID={7CCBF530-0A68-11EB-800E-444553540000}
2=X56 H.O.T.A.S. Stick
2.GUID={0F856C10-889C-11EB-8003-444553540000}
A=X56 H.O.T.A.S. Throttle
A.GUID={0F856C10-889C-11EB-8001-444553540000}
B=T-Rudder
B.GUID={7CCBF530-0A68-11EB-800E-444553540000}
C=X56 H.O.T.A.S. Stick
C.GUID={0F856C10-889C-11EB-8003-444553540000}
D=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>

You didn't attach your inis, but did you delete this one as recommended:

6 hours ago, John Dowson said:

You can also delete this entry under [Axis]:
    6=DR,256,D,36,0,0,0    -{ DIRECT: SteeringTiller }-

Also, search for any other assignments to your 'D' device and remove them, and then you should be ok.

John

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.