Release Aussiedroid's Enhanced Thrustmaster Warthog Script
- Thread starter Aussiedroid
- Start date
There is mapping in the script for the FSS scanner but I don't see anything for the D Scanner? Is there any reason this hasn't been included? As I said earlier I'm just starting to learn the game so sorry if this is dumb question.
@CrackerJack ,
Are you referring to the image files, the script, or general functionality?
Regarding script/functionality...
Aussiedroid's script uses the mapping called "PrimaryFire" and a modifier to achieve a timed hold on the trigger for Discovery Scanner function.
Looking at the code (and not the map images) it looks like this would be activated by PSF+TG1 (Primary fire) or PSF+S3 (Secondary fire).
Legend:
PSF = Throttle Pinky switch - forward
TG1 = Main joystick trigger (Primary)
S3 = Secondary Joystick switch (red) (Secondary)
If flicking PSF first and pressing the trigger/switch does not work, try it the other way around.
ie. Press and hold the trigger then flick the throttle pinky switch to forward.
Regarding image map files...
I cannot find anything representing this specific firing mode.
NOTE: v5 is/was a development or beta version and I do not think Aussiedroid ever got around to finalising.
This would explain why the image map files are all still labelled as v4.3 and this specific function is not shown.
As I don't usually run Aussiedroid's script, I have not tested the above mappings.
It would be great if you could test and report back.
Hope this helps.
Clicker
Last edited:
Correction: I did not look hard enough, this IS included in the binds and mapped to a script define called "HideShipGUI".
This is shown on the Throttle map image (bottom right hand side) and is represented by the back arrow and "[1] Hide Ship GUI"
The "[1]" refers to modifier #1 which is the Joystick Pinky Lever (S4)
The back arrow in the box next to the Throttle Pinky Switch refers to the Back position on that switch.
So...
S4+PSB = Press and hold Joystick Pinky lever (S4) then flick Throttle Pinky switch to back position (PSB) will toggle the Ship or SRV HUD GUI ON/OFF
PSF = Throttle Pinky Switch Forward (away from you)
PSB = Throttle Pinky Switch Back (toward you)
CTRL+ALT+G on keyboard will manually turn the HUD GUI ON/OFF as you have already discovered.
Hope this helps
Clicker
Last edited:
Thank you Clicker for clarifying both of those mappings for me! Cheers!
Hello Commanders,
After a 6-year break, I’ve decided to return to Elite to see what’s changed.
However, I’ve run into some issues while trying to get Aussiedroid’s Enhanced Warthog Script up and running again.
I’m using a Thrustmaster Warthog HOTAS setup along with TFRP pedals, all updated with the latest firmware. The 5.0 script runs fine — it compiles and exits with “main returned 0” so no problems there. Elite Dangerous also launches and recognizes the controller setup.
The problem starts with the bindings file.
I’ve tried both v5.0.0.3 and v5.0.0.4, but for some reason the control mappings are completely off. For example, Roll is bound to something like Joy 4 + Joy 17, and there are lots of other similarly strange bindings. It feels like the devices are not being recognized in the correct order or the bindings don’t match up with the current setup.
Has anyone else encountered this issue recently?
If so, what was your solution?
Also, does anyone happen to have an updated bindings file compatible with the latest script and device configurations?
Any help would be greatly appreciated!
Fly safe,
After a 6-year break, I’ve decided to return to Elite to see what’s changed.
However, I’ve run into some issues while trying to get Aussiedroid’s Enhanced Warthog Script up and running again.
I’m using a Thrustmaster Warthog HOTAS setup along with TFRP pedals, all updated with the latest firmware. The 5.0 script runs fine — it compiles and exits with “main returned 0” so no problems there. Elite Dangerous also launches and recognizes the controller setup.
The problem starts with the bindings file.
I’ve tried both v5.0.0.3 and v5.0.0.4, but for some reason the control mappings are completely off. For example, Roll is bound to something like Joy 4 + Joy 17, and there are lots of other similarly strange bindings. It feels like the devices are not being recognized in the correct order or the bindings don’t match up with the current setup.
Has anyone else encountered this issue recently?
If so, what was your solution?
Also, does anyone happen to have an updated bindings file compatible with the latest script and device configurations?
Any help would be greatly appreciated!
Fly safe,
Yaw is bound to the stick by default, I always switch that to the stick and bind yaw to the the pedals. Everything else stays the same.
Aussiedroid provides 2 sets of mappings.
One for MFG Crosswind Pedals and one without.
Which one are you using, and have you tried the other set?
I seem to recall the one for MFG Crosswind worked for me with TFRP pedals.
I could be wrong though as that was a LONG time ago.
Clicker
Thank you very much.
For both of you.
I tried using both. The Crosswind Pedal one haven't even showed up when i put it into the folder.
I've also tried to rebind the flight axis, that worked.
But unfortunately i'm having issues using the macros on the stick. The big white mini joystick on top of the actual joystick does weird stuff on the right menu. (I'm testing it in the tutorial, don't want to break my actual ship)
I forgot how can I activate my supercruise and FSD with the red 3 stage button on the right side of my throttle. (sry for my silly questions, it was a while ago when I used it)
For both of you.
I tried using both. The Crosswind Pedal one haven't even showed up when i put it into the folder.
I've also tried to rebind the flight axis, that worked.
But unfortunately i'm having issues using the macros on the stick. The big white mini joystick on top of the actual joystick does weird stuff on the right menu. (I'm testing it in the tutorial, don't want to break my actual ship)
I forgot how can I activate my supercruise and FSD with the red 3 stage button on the right side of my throttle. (sry for my silly questions, it was a while ago when I used it)
Last edited:
In the downloaded files there is a full map of all the buttons along with modifiers e.g. pinkie button.
FSD is activated by holding the pinkie trigger and pressing the button on the lowest row of the throttle and closest to you (the others are all switches/toggles).
ETA it’s the autopilot engage disengage button
FSD is activated by holding the pinkie trigger and pressing the button on the lowest row of the throttle and closest to you (the others are all switches/toggles).
ETA it’s the autopilot engage disengage button
Last edited:
Apologies, brain fart, the supercruise/FSD initiated by holding the pinkie trigger and pushing the throttle to maximum forward thrust.
Hi @Gerydos
REMINDER: Aussiedroid has not maintained or developed this script for quite a few years now.
As such, there have been many changes within the game itself which this script does not feature.
Despite many requests to FDEV for this, as of 2025/05/18 (NZT) there is no bind available within the game to turn Supercruise Assist on or off.
Saying that, it is technically possible to map a button to provide this function.
In order to automate this feature within TARGET script, you'd have to create a macro similar to the Auto-docking request feature then map an unused button or switch to fire the macro. (refer AD_EDMacros_v5.0.0.tmh via notepad++)
DISCLAIMER:
As with the 'REMINDER' above, some of the macros within that file were written years ago may no longer work.
The point here is that if you write a macro, every time there's an update to the game you need to test the macros still work and adjust accordingly.
Clicker
Last edited:
Thanks a lot. Now it's time to dip my toes into writing some macros.
(also reacting to your earlier post, yes unfortunately I know that Aussiedroid stopped worked on this. I don't know the reason why he did it, but one thing is for sure. He's work is awesome, and he is a great loss for the community)