Release Aussiedroid's Enhanced Thrustmaster Warthog Script

Aussiedroid · Nov 3, 2018

Mettius said:
Hello, Yes. They are the latest from Thurstmaster. Pretty cool (but a bit pricey). All the definitions are in the most recent TARGET release. Just had to reference them. I just copied and renamed the pedals section you had for the older TM pedals with the new device name and removed one } and everything works fine.

Please feel free to use my edits. I love your config (I modified a few things because the the slew control on the warthog kind of blows, but otherwise "just makes sense").

Cheers! I had a look at a couple videos of those pedals last night. They look really nice! Looks like something compatible to the Warthog level of quality. Interesting design.

imski said:
As someone who’s come to rely on your TARGET profiles and lacking the patience to learn how to modify them myself, I’m looking forward to your updated bindings.

I should add, I’ve been toying with using the toe breaks as an alternative to putting the throttle into full reverse on the right and an all stop on the left, but need to play with it in combat to see if it actually works for me.

Thanks a lot imski!

WIP on the new version currently. Hoping to get some time in the cockpit today and try a few more things out. I will be targeting to have something ready for launch day all going to plan, but in the mean time I guess if you wanted to try out the beta you will have to map the new stuff temporarily yourself, sorry.

(Remember to make a backup)

Interesting idea with the toe brakes. I see how that could be very handy if mastered. I would personally struggle though, I have lazy feet haha and often find I am pressing the toe brakes when I shouldn't be (even when I set big deadzones). I really should revisit and find a use for my toe brakes one day

Cheers, AD

Clicker · Nov 4, 2018

For some reason, I cannot move the targetting reticle for the surface probes.

In FSS mode I use the joystick for pitch and my pedals for yaw, and they work fine in that mode.
But moving into the detailed surface scan mode, I cannot move around.

What have I missed?

Clicker

p.s. I'm posting here as well as the feedback page in order to hopefully get a quick response!

Aussiedroid · Nov 4, 2018

Hey Clicker,

I think I read that this is currently mapped to the Multicrew 'Third Person' axes and its a known bug. If you dont have those mapped then it may need to be configured there for the time being.

Mine seems to work testing not long ago for a reference.

Cheers, AD

Clicker · Nov 4, 2018

Aussiedroid said:
Hey Clicker,

I think I read that this is currently mapped to the Multicrew 'Third Person' axes and its a known bug. If you dont have those mapped then it may need to be configured there for the time being.

Mine seems to work testing not long ago for a reference.

Cheers, AD

Yep, that worked!

Spent over an hour searching and didn’t find that particular gem, so, THANKS!!

Clicker

Clicker · Nov 6, 2018

!!! BLING !!!

Here's a little something that adds bling to the script.

Code:

	int initFlashLED(int x) {		
		int counter = 0;
		while (counter < 11) {
			ActKey(KEYON+PULSE+LED(&Throttle, LED_ONOFF, LED_CURRENT^x));
			counter = counter + 1;
			Sleep (80);		
		}
	}

Example: "initFlashLED(LED1);" \\ Flashes LED1 5-6 times...end result is a toggled LED.

BEWARE: commands are QUEUED during the loop so be careful setting the sleep parameter too high.

There may be a more elegant way of doing this and perhaps a way to do this without commands being queued during the loop.
If so, please, do tell!

Clicker

Clicker · Nov 6, 2018

No queued commands!

Code:

	int initFlashLED(int x) {	
		int counter = 0;
		while (counter < 15) {
			DeferCall(counter*80, &ActKey, KEYON+PULSE+LED(&Throttle, LED_ONOFF, LED_CURRENT^x));
			counter = counter + 1;
		}
	}

:-D

Clicker

Aussiedroid · Nov 6, 2018

Very cool mate!

Here was my less elegant attempt:

Code:

