steering wheel bindings issue

Hi, I am trying to get a genius speed wheel 5 to bind but no joy
version 0.4.3.0.1413
win 8.1 Pro

BeamNG controls menu recognises it as a device:


but bindings menu shows only the keyboard bindings:


when I click on one of those ("steer", "steer left", "steer right", "brake", "throttle", or "throttle & brake") and move the steering wheel or depress the accelerator/brake pedals then BeamNG recognises my input as "last detected" but doesn't do anything. Then when I move the mouse to click on apply it takes the mouse movement as the correct input for that binding. The result is that my mouse now controls my steering but my steering wheel does nothing...

What am I missing?

 

update: I re-installed the driver for the wheel. When I try to bind the wheel inputs to a function it shows a blank icon next to "assigned control" in the binding screen, it doesn't do anything when I click apply. I'm pretty confused at this point.

 

Yeah, the same issue for my controller, it shows blank and does nothing when i click apply, any fix?

 

+1 here with a Logitech Driving Force Pro. The button/axis is registered but not stored...

Edit: The problem was solved by downloading the Logitech Gaming Software. That also magically got my Force Feedback working. I thought the Windoze drivers were good enough, but I was clearly mistaken!

+H+

 

Hi,

I have a solution to your problem.

----------
But first, if you care to read, here is why the issue you have exists...

If you notice in the hardware page, your mouse has a range between the left and right ranges on the xaxis. You will also notice that you have to move your mouse pretty far in either direction to reach to max of the ranges; this is very different from other controls, like a key on your keyboard which instant goes to the max range when pressed. (A reason I hate using the keyboard for driving, unless I'm Saudi Drifting... )

When you press a button on the binds pages after selecting an action, say "Steering", the detection waits for a "100% range" to move to the confirmation page for the binding. So when you just move your mouse a little to find the X or Y axis, you aren't actually "100% pressing" the mouse axis. It detects it, but wont bind it. When you press a key however, its either on or off, so its either 100% pressed or 0%, making detection instant.
----------

Move your mouse all the way to the left or right until it detects; you need to be at the Max or Min ranges of your mouse input for the detection to work.

Best,

Peter