Release Aussiedroid's Enhanced Thrustmaster Warthog Script

vorr · Apr 10, 2022

Hi all, first of all I want to talk you all for keeping the forums alive and helping people.
I am having problems with my Aussiedroid's Enhanced Warthog Script 4.3.0.
It works fine without any issues on Horizons but when I switch to Odysseys its just not there and I cant select it from controls drop down menu, furthermore I cant even see the warthog.
When the game is loaded as Horizon I can manually choose Aussiedroid's Enhanced Warthog Script 4.3.0 or Warthog from the drop down menu (pre-sets) but if i load the game as Odysseys I cant choose or see Odysseys or the Warthog.
Please help
Thank You

Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&F2C1491&0&1) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\6&F2C1491&0&4) selected
USB HID device with hardware id "VID_044F&PID_0403" cannot be found
USB HID device with hardware id "VID_044F&PID_B10B" 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_0405" cannot be found
USB HID device with hardware id "VID_044F&PID_0406" cannot be found
USB HID device with hardware id "VID_044F&PID_0407" cannot be found
USB HID device with hardware id "VID_044F&PID_0408" 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
-----------------------------------------------------------------------------------------------------------------------------------------------

> ENHANCEMENTS LOADING: v4.3.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 = 0]
[Combine External Mic = 0] [Sec. Fire Override = 0] [NightVision HUD = 0] [Ext Mic+Mic = 0]
[Headtrak Center Mode = 0] [Ship Utility Mode = 0] [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 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
Throttle Profile: FORWARD ONLY [0 -> 100]

Irakandjii · Apr 10, 2022

Clicker said:
Hi @Irakandjii ,

Seems you've found where to change colours via the Options, but that has not helped you.
My only advice would be to use Notepad++ as your main editor, then load into the TARGET editor to compile/run.

Clicker

Ok, thank you for the quick response. I will try an alternate editor most likely VS Code since it supports include files nicely.
I am just burning into the code now and learning more about how it is done. You folks have done a very professional job and the documentation is exemplary.

Clicker · Apr 12, 2022

vorr said:
Hi all, first of all I want to talk you all for keeping the forums alive and helping people.
I am having problems with my Aussiedroid's Enhanced Warthog Script 4.3.0.
It works fine without any issues on Horizons but when I switch to Odysseys its just not there and I cant select it from controls drop down menu, furthermore I cant even see the warthog.
When the game is loaded as Horizon I can manually choose Aussiedroid's Enhanced Warthog Script 4.3.0 or Warthog from the drop down menu (pre-sets) but if i load the game as Odysseys I cant choose or see Odysseys or the Warthog.
Please help
Thank You

Allocated ProcInstances found from the previous run: use FreeProcInstance() ***
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
2: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
3: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\6&F2C1491&0&1) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\6&F2C1491&0&4) selected
USB HID device with hardware id "VID_044F&PID_0403" cannot be found
USB HID device with hardware id "VID_044F&PID_B10B" 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_0405" cannot be found
USB HID device with hardware id "VID_044F&PID_0406" cannot be found
USB HID device with hardware id "VID_044F&PID_0407" cannot be found
USB HID device with hardware id "VID_044F&PID_0408" 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
-----------------------------------------------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------------------------------------------------
:....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 = 0]
[Combine External Mic = 0] [Sec. Fire Override = 0] [NightVision HUD = 0] [Ext Mic+Mic = 0]
[Headtrak Center Mode = 0] [Ship Utility Mode = 0] [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 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
Throttle Profile: FORWARD ONLY [0 -> 100]

Hi @vorr ,

Looks like the script is running fine.

When the Aussiedroid profile is not available, it can mean one of the controllers defined inside the bind file cannot be found....check your bindings folder and see if there's an error file been created within called "BindingLoadingErrors.log". The file will contain one or more lines that look like "Failed to find GUID for device: 16D00AEC".

You said the profile works with Horizons, so it should also work for Odyssey.
Try to unplug/replug your controller USB plugs, restart windows and try again.

Let us know how you get on.

Clicker

RagingDoc · Sep 20, 2022

UPDATE: Problem solved. Rebooted the computer, and starting now as Administrator.

Hi all,

I've been away for a couple of months, and am now trying to reinstall ED with this great script on a new PC. It went pretty smooth, until I hit a strange error after starting the AD_ED_v5.0.0.tmc script:

[...]
Starting Macros... Compiling Functions... Script stopped!

Runtime Error: STOP request received while running main on line 84 in "C:\Users\windo\Documents\EliteDangerous\AD-EDWarthogEnhancedScript-odyssey\Warthog Script\AD_ED_v5.0.0.tmc"
Error:Script run timed out!

Did I forget of misconfigure something?

Cheers
RagingDoc

Mettius · Apr 9, 2023

Coming back to ED a couple years later. I see there is a "Basic" and "Full/Advanced" version of the button maps. How do I load the Full/Advanced? It seems like following the instructions from the installation.txt file yeields the Basic version.

Clicker · Apr 9, 2023

If I recall correctly, loading the Aussiedroid script and running in TARGET will load everything.

Some things are enabled via one of AD's script config files.

The maps are just cutdown cheat sheets to help with the learning curve.

Hope this helps

Mettius · Apr 10, 2023

Clicker said:
If I recall correctly, loading the Aussiedroid script and running in TARGET will load everything.

Some things are enabled via one of AD's script config files.

The maps are just cutdown cheat sheets to help with the learning curve.

Hope this helps

Thanks. I think I figured it out. My issue was with the china hat switch not engaging supercruise/jump. I found the setting to fix it. Thanks.

CMDR Saigon · Jun 14, 2023

o7 CMDRs,

Found a great offer that I couldn't resist so bought the Warthog stick & throttle. I am in the financial industry so this is a steep learning curve for me when it comes to scripting etc.

I have tried to follow CMDR Aussiedroid instructions@github but I always get the below error. Also on step 3: "Edit User Preferences file, primarily the 'Core Hardware' variables (rest can be reconfigured on later runs) SAVE & Close TARGET Script Editor when done editing." What do I actually need to do here?

Appreciate help & advices.

Clicker · Jun 16, 2023

Hi @CMDR Saigon ,

Let's start from step 1...

If you have not already done so, make sure you've installed the TARGET drivers to WINDOWS.
Next, make sure your firmware is latest version.

Both can be found at following link along with instructions....

Hotas Warthog – Thrustmaster

Hotas Warthog -

support.thrustmaster.com

Next, and just so you know...version 4.3.0 is VERY old.
If I'm not mistaken latest version is/was version 5.0.0, so you probably should be trying to install that one.

Confirm above and we can go to next step if needed.

Cheers
Clicker

CMDR Saigon · Jun 16, 2023

Clicker said:
Hi @CMDR Saigon ,

Let's start from step 1...

If you have not already done so, make sure you've installed the TARGET drivers to WINDOWS.
Next, make sure your firmware is latest version.

Both can be found at following link along with instructions....

Hotas Warthog – Thrustmaster

Hotas Warthog -

support.thrustmaster.com

Next, and just so you know...version 4.3.0 is VERY old.
If I'm not mistaken latest version is/was version 5.0.0, so you probably should be trying to install that one.

Confirm above and we can go to next step if needed.

Cheers
Clicker

Hi CMDR Clicker,

Thank you for your reply.

I have the latest firmware + drivers. I will try version 5.0.0 later and let you know if I still have any issues Sir.

On a side note, moving from an X52 Pro set up to the Warthog is definitely several levels up on feel, quality & accuracy and I am pretty fast at relearning buttons, mappings etc.. but getting used to pedals, no twist and stick with such friction for fast manoeuvres will probably take several more weeks...led to my 1st death in a long time@AXCZ last night...

Many thanks,

watty · Jun 21, 2023

o7 CMDRs,
I've been using AD's script for my joystick for a few months, and it has been working great. However, I've recently encountered a problem specifically when trying to land on planets with atmospheres. Whenever I attempt to land, the script fails, and I have to resort to manually pressing the "L" key on my keyboard to initiate the landing. Oddly enough, after this manual landing, the script works fine until I have to land on another planet with an atmosphere. I suspect that there may be an issue with the status file, but I'm unsure how to resolve it.
I would greatly appreciate any help or suggestions that you could provide. Thank you in advance for your time and support.
Fly safe, CMDRs!

Clicker · Jun 21, 2023

Hi @watty,

Does this happen every time you try to land on a planet, or only sometimes?
Does the script actually crash, or landing gear simply doesn't deploy?
If the script is crashing, what error message gets sent to console (if any).

Also, what version of the script are you using?

Assuming version 5.0.0 and script not crashing, when it happens, Alt+Tab to the console and see what console messages have come up.
AD's script writes messages for DELPOYED, RETRACTED and when it's an invalid choice.
(ensure 'VerboseOutput' is set to 1 in AD_EDUserPrefs_v5.0.0.tmh)

Invalid choices include;
a) if you are landed/docked
b) if you are in the SRV
c) if you are in supercruise