[COLOR=#1e90ff][B]int[/B][/COLOR] initFlashLED[COLOR=#ffffff]([/COLOR][COLOR=#1e90ff][B]int[/B][/COLOR] x) {        
            [COLOR=#1e90ff][B]int[/B][/COLOR] counter = [COLOR=#ffffff]0[/COLOR];
            [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]FlashActiveCheck == [COLOR=#ffffff]0[/COLOR]) {
                FlashActiveCheck=!FlashActiveCheck;
                [COLOR=#1e90ff][B]while[/B][/COLOR] (counter < [COLOR=#ffffff]11[/COLOR]) {
                    ActKey[COLOR=#ffffff]([/COLOR]KEYON[COLOR=#ffffff]+[/COLOR]PULSE[COLOR=#ffffff]+[/COLOR]LED(&Throttle, LED_ONOFF, LED_CURRENT[COLOR=#ffffff]^[/COLOR]x));
                    counter = counter + [COLOR=#ffffff]1[/COLOR];
                    Sleep ([COLOR=#ffffff]80[/COLOR]);        
                    }
                FlashActiveCheck=!FlashActiveCheck;
                }
            }

Not that I have tested though...

Will give your better version a test out.

AD

Clicker · Nov 6, 2018

Aussiedroid said:

Very cool mate!

Here was my less elegant attempt:

Code:

[COLOR=#1e90ff][B]int[/B][/COLOR] initFlashLED[COLOR=#ffffff]([/COLOR][COLOR=#1e90ff][B]int[/B][/COLOR] x) {        
            [COLOR=#1e90ff][B]int[/B][/COLOR] counter = [COLOR=#ffffff]0[/COLOR];
            [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]FlashActiveCheck == [COLOR=#ffffff]0[/COLOR]) {
                FlashActiveCheck=!FlashActiveCheck;
                [COLOR=#1e90ff][B]while[/B][/COLOR] (counter < [COLOR=#ffffff]11[/COLOR]) {
                    ActKey[COLOR=#ffffff]([/COLOR]KEYON[COLOR=#ffffff]+[/COLOR]PULSE[COLOR=#ffffff]+[/COLOR]LED(&Throttle, LED_ONOFF, LED_CURRENT[COLOR=#ffffff]^[/COLOR]x));
                    counter = counter + [COLOR=#ffffff]1[/COLOR];
                    Sleep ([COLOR=#ffffff]80[/COLOR]);        
                    }
                FlashActiveCheck=!FlashActiveCheck;
                }
            }

Not that I have tested though...

Will give your better version a test out.

AD

I had not seen that...was that new or something you didn't publish in 3.1.0 or 3.2.0?

Clicker

Aussiedroid · Nov 6, 2018

Just something new I modified from your earlier post, trying to get it not to queue the commands if done quickly.

Aussiedroid · Nov 6, 2018

Well, I ended up implementing the FlashLED code last night, played around a bit with timings/speed (gone with a slightly faster and shorter sequence), and added it behind a user preference so players can choose if they want it enabled or not across the toggles. Works perfectly, so I started playing with the code to see what I might be able to do with it. Long story short, I messed up the code at one point, crashed with error but the Throttle backlighting completely died! Script wouldnt change it, manual control was dead, restart PC, unplug device etc, would not work even when I fixed the typos. Fearing the worst I called it a night, unplugged the devices overnight and turned off PC. Thankfully, it came good this morning but was a bit of a worry. Just a heads up.

Axsom · Nov 8, 2018

Anyone use Voice Packs/Attack?

I would like to use HCS Voice Packs in conjunction with this script, however they require the use of key binds in Elite. Anyone have any experience setting this up that can offer advice?

Aussiedroid · Nov 8, 2018

Hi again Axsom,

Originally the scripted used all the default HCS Voice Pack keys. These are still setup, but from what i understand these days that it will map/align to your own keymappings via Voice Attack whatever is setup. I don't use VA myself so cannot confirm directly how to setup everything, but should in theory still be compatible.

Is anyone else using VA with the current version of the script, able to confirm how to setup?

PS - Your comment on the Steam Guide, regarding nothing happening in the game when loading the script. I had the same issue yesterday. I had to unplug everything and shutdown. Restart and then plug Joystick, then throttle. My Joystick was also running an old version of the firmware, so I updated that to align with latest software version and drivers and seems to have come good after a couple of tries. Was a bit worrying as it was working fine till the virtual device loaded, but looks like the devices were registering in the wrong order in Windows causing the issue.

Cheers, AD

Clicker · Nov 9, 2018

Aussiedroid said:
Well, I ended up implementing the FlashLED code last night, played around a bit with timings/speed (gone with a slightly faster and shorter sequence), and added it behind a user preference so players can choose if they want it enabled or not across the toggles. Works perfectly, so I started playing with the code to see what I might be able to do with it. Long story short, I messed up the code at one point, crashed with error but the Throttle backlighting completely died! Script wouldnt change it, manual control was dead, restart PC, unplug device etc, would not work even when I fixed the typos. Fearing the worst I called it a night, unplugged the devices overnight and turned off PC. Thankfully, it came good this morning but was a bit of a worry. Just a heads up.

Hmmm...I’ve not seen that.

What I have seen recently though, whilst cutting and tweaking code is that every now and again, usually after trying to run something that doesn’t work or crashes the script, one of the Thrustmaster services crashes. Usually restarting the service manually sorts it.

Does not sound like this was your problem though since a reboot didn’t fix.

I’m wondering that if you are trying to cycle the LEDs for too long and/or very fast, you may be overheating some of the electronics controlling the LEDs in the Throttle base.

Clicker

Clicker · Nov 9, 2018

Aussiedroid said:
Hi again Axsom,

Originally the scripted used all the default HCS Voice Pack keys. These are still setup, but from what i understand these days that it will map/align to your own keymappings via Voice Attack whatever is setup. I don't use VA myself so cannot confirm directly how to setup everything, but should in theory still be compatible.

Is anyone else using VA with the current version of the script, able to confirm how to setup?

PS - Your comment on the Steam Guide, regarding nothing happening in the game when loading the script. I had the same issue yesterday. I had to unplug everything and shutdown. Restart and then plug Joystick, then throttle. My Joystick was also running an old version of the firmware, so I updated that to align with latest software version and drivers and seems to have come good after a couple of tries. Was a bit worrying as it was working fine till the virtual device loaded, but looks like the devices were registering in the wrong order in Windows causing the issue.

Cheers, AD

Hi AD and Axsom,

I use VA with HCS voicepacks and can confirm that it reads in your keybinds file and maps its commands to your key binds, so, should be compatible with ADs script with the only exception being things like the status LEDS which will go out of sync. (Or anything else that uses state tracking within the script)

Example, using HCS Voicepacks/VA to issue a toggle of the landing gear...will toggle this in game, however there is currently no way that ADs script will know you’ve done that, so the LED stays on (or OFF as the case may be).

EDIT: toggle switches may also cause a temporary issue, example, if you’ve used an HCS Voicepack command for things like the cargo scoop or silent running....the switch on the HOTAS will likely then need to be toggled twice or the LED state fixed as per ADs instructions.

Feel free to be specific with your query, if this has not answered your question.

As for “nothing happening” when you start your script...well, I reported this issue in this thread a couple months back.
This is usually directly related to the new version of the firmware and/or TARGET software.

I still encounter this issue from time to time and have an open ticket with Thrustmaster.

The workaround I use is;
Every time I start the script I open the event tester and check that the buttons on the JS still fire the appropriate key.
If not, usually a simple restart of the script fixes this.

If you are finding that you need to unplug/replug and or restart your PC, then I’d suggest a complete reinstall of the drivers and software...following Thrustmaster’s instructions, to the letter!

Clicker

Aussiedroid · Nov 9, 2018

Clicker said:
Hmmm...I’ve not seen that.

What I have seen recently though, whilst cutting and tweaking code is that every now and again, usually after trying to run something that doesn’t work or crashes the script, one of the Thrustmaster services crashes. Usually restarting the service manually sorts it.

Does not sound like this was your problem though since a reboot didn’t fix.

I’m wondering that if you are trying to cycle the LEDs for too long and/or very fast, you may be overheating some of the electronics controlling the LEDs in the Throttle base.

Clicker

I have had that crash once too the other day, the TM FAST Service or something. That is about when everything went pear-shaped, but not really sure if it was the coding or something else. I have been fortunate not to have too many issues, but any rate all good now

Cheers, AD

GravitusMaximus · Nov 17, 2018

Hey Aussiedroid... first of all, thank you for all of this hard work. This is truly a work of art, after taking a break from the game for a few months, and then "inheriting" Warthog HOTAS, this has been a life saver.

Thanks for all the attention to detail on this, please keep this going!

Aussiedroid · Nov 17, 2018

GravitusMaximus said:
Hey Aussiedroid... first of all, thank you for all of this hard work. This is truly a work of art, after taking a break from the game for a few months, and then "inheriting" Warthog HOTAS, this has been a life saver.

Thanks for all the attention to detail on this, please keep this going!

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

imacken · Nov 17, 2018

Aussiedroid, been away from ED for quite a while and I tried to get your script working again, but can't understand what's going on.
When I run the script, I get this:
Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"Compile Succeeded.
Physical USB HID devices managed by script!
Currently plugged USB HID devices[3]:
1: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
2: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
3: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
Error

internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0404"
Error

internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_0402"
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
Error

internal) cannot associate a filter with the selected USB HID device "VID_044F&PID_B679"
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

Are the errors there important? It's just that when go into ED, not even the throttle and pitch/roll axes are working. I have to rebind, even though the binding looks OK before I do it.
As usual, any help appreciated!

Aussiedroid · Nov 17, 2018

Hey imacken,

Welcome back! The script skipping hardware devices during startup is to be expected, but it should be including the devices you have plugged in. If I am reading the output correctly yours are not.

Do the axes or buttons work in Windows before you start ED?

Do the devices work before you run the script (does windows show the devices working?)?

Is the script still returning main 0 at the end of the startup?

Are you running the latest version of the script?

Have you tried restarting PC, cycling USB ports for your devices etc?

Playing Beta or the Live server?

Cheers, AD

imacken · Nov 17, 2018

Thanks AD,
Everything works fine in other games.
Yes, Windows shows everything working before the script.
Yes, the script is showing 'main returned 0' at the end.
Yep, running the latest 3.2.
No, haven't tried cycling USB ports.
Live server.
As I said, it really weird, as all the button show correctly, but don't actually register on device. I have to go into CONTROLS and re-assing everything to the same buttons, which I don't want to do for everything!
Any further help appreciated.
Cheers, Iain