Release Aussiedroid's Enhanced Thrustmaster Warthog Script

[Aussiedroid]

No worries imacken,

Ok, that sounds like everything is essentially fine but just not working in game. I wonder if there is an issue with the bindings file. I have had a similar thing happen in the past, and other users have said the same thing, where one or two commands do not work and need to remap and save again to work. Seems to be rare but not sure what causes it. Normally just remapping it once will fix it though and that doesn't seem to be helping for you.

Might be worth trying a fresh bindings file. Redownload the one from the pack, remove the old bindings from your folder and replace it. Retest.

Likewise, it may just be something strange happening when the virtual device is created. Cycling USB ports may help there, likewise a restart/shutdown.

CMDR Clicker a few comments back also had a 'dead' device in game. Running the Event Tester I believe before running the script helped as a workaround. Believe that related back to the Firmware/software version installed and needed to have a full uninstall and reinstall to fix.

Cheers, AD

 

[GravitusMaximus]

No worries imacken,

Ok, that sounds like everything is essentially fine but just not working in game. I wonder if there is an issue with the bindings file. I have had a similar thing happen in the past, and other users have said the same thing, where one or two commands do not work and need to remap and save again to work. Seems to be rare but not sure what causes it. Normally just remapping it once will fix it though and that doesn't seem to be helping for you.

Might be worth trying a fresh bindings file. Redownload the one from the pack, remove the old bindings from your folder and replace it. Retest.

Likewise, it may just be something strange happening when the virtual device is created. Cycling USB ports may help there, likewise a restart/shutdown.

CMDR Clicker a few comments back also had a 'dead' device in game. Running the Event Tester I believe before running the script helped as a workaround. Believe that related back to the Firmware/software version installed and needed to have a full uninstall and reinstall to fix.

Cheers, AD

I had the same problem initially... switching the Thrustmaster Warthog to a pair of USB 3.0 ports fixed the problem for me.

@imacken - if this is already the case, try unplugging the controllers and rebooting the computer. After fully booted up, reconnect the controllers and then spool up TARGET. This happened to me while my old Saitek software was telling the computer the old set was still installed, when you unplug something from the USB, it forces the Device Manager to refresh.

Let me know if that works.

 

[imacken]

Thanks guys, all working fine now with the above errors gone.
The only thing that isn't working is the China Hat binding to FSD and Supercruise.

 

[Aussiedroid]

Thanks guys, all working fine now with the above errors gone.
The only thing that isn't working is the China Hat binding to FSD and Supercruise.

Great to hear!

There is a user preference to change the FSD/Supercruise from the Throttle to the China Hat if you prefer it there

Cheers, AD

 

[imacken]