Whilst the script does not currently check "glide mode", that is also an invalid choice.

Hope this helps.

Cheers
Clicker

Wind-Dancer · Oct 24, 2023

Hi, firstly, love Aussiedroid's Warthog setup, and even though I've modified a couple of settings I couldn't have done it without his original script...

I've seen mention, particularly on this thread, of the work he was doing on a 5.0 version that would include 'On Foot" bindings, but I can't find it anywhere on the internet? The only source I can find is still 4.3.0 - and in GitHub it still lists only that version...

Can anybody point me in the right direction for his latest version that includes the Odyssey 'On Foot' bindings?

Many thanks
David

Clicker · Oct 26, 2023

Hi @Wind-Dancer ,

I think I have a copy of the v5 package at home on my PC.
When I get home, I'll confirm the version etc.

Clicker · Oct 26, 2023

Never mind, found it online...

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

NOTE: this version uses state tracking by polling the status.json file. When this script was last written, the version of the journal files was '31'...we're now up to v37.
Don't forget to set the status file location correctly in AD_EDUserPrefs_v5.0.0.tmh file (line 41).
You should be able to just replace "<username>" with your windows username and it should just work, unless you have a customized install.

Also NOTE since this script version was created the Thrustmaster Target drivers have been updated so if you get weird script startup errors, check and update these if required.
Latest TARGET v3.0.21.910
Joystick firmware v12
Throttle firmware v23

