Release Aussiedroid's Enhanced Thrustmaster Warthog Script

Clicker · Sep 30, 2018

Mettius said:
The readme states:

First Run: If you are not using MFG Crosswind Pedals, at this point, you will need to map the 'Other Mappings' outlined in the Legend Section. This will configure Roll & some Galaxy Map axes (along with some optional custom configurations highlighed you may like).

For the life of me I'm not finding an Other Mappings section in any of the macro files. Where do I configure this?

I think Aussiedroid is referring to his image...https://steamuserimages-a.akamaihd.net/ugc/918042004704782536/EA3EA7FB4397AF2FCB4582A0DFC42B548DDCFC37/

It references other mappings which you may need to bind within ED if you wish to use them.

Clicker

Clicker · Sep 30, 2018

Hi Sarge,

Very strange issues indeed.

Can I suggest you try different USB ports?
Maybe unplug anything else you have in USB that you don't need for the game (just to test)?

There's an app which I think was mentioned in a much earlier post in this thread which checks all the USB resources in use...you might like to try that?

Have you tried compiling and running the script via the TARGET Script editor and using the Event tester to see what outputs you get when you use the buttons required for the functions you're having issues with?
(hint: you should see no output when using the mic switch for lateral thrusters)

Clicker

Sarge788 · Sep 30, 2018

Hi Clicker,

When I used the Target Device Analyser and noticed that when moved any of the to switches in any direction. Multiple events light up i.e 5, 6 19 29 and 30 at tthe same time when i move the coolie up which is Thrusters up in the script.

Did see this when I closed the game

https://drive.google.com/open?id=1eEu7zGqxyjZMLVu527HEdt5rJcLdZ6Iu

It seems to be switching profiles

thanks for trying to help

Sarge

Clicker · Oct 1, 2018

You get numbers in the Device Analyzer?
Very strange.

Those messages in your image are typically when you switch joystick curve profiles.
I think from memory these are triggered by the “AutoPilot” switch on the throttle base (APPAT, APAH, APALT).

...and you are saying you get this output when pressing the MIC thumb button on the throttle arm?

Clicker

P.s. when I get home tonight, I’ll load up Ausiiedroids 3.2.0 script and binds and test on my system and let you know.

Clicker · Oct 1, 2018

Scrub the above, those console message are generated when you switch FA-OFF on and off via the Speed Brake switch.
(which is the switch immediately under the MIC thumb switch on the throttle arm).

And, I mistook "Device Analyzer" for "Event Tester" in your reply.
You should see no output in "EVENT TESTER" when using the coolie switch or MIC switch...if you are seeing keypresses, then something is not right.

I cannot comment on "Device Analyzer" as I can't get that working on Windows 10.

I've tested Aussiedroids script and binds (3.2.0) on my PC (Windows 10) and unfortunately Sarge, everything works perfectly.

I do wonder if your Throttle or USB connection is borked.
Can you try a different USB port? Are you using a USB 2.0 or 3.0 port?
Are you using a USB hub at all? Is it powered or unpowered?

Clicker

Sarge788 · Oct 2, 2018

Hi Clicker,

This is slowly driving me insane

I have been using Aussiesdroid's profile for ages and never had any problems until just over a weekend ago.

I have changed the USB port for the throttle and before I started up Target I tested it by using:
Press Window key and "R" and Ran Joy.cpl, selected Warthog Throttle, pressed Properties. I then tested all buttons, slider and throttle axis and anything worked fine. So this rules out a problem with the USB port and my throttle.

When I run Aussiesdroid's profile that's when the problems start. Key bindings not been mapped or changed.

I was doing some exploration so I never toggle flight assist.

I check Elite bindings folder this morning and there is another binds file named "Aussiedroid Warthog Enhanced 3.2.0.3.0.binds" I have not changed anything.

I also noticed that there is a Bindingsloadingerrors file which has the following:

There where errors when loading preset file: Aussiedroid Warthog Enhanced 3.2.0.3.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Aussiedroid Warthog Enhanced 3.2.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.1.8.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.2.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.3.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Noidea.binds
Missing devices: ThrustMasterWarthogCombined

This is what see when the profile is running:

https://drive.google.com/open?id=1kXxYEhFj9Vm4vNeBcxNDMxgeIKHv7JXj

I will resorting to self harm soon ;-)

Sarge

kontrolldon · Oct 2, 2018

Got an error. When deploying the cargo scoop, LED light (2nd one from the bottom) lights up. BUT when retracting Cargo Scoop the LED doesn´t turn off and get stuck on. I have to stop the script to get it off. Any one got any idea?

Clicker · Oct 3, 2018

Bigdave788 said:
Hi Clicker,

This is slowly driving me insane

I have been using Aussiesdroid's profile for ages and never had any problems until just over a weekend ago.

I have changed the USB port for the throttle and before I started up Target I tested it by using:
Press Window key and "R" and Ran Joy.cpl, selected Warthog Throttle, pressed Properties. I then tested all buttons, slider and throttle axis and anything worked fine. So this rules out a problem with the USB port and my throttle.