Thanks AD. Sorry to ask basic questions, but your map shows it as being on the china hat. How do I change it? Obviously, I can just rebind the china hat forward for FSD, but I can't do the long press for Supercruise.
Another basic question - it has been a long time! - how to I get the throttle to go all the way forward, it seems to only go so far. (That's in cockpit, not reality!)

 

[Aussiedroid]

Thanks AD. Sorry to ask basic questions, but your map shows it as being on the china hat. How do I change it? Obviously, I can just rebind the china hat forward for FSD, but I can't do the long press for Supercruise.
Another basic question - it has been a long time! - how to I get the throttle to go all the way forward, it seems to only go so far. (That's in cockpit, not reality!)

No issues mate.

If you look closely at the map it will indicate there are two different mappings for the China Hat Switch. The mappings are based on your setting for CruiseOnThrottle in the AD_EDSettings file. If it is 1, it will map the FSD & Supercruise to the 100% throttle + Pinky Trigger (default). If you set it to 0 it will put the FSD & Supercruise on the China Hat.

You can set 3 Throttle presets to change how the throttle behaves in the game. If its not going all the way it may be the wrong preset (perhaps Precision mode).

Let us know how you get on

Cheers, AD

 

[imacken]

Got it, thanks a lot! I tried with the pinky before putting on to the china hat, but I couldn't see how to exit from Supercruise.

 

[kontrolldon]

Hey guys,

Found something that I can´t figure out...

When pushing in thumb button on the Throttle and Mic setting is Internal (down) it just press and directly releases in the Event tester. If I switch to external it works as it should as a PTT.
Key Press: -
Key Release: - [25ms]

I have tried to delete the script and downloaded it again. So this time it´s not my error.

Thanks in advance and I really look forward to an update when Beyond 4 is released!
Keep up the great work!

(And Clicker, seems I´ll visit NZ in a few months, so I´ll trade a MFD for a beer

 

[Aussiedroid]

Hey guys,

Found something that I can´t figure out...

When pushing in thumb button on the Throttle and Mic setting is Internal (down) it just press and directly releases in the Event tester. If I switch to external it works as it should as a PTT.
Key Press: -
Key Release: - [25ms]

I have tried to delete the script and downloaded it again. So this time it´s not my error.

Thanks in advance and I really look forward to an update when Beyond 4 is released!
Keep up the great work!

(And Clicker, seems I´ll visit NZ in a few months, so I´ll trade a MFD for a beer

Hey kontrolldon,

Good pickup, yeah, this seems a bit counter-intuitive on the surface but should work as expected (let me know if this is not the case in practice though as I don't often use it myself).

It's basically down to the way its programmed. When you press down on the Mic button, it is actually doing a toggle (same behaviour is setup in binds too), but your action is to keep holding the button in (so from code side, this has only toggled the Mic once to On). When you release the Mic button, the reverse action toggles the mic again to off, so as you release the open mic is closed again (from code side, this is the second toggle to Off). It was probably easier to code at the time, but as with most of this sort of thing there are often multiple ways to accomplish the same thing

External Mic controls can be changed as required in the user preferences from toggle to hold depending on your software being used too.

The new 3.3.0 version is working well so far. Frontier just added a sensitivity for the FSS radio tuning so it is working a treat on the Throttle axis now (not to mention the digital tuning and also mapping to pedals is precise). Few other new things in this build and fixes to come too. Probably not long till they go live with this chapter so prepping things soon for release.

Cheers, AD

 

[Clicker]

Hey guys,

Found something that I can´t figure out...

When pushing in thumb button on the Throttle and Mic setting is Internal (down) it just press and directly releases in the Event tester. If I switch to external it works as it should as a PTT.
Key Press: -
Key Release: - [25ms]

I have tried to delete the script and downloaded it again. So this time it´s not my error.

Thanks in advance and I really look forward to an update when Beyond 4 is released!
Keep up the great work!

(And Clicker, seems I´ll visit NZ in a few months, so I´ll trade a MFD for a beer

haha! If you gave me an MFD, I'd have to buy you more than one beer.
And if you gave me no MFD, I'd still buy you a beer!

Cheers
Clicker

 

[kontrolldon]

Hey kontrolldon,

Good pickup, yeah, this seems a bit counter-intuitive on the surface but should work as expected (let me know if this is not the case in practice though as I don't often use it myself).

It's basically down to the way its programmed. When you press down on the Mic button, it is actually doing a toggle (same behaviour is setup in binds too), but your action is to keep holding the button in (so from code side, this has only toggled the Mic once to On). When you release the Mic button, the reverse action toggles the mic again to off, so as you release the open mic is closed again (from code side, this is the second toggle to Off). It was probably easier to code at the time, but as with most of this sort of thing there are often multiple ways to accomplish the same thing

External Mic controls can be changed as required in the user preferences from toggle to hold depending on your software being used too.

The new 3.3.0 version is working well so far. Frontier just added a sensitivity for the FSS radio tuning so it is working a treat on the Throttle axis now (not to mention the digital tuning and also mapping to pedals is precise). Few other new things in this build and fixes to come too. Probably not long till they go live with this chapter so prepping things soon for release.

Cheers, AD

o7 Gents,
I found it. It was keyboard layout related as almost everything else regarding Target GUI scripts. I think Clicker and I agreed that only ENG, GER and FRE keyboard layouts are fully supported a few weeks ago
Well, now I have to abandon 32 years of muscle memory and try to learn using a different layout...

Into the void...




btw. I have got a few hours to kill every day when the offspring is in school, so just shout or find me on Discord if you guys need any help.

 

[Hobson's Choice]

This is a strange one (I think).

Summary.
Warthog Hotas Throttle lever does not work. Regardless of throttle position, engines are at max on entry to game, if keyboard X is used to stop engines, throttle lever does nothing.

Detail
I run ED as an independant program. I sometimes run ED in VR, but not recently and when I do it is as an independant program, not through Oculus or Steam. I have a script that disables/enables Oculus Home service as and when I need it. When enabled I select HMD in graphics options.

I turned off ED yesterday and everything was working fine.
I fiddled with Steam VR for a while (hadn't used it before so set up the environment).

I am not using the Beta version of ED, Just ED Horizons. I am using Aussiedroid script - Aussiedroid Warthog Enhanced 3.2.0

Today when I started ED, I found that I could not load the aussiedroid bindings. The bindings file was ok, but did not appear in the controls menu, all that was there were generic type options that I have never seen before. The SteamVR app loaded when I started ED. It has always (well, for some months) done that with no problems, I simply select exit from the SteamVR drop down menu. I read that it can cause interference with bindings, so, I totally removed Steam (including my Steam games. Why does it do that without warning? Grrr).

Rebooted PC and the aussiedroid option appeared in the controls menu.
But....
Now, the engines are set at max and moving the throttle in ED, in either SRV or Ship, has no effect. Regardless of position of the throttle lever, even fully back (off), the engines are set at max.
Changing the flaps switch to any of the three throttle override options has no effect, the engines are still set at max.

Running the warthog profile in Target GUI, shows no errors (Main returned 0).

The bindings for flight and SRV throttle, in the controls menu are set to Joy Z-axis, Inverted & Full Range

In the Device Analyser,
the Throttle - Hotas Warthog window, for Z and Rz axes, shows a range of 0 to 16383. When the throttle is in the 'off' position, the value is 18383, when in the Max position the value is 0 (which I think is correct for an Inverted option).
the Thrustmaster Combined window, for Z and Rz axes, shows a range of -32767 to +32767. When the throttle is in the 'off' position, the value is +32767, when in the Max position the value is -32767.
The Throttle Axis has values of -32767 to +32767, but the 'pip' does not change when the throttle lever is moved. It stays at a value of 0.

The Incremental throttle buttons on the keyboard work as intended. Numlock buttons give + and - increments. The X stops the engines.
When the keyboard numpad/X buttons are used, the throttle lever then does nothing, Off to Max does not start the engines. The throttle lever is U/S.
If I quit to menu, then start ED again, the situation reverts to throttle being at max regardless of throttle lever position.

I have unzipped a vanilla set of aussiedroid scrip files.
I have replaced the binds file in the Elite Dangerous/Options/Bindings folder.
I have replaced the Aussiedroid-ED-Warthog-Script folder contents.
This had no effect. The events detailed above are the same.

Can you AD, or anyone else who may have had this problem, please have a solution?

 

[Aussiedroid]

Hey Mate,

Reading through your symptoms it looks like 2 things happened:

1) Your throttle cut out at some point (perhaps when you plugged your VR gear in?), although the virtual device didn't error out, if its not found in ED on startup it will not show your bindings associated to it. That relates to the GUID issue that Frontier introduced in 3.0 and remains an issue. Also, CMDR Clicker a few comments back had a similar drop out scenario on his Joystick. Believe it is a bug in TM software. There was a workaround I believe to open Event Tester before start (I think) but more details a page or two up (#654).

2) After finding the Throttle again, it has not initialised properly. Problematic axes or buttons etc, causing the weird behavior in ED. Might be worth a shutdown, unplug all USB and PC for a few mins and then reinitialise and try running script again. It can be a PITA when that happens, but eventually comes good from my experience. If still problematic then a full uninstall, unplug and reinstall the latest software/drivers/firmware and plug back in as requested during install. Retest. Try a restart/shutdown a few times first though as normally does come good by itself.

PS. Will likely have latest build of script uploading in a few days, so latest software/drivers/firmware will be needed to run it too.

Let us know how you get on.

Cheers, AD

 

[Alpenmilch]

Oh man, I wish I inherited mine LOL Congrats!

Thanks as well for the kind words. I took a bit of a break myself for a while recently, although bit more invigorated now with the beta in good swing and new stuff to play with. Looking forward to it dropping to the live servers.

I've got a new 3.3 version I am working on currently through the beta, so come the live drop there will be an updated version to cover all the new stuff for you to download.

Spent some more time using the FSS and exploration, and feel I have a fairly solid setup now. Want to play a bit more though as I have been back and forth on a couple of button positions. All part of the fun of figuring this stuff out. Also need to play some mining this weekend and ensure that it plays well too.

Cheers, AD

Mylord, time to kiss your Ring again.

Looking forward to another piece of art from you is part of the Update happiness.

Thanks as always.

You made the Warthog to "THE THING" to fly with

 

[Hobson's Choice]

Summary.
Still not working. Still only a on-off response from throttle, either nothing (if pulled back to OFF) or max
Device Analyser shows full range, Throttle works correctly profile is NOT running and if using the Thrustmaster Warthog bindings file.
Details of workflow (!) follows. See note at end for strange response when set to Forward Only.

Flow for setting up Thrustmaster Warthog Joystick and Throttle plus Pedals.

Windows 10.
Uninstall all thrustmaster software.
Shutdown PC, remove power lead from PC.
Unplug joystick, throttle (and rudder).
Go and have a cup of Coffee - For The Mug !
Plug in PC.
Switch on PC.
Install latest software/drivers 2018_TMHW_1.exe from Thrustmaster website.
Plug rudder into USB. Windows made little happy sounds, ending with message 'T-Rudder driver installation complete'.
Start the Thrustmaster Firmware program.
Plug joystick and throttle into USB. More Windows happy sounds.
The throttle and joystick appears in the device window.
Selected joystick, click OK. After a minute or two of activity, three green ticks appeared. It took me two attempts.
Repeated for the throttle.
Started the Thustmaster Control program to check all is ok with both devices.
Started the Thrustmaster Control program and run calibrations on all Thrustmaster devices.
Installed the latest Thrustmaster Script program TARGET_v3018(328v2).exe from Thrustmaster website.
Restarted the PC.
Because I deleted EVERYTHING Thrustmaster, I now needed to setup the Aussiedroid Script again.
Started the script editor, compiled AD_ED_v3.2.0.tmc, navigated to AD_EDSettings_v3.2.0.tmh and set my options. Compiled.
Started GUI Command Center and run.
Opened ED Launcher & Play Elite, select bindings file in Controls.
Changed keybinding for Rudder (yaw) and Joystick X Roll.
Checked binding for throttle. Z-axis, Inverted, full range. OK.

A). Still doesn't work. Throttle acts as on-off switch, when at Off position (pulled back), engines zero, when at any position except Off, engines are at maximum.
But in the Device Analyser, the throttle show a full range in the of -32767 to + 32767. Which is correct.
The throttle is physically working correctly, as the correct full range is seen in the device analyser, but that is not translating to full range in the game.
If I close the Target GUI profile, I see a keybindings option in controls for Thrustmaster Warthog.
The Flight Throttle binding is Joy Z-Axis Inverted Forward Only. I changed that to Full Range.
Now in Elite, the throttle performs correctly, full range, plus to minus!! So, the throttle is working corrrectly in a bindings file.

However, if I then run the Target GUI, with AD_ED_v3.2.0.tmc, and start Elite, select the Aussiedroid bindings file, It still is same as in A). above.

I have uninstalled the drivers, unplugged devices, plugged in and reinstalled drivers twice.
I have unplugged and plugged in the devices, and rebooted four times. No change.

Here is another thing...
If I select FORWARD ONLY for engine throttle in the Aussiedroid bindings file, the result is weird.
With flaps set for 0 to +100, mThrottleFwdOnly, as soon as the throttle is taken off the OFF position, engines immediately go to full throttle (yeah. that's ok).
With flaps set for -50 to +50 mThrottlePrecision, as soon as the throttle is taken off the OFF position, engines immediately go to full throttle. Nope, that's wrong.
With flaps set for -100 to +100 mThrottleFullScale, as soon as the throttle is taken off the OFF position, engines immediately go to HALF throttle. Nope, that's wrong.
No option allows for reverse engines!

I wil try some more experimentation. but that's enough for today. ;-)

There is no Steam software on the PC, either normal Steam or Steam VR. There is Oculus Home, but the Oculus service is disabled.

Over to you guys

 

[Aussiedroid]

I'm not sure why this is happening mate. I'm running out of ideas. I know the code is fine and the binds are correct for the throttle, but its clearly not initialising properly on your hardware. A full uninstall/reinstall should have fixed that along with unplugging your other USB devices.

Have you tried clearing the Throttle mapping in the bindings file, apply to save (unbinded), and then rebinding them again and saving the bind again? (basically remapping the same thing)

For reverse, if you are not using Full Range you need to use the digital reverse thruster, not the throttle as the script overrides the binding file in this instance.

AD

 

[feiercrack]

...maybe he got some issues with the USB port (drivers) which USB is he using, USB 2.0 or 3, or 3+ ?
then it could be that the internal warthog chip is damaged...

i would check all my USB port drivers first.

then i would write an ticket to thrustmaster...

your script is running as an charme, as ever!
but i miss your new 3.3 version, cause only 3.2 is downloadable at moddb.com -.-

thanks for the good work!
cheers

 

[kontrolldon]

...maybe he got some issues with the USB port (drivers) which USB is he using, USB 2.0 or 3, or 3+ ?
then it could be that the internal warthog chip is damaged...

i would check all my USB port drivers first.

then i would write an ticket to thrustmaster...

your script is running as an charme, as ever!
but i miss your new 3.3 version, cause only 3.2 is downloadable at moddb.com -.-

thanks for the good work!
cheers

Same here, seems like its only the 3.2.0 linked. Frontier servers are up BTW!

 

[GravitusMaximus]

AD,

Can you confirm the file at moddb.com is your 3.3 or is it the 3.2 as it is stated in the text?

 

[Hobson's Choice]

I'm not sure why this is happening mate. I'm running out of ideas. I know the code is fine and the binds are correct for the throttle, but its clearly not initialising properly on your hardware. A full uninstall/reinstall should have fixed that along with unplugging your other USB devices.

Have you tried clearing the Throttle mapping in the bindings file, apply to save (unbinded), and then rebinding them again and saving the bind again? (basically remapping the same thing)

For reverse, if you are not using Full Range you need to use the digital reverse thruster, not the throttle as the script overrides the binding file in this instance.

AD

Yeah. Tried that. But will look at it again.
I too know the code is fine because I have had it working properly for a year, or so. So, as you say, it's only TARGET that is failing to pick it up. I could
(more or less) understand it if it was just going to forward only, but going from off to max at the smallest movement of the throttle is just weird, ie, digital off-on.
Of course, it might be a fault with the throttle body electronics, if I can't get anywhere soon, I will contact Thrustmaster.
I will try removing ALL pc usb connections and starting with warthog, then putting the others back in.
Annoying, because I haven't been playing much and just got my muscle memory working :-( .
I am using USB 2.0 sockets (onto a Rampage Extreme IV board), not mixing USB 2.0 and USB 3.0
I will let you know if there is any positive news.
Cheers AD