Extra commands to default hotas warthog A-10c profile

[=Spooky=]

Hi all

I'm looking for the Hotas Warthog default profile for A10C.

The reason is that I would like to add some extra commands via the TARGET.

Could someone help me?

 

Thanks in advance

[sobe]

I don't think you can mix the default with target. What you can do is mix the default with Autohotkey.

[PiedDroit]

Actually you can create a TARGET profile for throttle only that will look like the throttle (without TARGET) from a DirectX point of view.

This will allow you to customize the throttle via TARGET on top of the default profile.

 

-1-

Get file _DefaultMap.tmh, this file contains a button mapping (ThrottleMap1) that will restore all default buttons for the throttle (i.e directX mapping).

You can't use it with the throttle+joystick because the directX mappings of the joystick and throttle will overlap.

 

The .tmc file is attached, this is the command that load the new mapping:

MapList(&Throttle,&ThrottleMap1); // _DefaultMap.tmh

-2-

Copy the content of \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\Throttle - HOTAS Warthog.lua

Inside file \DCS World\Mods\aircraft\A-10C\Input\A-10C\joystick\Thrustmaster Combined.lua (make a backup for it first).

 

Also backup (and delete) file \Saved Games\DCS\Config\Input\A-10C\joystick\Thrustmaster Combined {7B669F90-9A15-11e2-8002-444553540000}.diff.lua

 

---

You can test the .tmc file alone and check (with windows controller test tool) that the throttle and the throttle+TARGET have the same DirectX output.

 

Step 2 ensures that the combined and the throttle will behave the same in DCS, you can test it, start the profile in TARGET, start DCS and check that the throttle switches and axis work correctly.

 

At this point you can add your custom stuff in the TARGET script.

 

---

EDIT: You can do the same for the joystick except you shouldn't have to redefine anything, an empty profile will do as the default mappings in TARGET are those of the naked joystick.

If you want to customize for throttle and joystick at the same time, I'm afraid that won't be possible, you'll need to rebuild a full TARGET profile that remaps every keyboard command to the HOTAS buttons before anything else.

_DefaultMap.tmh.txt

ThrottleOnly.tmc.txt

Edited August 28, 2015 by PiedDroit

[Achiral]

Actually, you can use TARGET with both Joystick and Throttle while maintaining them as independent controllers (i.e., not combined into a new virtual controller). It's just not very well documented.

 

In your .tmh file, you will have a line like

if(Init(&EventHandle)) return 1;

Change that to

if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;

That second parameter being passed restricts the script from creating the virtual controller - so the joystick and throttle (and any other TM controllers for that matter) will remain separate in the device list.

 

I don't think there's any way to do this with the TARGET GUI though.

[PiedDroit]

Cool this looks like much simpler than my solution, good find :thumbup:

I'm gonna try that some day

[PiedDroit]

Actually, you can use TARGET with both Joystick and Throttle while maintaining them as independent controllers (i.e., not combined into a new virtual controller). It's just not very well documented.

 

In your .tmh file, you will have a line like

if(Init(&EventHandle)) return 1;

Change that to

if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;

That second parameter being passed restricts the script from creating the virtual controller - so the joystick and throttle (and any other TM controllers for that matter) will remain separate in the device list.

 

I don't think there's any way to do this with the TARGET GUI though.

Hi, I tried your method but it makes the joystick and throttle disappear completely from the windows controller list and the thrustmaster combined is not created either.

This way you can only emulate keystrokes, the axis are not seen at all.

What is the supposed effect of this code?

 

The code I posted above will keep the joystick and the throttle visible to DCS while allowing the user to customize the throttle output at the same time, with minimal change of configuration.

 

So, is there anything to add to achieve the same with the Init() modification? Maybe there's another code modification I don't have.

Thanks!

[Achiral]

...

So, is there anything to add to achieve the same with the Init() modification? Maybe there's another code modification I don't have.

Thanks!

 

Oops :music_whistling:

I had made a bunch of changes back and forth at one time while figuring out how it all worked, and had multiple target.tmh files that were doing different things.

 

You will also need to Configure() the devices you want to keep separate. So it will end up like:

   Configure(&Joystick, MODE_KEEPENABLED);
   Configure(&Throttle, MODE_KEEPENABLED);
   if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;

I think that should be all.

[PiedDroit]

Oops :music_whistling:

I had made a bunch of changes back and forth at one time while figuring out how it all worked, and had multiple target.tmh files that were doing different things.

 

You will also need to Configure() the devices you want to keep separate. So it will end up like:

   Configure(&Joystick, MODE_KEEPENABLED);
   Configure(&Throttle, MODE_KEEPENABLED);
   if(Init(&EventHandle, CREATE_KEYBOARD+CREATE_MOUSE)) return 1;

I think that should be all.

Oh that's sneaky :D

I'll keep you posted when I have tried it, no time today.

[PiedDroit]

Hi, I tested that today, I confirm it works :thumbup:

This opens a new world of scripting possibilities!

[xoxen]

Hi, I tested that today, I confirm it works :thumbup:

This opens a new world of scripting possibilities!

 

Could you please post how your complete files are looking now? I´m trying to do exactly the same but am new to TARGET. This would be of great help to start with.

Thanks,

Xoxen

[PiedDroit]

Could you please post how your complete files are looking now? I´m trying to do exactly the same but am new to TARGET. This would be of great help to start with.

Thanks,

Xoxen

Sorry I missed this post :cry:

I don't have a script using the CREATE_KEYBOARD+CREATE_MOUSE hack right now (I just did some throw away tests for now).

Is that what you need?

 

If you need some generic TARGET programming I can just dump one of my scripts here - or maybe it would be better to create a new thread with your requests.