Tool to manage several USB devices

[Zettman]

S!

 

Yeah, I broke my key mapping again by accidentally pulling out my throttle, happy remapping....

 

Since my English isn't that good and I have some problems to explain exactly what I want, I will try to describe my problem a bit more in detail.

 

I currently have 3 USB devices, a TM Warthog joystick and throttle and a MFG Crosswind rudder. I mapped all keys and axis directly in the game. If I pull out one device and plug it in again, it sometimes happens that my mapping is broken and my Joystick buttons and axis are now recognized as my throttle buttons and vice versa. This seems to be a problem with USB addresses and which device is first recognized by the PC. Removing the device in the System control panel or restarting the PC does not help in most cases. I normally end up remapping all devices again.

 

Which options, instead of remapping all keys in all 3 games (BoS, DCS, WT) again every time, are there? Is there a tool too make one USB device out of three (hardware or software)? My soldering skills are low, but I managed to solder a three-point IR LED cap for head tracking.

 

Making a profile in Target GUI (TM software) will only help me to map my joystick and throttle, there is no option to add the rudder, right?

 

VKB offers this nice throttle box (currently not for EU), to combine their rudder and Joystick to, so I guess, avoid these problems, would they work with other devices too?

 

Zettman

[==LD==Lemsko]

http://vjoystick.sourceforge.net/site/

 

this is a program which maps all different input devices you want into 1 giant virtual joystick, that should definitely help.

[Zettman]

http://vjoystick.sourceforge.net/site/

 

this is a program which maps all different input devices you want into 1 giant virtual joystick, that should definitely help.

 

S!

 

Thank you very much. This sounds promising. I will try it out this afternoon.

 

Zettman

[==LD==Lemsko]

anytime o7

[Zettman]

S!

 

How exactly do I assign a physical key on m joystick/throttle to the virtual joystick? I only managed to configure my virtual joystick and change the number of buttons and axis it has. Do I need another tool to map the physical keys and axis of my devices to the virtual one?

 

I tried UJR v6.5 (ADHD v3.2.1) so far. I can select the virtual Joystick I created with the vJoy Configurator so far, but I can't figure out how to assign the physical axis to it.

 

Edit: Okay, figured out, that UJR v6.5 only lets me assign 32 keys to my vJoy with 48 keys. But I could map the Warthog throttle keys with it. No luck with my Warthog Joystick keys and all of my axis so far.

 

Zettman

Edited December 9, 2014 by Zettman

[==LD==Lemsko]

for me it worked, i use my x52 pro together with a second x52 throttle and it works for me.

 

limitations are 8 axis 32buttons for every virtual joystick you create.

 

it might also help to tell windows not to delay background loading at the startup if the order of recognized usb devices changes from time to time.

[Zettman]

 

limitations are 8 axis 32buttons for every virtual joystick you create.

 

 

S!

 

The latest version of vJoy finally supports 128 buttons with 8 axis and 4 POV Hat Switch. So I theory would be able to map my Warthog Joystick (2 axis and about 30 buttons), Warthog Throttle (3 axis and about 30 buttons) and my MFG Crosswinds (3 axis) as one device.

 

But I fail as I don't know how to asigne physical axis and buttons to the virtual device I created. Tools like UJR can only assign 8 axis and 32 buttons to the virtual Joystick, even if it has more buttons. Has anyone a code example, cause I have no clue which file I will have to change and which lines I have to add. And the short examples on the vJoy site don't help me with my problem.

 

Zettman

[CaK_Rumcajs]

S!

 

The latest version of vJoy finally supports 128 buttons with 8 axis and 4 POV Hat Switch. So I theory would be able to map my Warthog Joystick (2 axis and about 30 buttons), Warthog Throttle (3 axis and about 30 buttons) and my MFG Crosswinds (3 axis) as one device.

 

But I fail as I don't know how to asigne physical axis and buttons to the virtual device I created. Tools like UJR can only assign 8 axis and 32 buttons to the virtual Joystick, even if it has more buttons. Has anyone a code example, cause I have no clue which file I will have to change and which lines I have to add. And the short examples on the vJoy site don't help me with my problem.

 

Zettman

I have created a mapping software based on vJoy. It's impossible to distribute it freely because it contains support for different kinds of automation of Cliffs of Dover planes. But i can give you some hints. To create a mapping software you need to be able to read state of your physical devices first. If you are well versed in DirectX programming it'll be easy. If not you may find it easier to use the help of SlimDX library. SlimDX is a nice tool tho still not exactly friendly to be used so some facade on top of it comes handy. Then, when you can read state of your devices and detect button clicks you'll need a loop repeatingly polling the state and computing state of your virtual mapped device. To compute state of your virtual device you'll need some mapping configuration. I've implemented this as a XML config file with all possible mappings. It should be able to map buttons and axes at least. You may even include some transformations (trim maybe or S curves) and even more sophisticated functions. And of course you'll need to be able to apply the computed state to your vJoy device. You can find examples how to do this in vJoy instalation. There are code examples that are easy to follow included. Last but not least you'll have to find a way to assign mapped buttons and axes in the game controls setup. Mind you'll have your physical devices and your virtual mapped device running simultaneously it'll be impossible for the game to distinguish which click it shall detect to be assigned. I've done this in a way that the mapping sw is able to generate clicks on a chosen button or movement on a chosen axis besides mapping. It may take 1 or 2 days of programming if you aim to make sw for your use only. It may be ready even faster with a very pragmatic approach.