When I run Aussiesdroid's profile that's when the problems start. Key bindings not been mapped or changed.

I was doing some exploration so I never toggle flight assist.

I check Elite bindings folder this morning and there is another binds file named "Aussiedroid Warthog Enhanced 3.2.0.3.0.binds" I have not changed anything.

I also noticed that there is a Bindingsloadingerrors file which has the following:

There where errors when loading preset file: Aussiedroid Warthog Enhanced 3.2.0.3.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Aussiedroid Warthog Enhanced 3.2.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.1.8.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.2.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Custom.3.0.binds
Missing devices: ThrustMasterWarthogCombined

There where errors when loading preset file: Noidea.binds
Missing devices: ThrustMasterWarthogCombined

This is what see when the profile is running:

https://drive.google.com/open?id=1kXxYEhFj9Vm4vNeBcxNDMxgeIKHv7JXj

I will resorting to self harm soon ;-)

Sarge

Ok...so what is happening is this...when you run the TARGET script, it converts the discrete 2 USB connected devices (throttle, joystick) into one combined virtual USB device (“ThrustmasterWarthogCombined”).

As these are defined within the binds file by name, when ED starts, if this has not been created by Windows properly, ED will create the error file and revert to another binds file within the binds file folder. In fact ANY error at all in the bind file when ED loads will do this.

In other words;
A) Combined joystick probably not being created in windows...this is either a TARGET/driver issue or an issue in windows.
B) Ed defaulting to a known good, or empty/default bind file when loading.

Your joystick will then not work properly in game.

Joy.cpl works fine before you run the script...does it work after the script is running and displays choice of ThurstmasterWarthogCombined?

After you load ED, check which bind is active...is it still AusieDroids? Probably not...probably showing "Thrustmaster Warthog" <-- not Aussiedroid's script.

I’m going to suggest something you may have already done...remove the throttle and joystick from the USB ports, remove target completely including the drivers...delete any leftover files in the install directory, clean the registry using something like ccleaner then reinstall from scratch.

Clicker

p.s. I hope this helps.

Clicker · Oct 3, 2018

kontrolldon said:
Got an error. When deploying the cargo scoop, LED light (2nd one from the bottom) lights up. BUT when retracting Cargo Scoop the LED doesn´t turn off and get stuck on. I have to stop the script to get it off. Any one got any idea?

Hi kontrolldon,

Can I assume you get the ingame message telling you that cargo scoop has been retracted and the cargo scoop light on your hud (ingame) goes off?

That is just the LED on the throttle base stays on?

Can you confirm you are deploying/retracting via the throttle RDRNRM/RDRDIS switch and not pressing “home” key on keyboard?

Thanks
Clicker

p.s. I’ll test this out myself when I get home from work this evening to make sure it is working as Aussiedroid intended.

kontrolldon · Oct 3, 2018

Clicker said:
Hi kontrolldon,

Can I assume you get the ingame message telling you that cargo scoop has been retracted and the cargo scoop light on your hud (ingame) goes off?

That is just the LED on the throttle base stays on?

Can you confirm you are deploying/retracting via the throttle RDRNRM/RDRDIS switch and not pressing “home” key on keyboard?

Thanks
Clicker

p.s. I’ll test this out myself when I get home from work this evening to make sure it is working as Aussiedroid intended.

Hi Clicker and thanks for the swift response.

Yes, ingame everything is fine. I use the RDRNRM (2 on/off switch from the left) in position down (as off). No "home" keypresses.

The base LED just gets stuck.. It´s a minor glitch but everything else works soo good, so it´s annoying.

Other useful information.
- I use Aussiedroid-ED-Warthog-Script-3.2.0
- Firmware on throttle is 23
- I have a VBKsim Gladiator joystick, no pedals and no MFDs.
- No errors on script launch.

Clicker · Oct 3, 2018

kontrolldon said:
Hi Clicker and thanks for the swift response.

Yes, ingame everything is fine. I use the RDRNRM (2 on/off switch from the left) in position down (as off). No "home" keypresses.

The base LED just gets stuck.. It´s a minor glitch but everything else works soo good, so it´s annoying.

Other useful information.
- I use Aussiedroid-ED-Warthog-Script-3.2.0
- Firmware on throttle is 23
- I have a VBKsim Gladiator joystick, no pedals and no MFDs.
- No errors on script launch.

Hi...yeah I just had a quick look at the code and I think I might know where the issue is.

Let me test this tonight when I get home and I’ll let you know how to fix it.

I assume the joystick you are using “looks like” the Thrustmaster one to TARGET?
Ie direct replica of buttons/switches axes etc?

Cheers
Clicker

kontrolldon · Oct 3, 2018

Clicker said:
I assume the joystick you are using “looks like” the Thrustmaster one to TARGET?
Ie direct replica of buttons/switches axes etc?

Clicker

Here´s a link to the joystick: https://vkbcontrollers.com/?product=vkb-sim-gladiator
Got that one because it got a yaw axis.