I think it should still work fine, but if not, post here with any errors you get and I'll have a go at suggesting updates.

Fill your boots!

Clicker

Wind-Dancer · Oct 26, 2023

Hi Clicker,

Many thanks for the link and the additional info. For some reason I couldn't find 5.0 anywhere, so I'm glad you were able to!

I'll be interested to see what's changed between 4.3 and 5.0 (other than On Foot bindings) - with the usual backup first ;-)
Thank you for the offer of help, greatfully received. In the past the only area was interaction with Discord and VoiceAttack - though I don't tend to use it for speech commands any more.

Many thanks
Wind-Dancer

Clicker · Oct 27, 2023

No problem.

See you in the black.

And if I do, make sure your hold is full of High Temperature Diamonds or Tritium!
;-)

rdalcroft · Aug 6, 2024

Hello

Is there anyway to get this script to work for the new Thrustmaster AVA base?

Would I need to add the base to the current target profile, then copy each binding over from the old warthog stick? and save. Then re-open the file and delete the warthog stick from the profile leaving just the AVA base/stick and tThrustMaster

Seems thrustmaster did not think this through, for users with profiles already set up? All button and switches have the exact same naming. So it should not be that hard to do. only thing is the scripts do they go off the id of the stick/base?

It works for basic target profiles, but not sure for this one because of the scripts?

Clicker · Aug 6, 2024

@rdalcroft ,

Do you already have this base and the script won't work?
What stick are you using with the base...it looks like it may not support the Warthog stick (?)

Aussiedroid has not been seen in a couple years.
That said, I know enough to make minor tweaks to his scripts to enable the base if required.

I will download the latest version of TARGET and have a quick look.

Clicker

rdalcroft · Aug 6, 2024

Clicker said:
@rdalcroft ,

Do you already have this base and the script won't work?
What stick are you using with the base...it looks like it may not support the Warthog stick (?)

Aussiedroid has not been seen in a couple years.
That said, I know enough to make minor tweaks to his scripts to enable the base if required.

I will download the latest version of TARGET and have a quick look.

Clicker

Hello
wow quick reply:

I have the F16 stick with the new AVA base.

Now I thought the script would automatically just select the new base, I tried adding the ID for the new base in the hid.tmh: char HWID_AVA_BASE[]= "VID_044F&PID_0415&REV_0200" but I do not think this does anything.

I thought i couls set up or edit a target .fcf file, but I didn't realise when you use a script, there is no .fcf file.

The script does see the base when loading the script, but it does not apply the buttons or axis to the stick. The throttle works ok though.

I have also sent an email to Thrustmaster to see if they could come up with an easy conversion script for users with older script with the new AVA Base. It should not be a hard thing to do, as all button and axis assignments are the same its just the base ID thats different: "VID_044F&PID_0415&REV_0200"