These are the Support Forums for FSUIPC and related products.

These forums replace the old support forums which have been running for 20+ years. The old forums contain a wealth of information on all FSUIPC products, but are now no longer available.

Please note that you will need to Register and Login to post for support, and also to download attachments. You can view these forums without registering.

Support is also available via Discord. Please use the following invite link to join the FSUIPC Discord server:
https://discord.gg/zjwUTrxmmE

Buttons Greater tha...
 
Notifications
Clear all

[Solved] Buttons Greater than 32 not Recognized

Posts: 242
Moderator
(@fsuipc-support)
Joined: 7 months ago

FSUIPC will only detect joystick-type HID devices. If your device is not detected/acquired, it is either a non-joystick type HID device, or you have registry issues. Check your FSUIPC7.JoyScan.csv file which will list all devices detected, registry entries for those devices, and also lists which devices are acquired or not. The HidScanner program will detect all of your HiID devices.

For non-joystick type HID devices, you can use a lua script to convert the button presses/releases to virtual button press/releases, and it can also handle axes. There is a demo lua scrip provided for this, called HidDemo.lua, which is in the Example Lua packages zip file (in your FSUIPC7 documents folder). Copy this lua script to your FSUIPC7 installation folder (or lua folder if you have set LuaPath), edit it to specify your devices VID and PID, and add make sure it is running (e.g. add it to the [Auto] section of your FSUIPC7.ini - see the documentation on how to auto-start luas if you don't know what this is).


Reply
Posts: 5
Registered
Topic starter
(@zap737)
Joined: 5 days ago

Thanks I got it working via HidDemo.lua but would like to get it working natively.

If it is indeed a registry issue, how would I go about fixing the registry ?

The device does not appear in FSUIPC7.JoyScan.csv


Reply
Posts: 242
Moderator
(@fsuipc-support)
Joined: 7 months ago

Posted by: @zap737

If it is indeed a registry issue, how would I go about fixing the registry ?

It is not a registry issue. It is due to the class of your HID device - as I said, FSUIPC only recognises device of type joystick (aka game controller) natively. I have no idea what determines the class of a USB device - I am no USB expert! But I do not think that this is possible to change via the registry - it is what the device reports and so I don't think this can be changed.

Maybe a correct driver for your device would make this visible as a game controller / joystick? What driver are you using? If using a dedicated driver, you could try removing (and deleting) this and let windows install a default driver to see if that makes a difference. Alternatively, if using a windows default driver, try with a dedicated driver if provided by the device manufacturer. 

Does the windows Game Controllers app see your device? I suspect not... If its not recognised as a game controller, it won't be recognized (natively) by FSUIPC.


Reply
Posts: 5
Registered
Topic starter
(@zap737)
Joined: 5 days ago

Does the windows Game Controllers app see your device?   No it does not.

There is no dedicated driver for the device.  Just plug and play.

I will try to contact the vendor and see if there is a firmware flash fix available.


Reply
Page 2 / 2