Release Aussiedroid's Enhanced Thrustmaster Warthog Script

[Clicker]

Ok, so...

Aussiedroid's script was last updated prior to the new sticks and works with a pretty old version of TARGET.
I will take a look when I get a chance and see what tweaks would be needed to bring it up to date.

BTW....you should not be editing hid.tmh, defines.tmh, sys.tmh or target.tmh. Please go in and revert any/all changes you've done to these files.

Make sure you have downloaded and are using Aussiedroid's version 5.0 script and not 4.3

GitHub - Aussiedroid/AD-EDWarthogEnhancedScript at odyssey

An Advanced & Highly Customisable Elite Dangerous Thrustmaster Warthog Script + ED Bindings Pack that utilises Modifiers, allowing for all commands to be easily accessible on the HOTAS. Include...

github.com

I am also assuming you've downloaded and installed the latest version of TARGET?
T.A.R.G.E.T - Software v3.0.24.618_rev1 <-- the new base and sticks are defined within target.tmh

I'll be in touch.

Clicker

 

[Clicker]

Oh, and another thought...Aussiedroid's script was written for the WARTHOG stick.
Can I assume you have used the F16 stick with the old WARTHOG base and it worked???

Clicker

 

[rdalcroft]

Ok, so...

Aussiedroid's script was last updated prior to the new sticks and works with a pretty old version of TARGET.
I will take a look when I get a chance and see what tweaks would be needed to bring it up to date.

BTW....you should not be editing hid.tmh, defines.tmh, sys.tmh or target.tmh. Please go in and revert any/all changes you've done to these files.

Make sure you have downloaded and are using Aussiedroid's version 5.0 script and not 4.3

GitHub - Aussiedroid/AD-EDWarthogEnhancedScript at odyssey

An Advanced & Highly Customisable Elite Dangerous Thrustmaster Warthog Script + ED Bindings Pack that utilises Modifiers, allowing for all commands to be easily accessible on the HOTAS. Include...

github.com

I am also assuming you've downloaded and installed the latest version of TARGET?
T.A.R.G.E.T - Software v3.0.24.618_rev1 <-- the new base and sticks are defined within target.tmh

I'll be in touch.

Clicker

Hello

Yes I have just read that. I have deleted that line now.

Yes I have the latest Target software, and driver for the AVA base. But in that hid.tmh file it only shows:

//hardware IDs, to be used in USB device selection with SelectUsbDevice
char HWID_T16000[] = "VID_044F&PID_B10A&REV_0500";
char HWID_HOTAS[] = "VID_044F&PID_0400&REV_0110";
char HWID_WARTHOG_JOYSTICK[]= "VID_044F&PID_0402&REV_0100";
char HWID_WARTHOG_THROTTLE[]= "VID_044F&PID_0404&REV_0100";

The last 2 lines are for the Thrustmaster warthog throttle and older base/stick 0100 at the end. where as the new AVA base is: "VID_044F&PID_0415&REV_0200"

Ok no rush, I can live without it for now, I just was hoping it would be as simple as a line oif code.. lol

Thanks for taking a look.

 

[rdalcroft]

Oh, and another thought...Aussiedroid's script was written for the WARTHOG stick.
Can I assume you have used the F16 stick with the old WARTHOG base and it worked???

Clicker

Sorry to be clear, my stick is the old warthog stick. I did have the older base along with the stick. But its the actual base that have all the button configs on it, the stick is just a bunch of switches, all the programming is on the base. I do not think there is a difference between the F16 stick and the old warthog stick, they just changed the name to F16 from warthog.

 

[Clicker]

Sorry to be clear, my stick is the old warthog stick. I did have the older base along with the stick. But its the actual base that have all the button configs on it, the stick is just a bunch of switches, all the programming is on the base. I do not think there is a difference between the F16 stick and the old warthog stick, they just changed the name to F16 from warthog.

Well, that's nice and confusing!

Can you please post the output when you run the script?
In particular the following section;

Currently plugged USB HID devices[1]:
1: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
USB HID device with hardware id "VID_044F&PID_0402" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device "T-Rudder"(USB\VID_044F&PID_B679\7&39F7723&0&1) selected
USB HID device with hardware id "VID_044F&PID_B68F" cannot be found
USB HID device with hardware id "VID_044F&PID_040A" cannot be found
USB HID device with hardware id "VID_044F&PID_040B" cannot be found
USB HID device with hardware id "VID_044F&PID_0409" cannot be found
USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found
USB HID device with hardware id "VID_044F&PID_0415" cannot be found
USB HID device with hardware id "VID_044F&PID_0414" cannot be found
Virtual HID devices managed by script!

