U-HID, what am i doing wrong?

[tony.silveira]

hey guys,

trying out my u-hid, everything seems to be fine.  except when i go into the device manager and look at the gamepad properties of the u-hid, the test tab only has 32 gamepad buttons listed and isn't showing any axes'.  i've assigned some pins to the x/y axis but nothing shows when testing.

anyone have any thoughts?

t

fyi, running win7 64bit if that means anything.

[degenatrons]

I'm pretty sure that the Windows test will only report on the first 32 buttons.  The others inputs are received but are not displayed, which kind of sucks.  Suggest you try using another test tool to verify your inputs.  I wrote a basic test tool in Python if you're struggling to find anything that works for you.

[tony.silveira]

I'm pretty sure that the Windows test will only report on the first 32 buttons.  The others inputs are received but are not displayed, which kind of sucks.  Suggest you try using another test tool to verify your inputs.  I wrote a basic test tool in Python if you're struggling to find anything that works for you.

are you sure?  from the u-hid page, analog input, they show the test screen up and running with the axes shown.  you can see it here.

http://www.u-hid.com/home/cms.php?page_id=7

i'd be happy to try your tool if you wouldn't mind sending it my way.

[tony.silveira]

has anyone else seen this issue and maybe figured out a fix?  working with andy on this but wondering if someone may have found a fix.

i updated the firmware and ran all my win7 64 bit updates so i'm fully up to date but still the same issue, buttons only and no axes' listed in the game control settings.

any thoughts?

[degenatrons]

Here's a link to my basic test tool.
https://dl.dropboxusercontent.com/u/26054088/KADE/sticktest/sticktest.zip

To use it you should extract files to a folder and run sticktest.exe program.
The program will report out the number of hats, axis and buttons on the first connected joystick it finds.
Input from the device will be echoed to the screen - or to a log file if you use the command:

sticktest.exe > output.log



Hopefully this helps to figure out your problem.