VKB T Rudder anyone have them working?

[Only]

Hi all

Hoping someone can help, have a set of VKB T Rudder Pedals connected via the Tiny Box and I can't get Elite to see them at all in the control config.

My Warthog works fine, I tried adding the PID and VID of the pedals to the devicemappings file and still nothing.

Can anyone help?

Running Win 8.1 and the pedals show up and work in the windows joy.cpl.

Thanks

 

[AndersNolberger]

I can not get them to work on my computer. I have a Throttle box and the pedals and Windows and other games see them but Elite wont react at all to them.
I also have the VKB Mamba and it is recognized in the settings. The Mamba has a newer firmware that I can not find on their site, perhaps that is what is needed for the T-rudders?

 

[AndersNolberger]

I searched the forums and found someone that said that Elite only supports devices with both X and Y axis.

So I started VKBDevCfg and enabled another logical axis called X that is not connected to any physical axis. And IT WORKED!

 

[Brun]

I asked on another thread whether that axis requirement bug had been fixed yet. I guess the answer is no.

I've got a set of CH pedals that were originally gameport but converted them to USB with one of Leo Bodnar's boards. No problems with them until ED, when I had to open them up and physically change the wiring before they'd work. Unfortunately putting the toe brakes on axes rather than sliders means they don't work properly in DCS World so I'd like to change them back at some point. Something along the lines of PPjoy and GlovePie would work around it but I hate having to mess about with all that crap, particularly as PPjoy means putting windows in test mode so the drivers will work.

 

[Druzil]

1651

So I started VKBDevCfg and enabled another logical axis called X that is not connected to any physical axis. And IT WORKED!

Hi, I have the same issue, but this didn't work for me.
I enabled a new logical axis Ry (enabled also Vs and Cn, like the first axis - shouldn't matter) and tried two ID's (1 and 3).
The axis appears in DXtweak, but does not react in Elite.
Did you change anything on the physical axis tab from the default values? Did you rename the axis ("HID Usage")?

Thx a lot!

 

[Druzil]

Hi,
it would be great if you can share your expereince - still not working for me. I tried a lot of variations in VKBdefCfg, with no success.

Thanks!

 

[dispat0r]

Working config for Elite

Hi,
I got the same vkb rudder here is the config thats working for me °.°
Ok I can not post links here so I will try to PM you my email or the link...

This should be loadable with VKBDevCfg please backup your config before flashing mine.
I also read somewhere that Elite has a problem with more than two joysticks but this information could be out of date.

 

[Druzil]

Great, this worked .
For anyone else who might encounter this problem - the names of the logical axes ("HID usage") need to be Y (the actual working one) and X (the new one, not bound to any actual axis), not the predefined Rx and Ry.

Now beta 3.9 can come - with CH Fighterstick, CH Throttle and VKB Rudder .

 

[FlexBravo]

It's a bit of an old thread, but FYI for anyone else... the VKB peddles now work right out of the box in ED. Literally plug and play. Wish I could say the same for the Gametrix ECS throttle