Thanks

 

[rdalcroft]

Well, that's nice and confusing!

Can you please post the output when you run the script?
In particular the following section;

Currently plugged USB HID devices[1]:
1: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
USB HID device with hardware id "VID_044F&PID_0402" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device "T-Rudder"(USB\VID_044F&PID_B679\7&39F7723&0&1) selected
USB HID device with hardware id "VID_044F&PID_B68F" cannot be found
USB HID device with hardware id "VID_044F&PID_040A" cannot be found
USB HID device with hardware id "VID_044F&PID_040B" cannot be found
USB HID device with hardware id "VID_044F&PID_0409" cannot be found
USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found
USB HID device with hardware id "VID_044F&PID_0415" cannot be found
USB HID device with hardware id "VID_044F&PID_0414" cannot be found
Virtual HID devices managed by script!

Thanks

Hello here you go:

Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[2]:
1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
2: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&2E5F6FA0&0&3) selected
USB HID device with hardware id "VID_044F&PID_0402" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device with hardware id "VID_044F&PID_040A" cannot be found
USB HID device with hardware id "VID_044F&PID_040B" cannot be found
USB HID device with hardware id "VID_044F&PID_0409" cannot be found
USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found
USB HID device "AVA Base"(USB\VID_044F&PID_0415\208237685341) selected
USB HID device with hardware id "VID_044F&PID_0414" cannot be found
Virtual HID devices managed by script!
Connecting virtual joystick...Done
Device name set to Thrustmaster Combined
Connecting virtual keyboard...Done
Connecting virtual mouse (absolute axes)...Done
Processing Status.json flags...now running...Done
-----------------------------------------------------------------------------------------------------------------------------------------------

> ENHANCEMENTS LOADING: v5.0.0 TARGET Mappings, Macros & Functions Decrypted <|>

-----------------------------------------------------------------------------------------------------------------------------------------------
:....USER PREFERENCES....:
[Run Software @ Start = 0] [Custom Slider Curve = 1] [PIP Mgt. Preset = 2] [MFD Active = 0]
[Cargo Precision Mode = 0] [S/Cruise @ Throttle = 1] [Chaff @ Escape = 0] [Boost @ Esc = 1]
[Combine External Mic = 0] [Sec. Fire Override = 0] [NightVision HUD = 0] [Ext Mic+Mic = 0]
[Headtrak Center Mode = 1] [Ship Utility Mode = 1] [LED Backlight = 172] [LED ¡Bling! = 1]
[Throttle Axis O/ride = 0] [Joystik Axis O/ride = 0] [Throttle D/zone = 5] [Joys D/zone = 1]

:..DEFAULT TOGGLE STATE..:
[Combine Pri+Sec Fire = 1] [Rot. Correction = 1] [C/ Scoop = 0] [L/ Gear = 0] [Lights = 0]
-----------------------------------------------------------------------------------------------------------------------------------------------
Starting Macros... Compiling Functions... Initialising Joystick Axis... Initialising Slew Axis..
Initialising Throttle Axis... Setting Throttle Profile: FULL SCALE [-100 -> 100]
-----------------------------------------------------------------------------------------------------------------------------------------------
Done... Enhanced ED Script Engineered by Aussiedroid is now running... Fly Safe CMDR! <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
main returned 0

 

[rdalcroft]

Well, that's nice and confusing!

Can you please post the output when you run the script?
In particular the following section;

Currently plugged USB HID devices[1]:
1: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device with hardware id "VID_044F&PID_0404" cannot be found
USB HID device with hardware id "VID_044F&PID_0402" cannot be found
USB HID device with hardware id "VID_044F&PID_B687" cannot be found
USB HID device "T-Rudder"(USB\VID_044F&PID_B679\7&39F7723&0&1) selected
USB HID device with hardware id "VID_044F&PID_B68F" cannot be found
USB HID device with hardware id "VID_044F&PID_040A" cannot be found
USB HID device with hardware id "VID_044F&PID_040B" cannot be found
USB HID device with hardware id "VID_044F&PID_0409" cannot be found
USB HID device with hardware id "VID_044F&PID_0412" cannot be found
USB HID device with hardware id "VID_044F&PID_0413" cannot be found
USB HID device with hardware id "VID_044F&PID_040E" cannot be found
USB HID device with hardware id "VID_044F&PID_040F" cannot be found
USB HID device with hardware id "VID_044F&PID_0416" cannot be found
USB HID device with hardware id "VID_044F&PID_0417" cannot be found
USB HID device with hardware id "VID_044F&PID_0415" cannot be found
USB HID device with hardware id "VID_044F&PID_0414" cannot be found
Virtual HID devices managed by script!