I have remapped (in ED) some of the buttons on the joystick to my own preference but NOT the ones on the throttle. None of the buttons remapped has anything to do with the issue of the Cargo Light that gets stuck. It also happens even if I haven´t launched the game. So it´s something in the code.

One off topic question: define KBLayout. I got a swedish keyboard but it doesn´t seem to be an option to change to KB_SV (or any other abbreviations except ENG and GER)

Clicker · Oct 3, 2018

Ok...found it.

This is a bug in the code.
It was also in the previous version (3.1.0) and obviously no-one noticed.

If you are comfortable using the TARGET script editor,
1) open AD_EDFunctions_v3.2.0.tmh
2) go to line 611 and add a } to the end of the line
3) go to line 612 and remove one of the } from the end of that line
4) save the file

The code should now look like this...

Code:

611	     DeferCall(5050, &ActKey, KEYON+PULSE+EXEC("printf(\"Cargo Scoop: RETRACTED <<\\x0a\");")); } }
612   ActKey(KEYON+PULSE+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); } } 			// set LED 4 OFF

You can test this by opening AD_ED_v3.2.0.tmc file, press "compile", then press "run", then use the cargo scoop switch (RDRNRM).
The LED should now turn on and off as intended.

Clicker

kontrolldon · Oct 3, 2018

That was quick! Thanks soo much Clicker. It works as it should now.
Now that I got your attention, if you know what abbreviation to use to change define KBLayout, it would be great. Tried google it and the common KB_SV does not work, script reports an error on that line if I change it.
Don´t think it´s a big deal, but it will make life easier when not having remap keys that ain´t valid on my keyboard. (it´s a Logitech G410 with Swedish layout)

Thanks a lot and fly safe cmdr!

Clicker · Oct 3, 2018

kontrolldon said:
That was quick! Thanks soo much Clicker. It works as it should now.
Now that I got your attention, if you know what abbreviation to use to change define KBLayout, it would be great. Tried google it and the common KB_SV does not work, script reports an error on that line if I change it.
Don´t think it´s a big deal, but it will make life easier when not having remap keys that ain´t valid on my keyboard. (it´s a Logitech G410 with Swedish layout)

Thanks a lot and fly safe cmdr!

No clue at all sorry!

Maybe open a ticket with Thrustmaster Support and ask what keyboards are supported?

Maybe try checking out one of the flight sim forums such as DCS (https://forums.eagle.ru) where the Thrustmaster Warthog is pretty popular.

Clicker

EDIT: I just had a search in target.tmh and it only shows support for 3x keyboards...ENG, GER and FR, so I'd take a guess and say the Swedish layout is not supported.

Sarge788 · Oct 5, 2018

Hi Clicker,

as if by magic my whole issues have disappeared without doing anything. So must have been a problem between windows and Target.

Thanks for all of your help.

Sarge

Clicker · Oct 6, 2018

Bigdave788 said:
Hi Clicker,

as if by magic my whole issues have disappeared without doing anything. So must have been a problem between windows and Target.

Thanks for all of your help.

Sarge

Well, I’m glad it’s working, however, I did nothing!

Hope it doesn’t come back.

Clicker

Mettius · Oct 6, 2018

Long Press for ECM not "holding down".

I set ShipUtilityPref to "1" from "0". And no change of the behavior. That being that when I activate the ECM module it doesn't "hold" as long as I hold down the button. This doesn't really work with the way ECM works. That is, it should "charge" for as long as I hold the button until I release.

I'm assuming this is a problem for everyone?

Clicker · Oct 7, 2018

Mettius said:
I set ShipUtilityPref to "1" from "0". And no change of the behavior. That being that when I activate the ECM module it doesn't "hold" as long as I hold down the button. This doesn't really work with the way ECM works. That is, it should "charge" for as long as I hold the button until I release.

I'm assuming this is a problem for everyone?

Hi Mettius,

I just took a quick look at the script.
ShipUtilityPref just swaps between short or long press to fire the ECM (and other functions)

Having said that, I think you may be correct in that you should be press and hold for ECM to work, and not a simple press/release.
In other words you may have found a bug in the script.

I will see if there is a simple fix and re-post here.
If the fix isn't simple we may need to wait for Aussiedroid to come back on line.

Stay tuned.

Clicker

Mettius · Oct 7, 2018

I think I fixed it.

Code:

[COLOR=#32cd32]//MapKey(&Joystick,  S2,  TEMPO(PULSE+UseShieldCell, PULSE+SRVTurret, LongPressDelay)); }                        // Weapon Release         [Short: Shield Cell,     Long: ECM/SRV Turret][/COLOR]
        MapKey(&Joystick,  S2,  TEMPO[COLOR=#ffffff]([/COLOR]PULSE[COLOR=#ffffff]+[/COLOR]UseShieldCell, SRVTurret, LongPressDelay)); }

Commented out line is the original code.
2nd line is what I modified. I just removed the "PULSE+" command. Prelimary test is that it is now working the way I was hoping for.

Line 163 of AD_ED_v3.2.0 BTW.