DCS World => Warthog Autodetect?

[idenwen]

Hello alltogether.

Finally I got my Warthog HOTAS Set and plugged it in after following the setup instructions of the Software. (Installing driver, unplug, installing TARGET, reboot, replug)

 

I thought that DCS Worlds A-10C should autodetect the HOTAS set and use the correct settings.

It did.. to about 40%. CMS, DMS, TMS, ... work but trim switch and trottle was totally wrong. Throttel had its axis for pitch and roll ^^ and not one switch had ANY function (Sync also dont works)

 

Anyway to tell DCS to correctly detect my set?

Tried deleting users/saved games/config/input/A10c/joystick/* but did not help.

 

Greetings

[Madog]

Hey, you can Check the functionality of your Warthog from within target. On the top of the Software there is a button that starts another program, 'device checker' or similar ( writing this from memory). First check every button of the stick and throttle to be sure the devices are working properly. For the game to detect the devices properly be sure to NOT load a profile with target. This is because, target disconnects the both stick and throttle and connects another device called Warthog combinded, which looks to the os as though it would be only one usb input.

Dcs only automatically detects the single stick and throttle, for the Warthog combined it just uses the standard joystick profile which is very simple.

So, you will have to decide if you'd like to use target or autodetection. I personally prefer target profiling, because it enables you to use advanced programming over the ever-chaning dcs input templates.

[idenwen]

Hey, you can Check the functionality of your Warthog from within target. On the top of the Software there is a button that starts another program, 'device checker' or similar ( writing this from memory). First check every button of the stick and throttle to be sure the devices are working properly.

 

Done. All buttons and axis(axes?axe) work as expected

 

For the game to detect the devices properly be sure to NOT load a profile with target. This is because, target disconnects the both stick and throttle and connects another device called Warthog combinded, which looks to the os as though it would be only one usb input.

 

Target was not even running. Also not the script editor.

 

Dcs only automatically detects the single stick and throttle, for the Warthog combined it just uses the standard joystick profile which is very simple.

 

It only assigns the default joystick profile to the throttle and the stick.

For the stick most of the buttons where correct. Throttle was total off

 

So, you will have to decide if you'd like to use target or autodetection. I personally prefer target profiling, because it enables you to use advanced programming over the ever-chaning dcs input templates.

 

I would at least want to try fully integrated autodetected and sychronised play :cry_2:

Have made a TARGET profile for the throttle only now but... meh...

 

Maybe someone has a idea how to fix this?

[Madog]

Hmm, i have two ideas what could be wrong.

1) DCS Installation: have you checked if there are template files for both controllers within in installation directory? They should be recognizable by the filenames.

2) somehow wrongly installed devices. As far as i could figure it out, DCS seems to search for usb devices which have a specific name and applies the controller template with the same name from the install directory to thier usbid and saves the result in the user directory with the usbid appended to the filename. If somehow Windows does not use the proper device names, DCS won't recognize the devices properly.

If both ideas do not lead you to a solllution, i suggest to open up a trouble ticket on digitalcombatsimulator.com, this is often more helpful than the forums.

Good luck,

Madog

[Flagrum]

I can't remember how it was exactly with the WH when I plugged it in for the first time, but I often (always?) experience that some axes are not mapped correctly when installing a new module (i.e. Huey, Mi-8). Usually several axes are assigned to more than one device.

 

Besides that, I am pretty sure at least the buttons and switches on Stick and Throttle were assigned correctly for the A-10C back then. With one exception: the trim hat was used as view hat - but that was intentionally I think, as not everybody is to expected to have TIR.

 

... is that roughly the situation you are experiencing, OP? If so, I suggest, just clear up the axis assignments ... and you're set. At least that will get you into the air way faster than waiting for a support ticket ...

[Madog]

Hey again,

im at home now and can be a little more precise. The templatefiles i was talking about can be found under <installation directory>\Mods\aircrafts\A-10C\Input\A-10C\joystick . The installation directory is C:\Program Files\Eagle Dynamics\DCS World by default. Specifically i mean these two files:

Joystick - HOTAS Warthog.lua 101.078 Bytes

Throttle - HOTAS Warthog.lua 100.690 Bytes

 

Are they present in your installation?

 

They should be converted into configuration files in your DCS configuration directory which can be found here:

C:\Users\<your windows username>\Saved Games\DCS\Config\Input\A-10C\joystick

Mine are named

Joystick - HOTAS Warthog {513ED360-6C79-11e1-8001-444553540000}.lua

and

Throttle - HOTAS Warthog {A3979F40-6C72-11e1-8001-444553540000}.lua

But as far as i can tell, the long string within the curly braces are system specific USB ids, so they would be different for you.

 

I also have got to correct myself: these files are not generated when you start up DCS, but upon entering the control section of the options screen.

 

Also, forget the part about the device names and the filenames, i have just checked mine and the do not match, so DCS must have some other means to detect what is what :)

 

Anyway, i'll attach my two configuration files, so if you swap the device id's maybe it will just work for you. Remember, though that if the templates will get updated these will stay in thier current state.

 

Madog

Joystick - HOTAS Warthog {513ED360-6C79-11e1-8001-444553540000}.lua

Throttle - HOTAS Warthog {A3979F40-6C72-11e1-8001-444553540000}.lua

[idenwen]

Hey again,

im at home now and can be a little more precise.

Same here :) I'll check...

 

The templatefiles i was talking about can be found under <installation directory>\Mods\aircrafts\A-10C\Input\A-10C\joystick . The installation directory is C:\Program Files\Eagle Dynamics\DCS World by default. Specifically i mean these two files:

Joystick - HOTAS Warthog.lua 101.078 Bytes

Throttle - HOTAS Warthog.lua 100.690 Bytes

 

Are they present in your installation?

 

Yes they are present and have the same size.

 

 

They should be converted into configuration files in your DCS configuration directory which can be found here:

C:\Users\<your windows username>\Saved Games\DCS\Config\Input\A-10C\joystick

Mine are named

Joystick - HOTAS Warthog {513ED360-6C79-11e1-8001-444553540000}.lua

and

Throttle - HOTAS Warthog {A3979F40-6C72-11e1-8001-444553540000}.lua

They're not.

But as far as i can tell, the long string within the curly braces are system specific USB ids, so they would be different for you.

Jup, it's machine specific. But can be changed.

 

 

I also have got to correct myself: these files are not generated when you start up DCS, but upon entering the control section of the options screen.

Yes found that out yesterday also after repeatet tries and deletions of the input folder in "saved games".

 

 

Also, forget the part about the device names and the filenames, i have just checked mine and the do not match, so DCS must have some other means to detect what is what :)

Dammn. To bad. Thought it's maybe because the throttle get's recognized as "5-axis 32-button Joystick with multiwayswitch". But if it's not the name....

 

 

Anyway, i'll attach my two configuration files, so if you swap the device id's maybe it will just work for you. Remember, though that if the templates will get updated these will stay in thier current state.

 

Madog

 

Thanks for the files :)

I'll try them and see if it changes anything in regards of sychronizing.

[idenwen]

Tested and sadly still no syching with the HOTAS controls.

And some funtions where not presend in the files also (EAC ARM had a command, EAC OFF not and such things). Seems I'm stuck at making my own profile in TARGET.