Thanks

FYI old base vs new base in Target

 

[Clicker]

Ok, so Windows/TARGET sees the stick and has combined with your throttle....all good.

I'll go take a look at Aussiedroid's script and see if I can suss it out.

As I do not use this script it may take a while as I need to re-familiarize myself with his code.

I'll be in touch.

 

[rdalcroft]

Ok, so Windows/TARGET sees the stick and has combined with your throttle....all good.

I'll go take a look at Aussiedroid's script and see if I can suss it out.

As I do not use this script it may take a while as I need to re-familiarize myself with his code.

I'll be in touch.

No issues, and don't spend too much time on it. Its not that urgent, I have emailed all the info I can to thrustmaster stating why the AVA base is not present in the hid.tmh file, as I think this may be the reason the script is not assigning the ava bast to the combined virtual input correctly, as when you do the event tester, the joystick axis moves on the lower left hand box, but does not show any axis movement in the main combined window.

see here a vid of the event tester I move the joystick you only see it move in the lower left box for the AVA stick, not in combined (Middle of screen)

But the throttle you will see move in both the upper left and in the middle.

Recording 2024-08-06 063119.mp4

 

[Clicker]

Hi,

The problem is not with hid.tmh. Otherwise you would not get the following;

2: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200"
USB HID device "AVA Base"(USB\VID_044F&PID_0415\208237685341) selected

Your base and stick are being detected by the script just fine.

Can you try the following...
Fire up the script editor, and without compiling or running the script, select "Device Analyzer" and check your axes and buttons are all working fine.

Cheers

 

[rdalcroft]

Hi,

The problem is not with hid.tmh. Otherwise you would not get the following;

2: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200"
USB HID device "AVA Base"(USB\VID_044F&PID_0415\208237685341) selected

Your base and stick are being detected by the script just fine.

Can you try the following...
Fire up the script editor, and without compiling or running the script, select "Device Analyzer" and check your axes and buttons are all working fine.

Cheers

With nothing running the device analyser shows nothing no axis or anything just blank, I thing a script needs to be running for it to work?

 

[rdalcroft]

With nothing running the device analyser shows nothing no axis or anything just blank, I thing a script needs to be running for it to work?

Hi,

The problem is not with hid.tmh. Otherwise you would not get the following;

2: "AVA Base" - "USB\VID_044F&PID_0415&REV_0200"
USB HID device "AVA Base"(USB\VID_044F&PID_0415\208237685341) selected

Your base and stick are being detected by the script just fine.

Can you try the following...
Fire up the script editor, and without compiling or running the script, select "Device Analyzer" and check your axes and buttons are all working fine.

Cheers

Would any of these option have anything to do with it?

 

[Clicker]

Hi,

It should show raw output for both the joystick and throttle.

With no script running etc, try running joy.cpl and select the joystick.

Something I didn't ask, are you running Windows 11 by chance?

Clicker

 

[rdalcroft]

Hi,

It should show raw output for both the joystick and throttle.

With no script running etc, try running joy.cpl and select the joystick.

Something I didn't ask, are you running Windows 11 by chance?

Clicker

yes windows 11.

In joy.cpl both throttle and AVA are registering fine.

 

[Clicker]

Would any of these option have anything to do with it?

Very good question.

The answer is no.
What those do is suppress error messages for disconnected devices.

 

[rdalcroft]

Very good question.

The answer is no.
What those do is suppress error messages for disconnected devices.

ah ok, good to know.

 

[rdalcroft]

Very good question.

The answer is no.
What those do is suppress error messages for disconnected devices.

I can use the basic target.gui and set up profiles for games, and it workes fine.

Even for older profiles, I have to load it up in edit mode, and then add the new AVA base, along side the 2 older warthog throttle and stick.

Copy all the stick assignments from the wart hog stick over to the new AVA stick i just added. save the file.

close the file, re open it in the editor, and delete the old warthog stick then save,

Then the file is good and works in game.

But the script editor i am not very experienced at.

 

[Clicker]

Ok, so now...run the script and rerun joy.cpl.

We're looking specifically for axis output here.
The buttons may not register due to the fact that the script does "stuff" when they're pressed.
(I hope that makes sense)

 

[rdalcroft]

Ok, so now...run the script and rerun joy.cpl.

We're looking specifically for axis output here.
The buttons may not register due to the fact that the script does "stuff" when they're pressed.
(I hope that makes sense)

ok

Buttons work all of them.

But no AXIS X or Y

 

[Clicker]

With the script running?

In joy.cpl, does it show "Thrustmaster Combined" or shows the individual Joystick and Throttle?

(I'm not running Windows 11....for a reason)