Release Aussiedroid's Enhanced Thrustmaster Warthog Script

Clicker · Oct 7, 2018

Ok, so for Charge ECM to work properly, you need to modify the script using TARGET Script Editor.

1) Set ShipUtilityPref to "1" ... unfortunately this is the ONLY way this will work until such a time as AD can rewrite his script or move ChargeECM to a different button.
2) In the AD_ED_v3.2.0.tmc script find line 163 and change PULSE+SRVTurret to simply SRVTurret.
Lines 161 to 163 now look like this (minus the comments)...

Code:

	if(ShipUtilityPref == 1) {
		MapKey(&Joystick,  S1,  TEMPO(PULSE+DeployHeatSink, PULSE+FireChaffLauncher, LongPressDelay));
		MapKey(&Joystick,  S2,  TEMPO(PULSE+UseShieldCell, SRVTurret, LongPressDelay)); }

Note: "SRVTurret" and "ChargeECM" share the same keypress...ie LSHIFT+U

Note2: Obviously there will be a short delay before the ECM starts to charge, but then it should work as designed. That is continue to hold it for as long as you need before releasing the button.

Let me know how you get on.

Clicker

p.s. SNAP!!! You beat me to it

kontrolldon · Oct 10, 2018

Issue with MFDs

Ok, I couldn´t help myself and bought some MFDs yesterday. Unfortunately they give me some problem. The scripts just stops automatically after a few seconds.
I now have 14 usb devices connected. NO power saving features and I´m sure my Corsair 1350W PSU can handle it.

I´ve tried just to have one MFD activated (in both the AD_EDSettings_v3.2.0.tmh and physically connected) and of the two MFDs only the one called MFD2 (MFD right) works as a single . No, I didn´t unplug the device.

Here´s what the script does:

*** 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[5]:
1: "T-Rudder" - "USB\VID_044F&PID_B679&REV_0110"
2: "F16 MFD 2" - "USB\VID_044F&PID_B352&REV_0100"
3: "Throttle - HOTAS Warthog" - "USB\VID_044F&PID_0404&REV_0100"
4: "Joystick - HOTAS Warthog" - "USB\VID_044F&PID_0402&REV_0100"
5: "F16 MFD 1" - "USB\VID_044F&PID_B351&REV_0100"
USB HID device "Throttle - HOTAS Warthog"(USB\VID_044F&PID_0404\9&1D41F2F5&0&2) selected
USB HID device "Joystick - HOTAS Warthog"(USB\VID_044F&PID_0402\9&1D41F2F5&0&4) selected
USB HID device with hardware id "VID_044F&PID_0403" cannot be found
USB HID device "F16 MFD 1"(USB\VID_044F&PID_B351\5&1E7D8DB7&0&3) selected
USB HID device "F16 MFD 2"(USB\VID_044F&PID_B352\5&1E7D8DB7&0&6) selected
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 "T-Rudder"(USB\VID_044F&PID_B679\7&22BC2147&0&2) selected
USB HID device with hardware id "VID_044F&PID_B68F" 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: v3.2.0 TARGET Mappings, Macros & Functions Decrypted <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
USER PREFERENCES: Run Software on Start = 0 PIP Preset = 3
Supercruise on Throttle = 0 Cargo Precision Mode = 1 Chaff on Escape = 0
Combine External Mics = 0 Text Chat Preset Mode = 1 Boost on Escape = 0
Custom Slider Curve = 1 Headtrack Center Mode = 2 AUTO Repeater Fire = 0
Ship Utility Mode = 0 MFD Active = 2
DEFAULT TOGGLE STATE: LED Backlight Level = 60
Combine Pri+Sec Fire = 1 Rotational Correction = 1 Cargo Scoop = 0
Landing Gear = 0 Classified Camera Mode = 0 Ship Lights = 0
-----------------------------------------------------------------------------------------------------------------------------------------------
Starting Macros... Trigger 2: Set to COMBINED Primary + Secondary Fire
Rotation Correction: ENABLED ^^
-----------------------------------------------------------------------------------------------------------------------------------------------
Initialising Joystick Axis ... Initialising Throttle Axis ...
Setting Throttle Profile: FULL SCALE [-100 -> 100]
-----------------------------------------------------------------------------------------------------------------------------------------------
Right MFD Configured
Left MFD Configured
Done... Enhanced ED Script Engineered by Aussiedroid is now running... Fly Safe CMDR! <|>
-----------------------------------------------------------------------------------------------------------------------------------------------
main returned 0
Throttle Profile: FORWARD ONLY [0 -> 100]
Error: One of the selected USB devices (2) has been unplugged. Aborting script!
Aborting script (check output above for reason)...
Script stopped!

Reason for the MFDs was that I found Robert Maynards StatusDisplay, so I really don´t need them for my setup but only added them for the immersion.. With a 11.6" screen of course.

Anyone got an idea of whats going on?

Clicker · Oct 11, 2018

Hi kontrolldon,

As MFDs are not really used, nor been tested in the script, and assuming you were not getting the errors before you plugged them in AND this issue is being caused by the MFDs, try commenting out lines 128 and 129 in the AD_ED_v3.2.0.tmc file by putting “//“ at the beginning of each line like this...

Code:

// if(UseMFD > 0) {initRightMFD();}
// if(UseMFD > 1) {initLeftMFD();}

I do not know if this is causing your issue and as I do not have any MFDs, I cannot test this.

Also, you previously mentioned you use a non-thrustmaster joystick and that you don't use pedals.
Is this still the case?

Also, I assume you do not have a Thrustmaster Joystick at all, but if you do it isn't plugged into a USB port right?

Let me know how you get on with the above suggestion.

I'm going to say this right here, right now...the script was written for the Thrustmaster Warthog Throttle & Joystick and I doubt it suits just the throttle by itself very well at all.
(as mentioned the MFDs are not really used at all in the script)

Also, even though you have a monster PSU, it's the motherboard or externally powered USB hubs that determine how well your USBs work.
14 USB devices is a LOT and I do not know many motherboards that can handle that many natively.

I assume therefore you have one or more powered USB hubs?

Out of interest, would you care to list what USB devices you do have connected?

Cheers
Clicker

kontrolldon · Oct 11, 2018

Hi Clicker,

Will try sort it out and do some experimenting.
I bought both a Warthog joy and the TFRP pedals, so all TM now

(joy, throttle, pedals and two MFDs).

I have two Inateck 4 port USB 3.0 PCIe cards and 6 USB ports on my ASUS Prime z370a. Both powered by the PSU.

Following hardware is connected:
1. Oculus Rift (USB 3.0 and HDMI)
2. Rift sensor USB 3.0
3. Rift sensor USB 3.0
4. Rift sensor USB 2.0
5. Logitech G600
6. Logitech G410
7. Logitech C920
8. RODE NT-USB
9. TM TFRP pedals
10. MFD1
11. MFD2
12. USB 3.0 hub (powered)
- 13. TM HOTAS Warthog joy
- 14. TM HOTAS Warthog throttle

I hope that´s all.

I have tried to removing usb peripherals and my issue ain´t there.
Where do you live? I might lend you some MFDs to tinker with.

kontrolldon · Oct 11, 2018

It was a faulty USB port on the MB! Now when the script is working I just have to figure out how to map the MFDs in the AD_ED_v3.2.0.tmc and what to bind my 56 extra buttons to..

When I press the buttons right of now, they are recognized as joy presses.

Will report back when everything is working.

Fly safe cmdrs!

Clicker · Oct 11, 2018

Cool...looks like you may have found the issue.
You may also want to look into USB priorities and/or redundant ghost USB connections as well if you keep having issues.
(Try USBDView via nirsoft.net)

I live in NZ, so feel free to “lend” me th MFDs any time you like!
;-)

The script has the bones of support for the MFDs, but nothing’s been mapped.
Aussiedroid also indicates in the script this is not tested or currently supported.
(Maybe you should send the MFDs to him...he’s in South Australia I believe!)

Clicker

Axsom · Oct 12, 2018

Quick question

First, new Elite gamer here.
My question (I am fixing to extract and read through instructions now). I have the TFRP T.Flight Rudder Pedals, do I need to map yaw with them from in game or add them to the script?
I imagine I am going to have a few more questions as I go, but I'm going to work through the instructions

. I am very glad I was pointed to this thread from Riddit, as the .fcf config that Thrustmaster has from their download resources left me - well let's just say - very disappointed...

Thank you to the original author, and community for continued support

Axsom · Oct 12, 2018

Update...

Axsom said:
First, new Elite gamer here.
My question (I am fixing to extract and read through instructions now). I have the TFRP T.Flight Rudder Pedals, do I need to map yaw with them from in game or add them to the script?
I imagine I am going to have a few more questions as I go, but I'm going to work through the instructions . I am very glad I was pointed to this thread from Riddit, as the .fcf config that Thrustmaster has from their download resources left me - well let's just say - very disappointed...

Thank you to the original author, and community for continued support

Update: I have followed the instructions until it says "Copy the Elite Dangerous Profile to: (Profile is found in the '/ED Profile' folder.)" I can not find the '/ED Profile' folder. I do assume the TrackIR isn't going to apply, being I am playing in VR and won't be using it. So then when I load and do testing I don't see any devices in 'device analyzer' but do get results in the 'Event Tester'. Everything also works in the Control panel. So, I'm not sure that this is working correctly. I would love to get this working.
Any advice?

Clicker · Oct 13, 2018

Axsom said:
First, new Elite gamer here.
My question (I am fixing to extract and read through instructions now). I have the TFRP T.Flight Rudder Pedals, do I need to map yaw with them from in game or add them to the script?
I imagine I am going to have a few more questions as I go, but I'm going to work through the instructions . I am very glad I was pointed to this thread from Riddit, as the .fcf config that Thrustmaster has from their download resources left me - well let's just say - very disappointed...

Thank you to the original author, and community for continued support

G'day and welcome.

I assume you have the Warthog HOTAS as well as the TFRP pedals?

You'll see a user preference setting in the AD_EDSettings file on line 41.
It depends on exactly how you wish to use the pedals as to whether you also need to map these in game.

Clicker

Clicker · Oct 15, 2018

Axsom said:
Update: I have followed the instructions until it says "Copy the Elite Dangerous Profile to: (Profile is found in the '/ED Profile' folder.)" I can not find the '/ED Profile' folder. I do assume the TrackIR isn't going to apply, being I am playing in VR and won't be using it. So then when I load and do testing I don't see any devices in 'device analyzer' but do get results in the 'Event Tester'. Everything also works in the Control panel. So, I'm not sure that this is working correctly. I would love to get this working.
Any advice?

Hi,

Device Analyzer does not work on Windows 10.

If you are talking about where to put the "bind" file then that's usually at C:\users\<username>\AppData\local\frontier developments\elite dangerous\options\bindings
It is possible that this folder may not have been created by the game if you've not customised any bindings.
In this case you can try to customise a binding, in game, then save it (doesn't matter which one)...then go take another look, or...
Create the folder manually on your PC, copy "Aussiedroid Warthog Enhanced 3.2.0.binds" file into your new folder then restart Elite and check if his binding file is now available in game.

Hope this helps.

Clicker

feiercrack · Oct 15, 2018

Hello Friends,

today, after some months offline, i´ll start to play ED again ;-)

Jeesus, so many things have changed.. My Astra wont talk to me again, and so on pp etc...

Now, i had configured this awesome new script! Thanxx again for this masterwork!

BUT: i cant deal with that : --> 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.

Where the heck can i find the "outlined" -other Mappings- in which " Legend" section??? is that ingame? or in a specific file???

Thanks

and:

i dont own those MFG Rudders, BUT i do own SIMPED F16/C Rudders, with Toebrakes via the famous R.U.S.B.A. USB Adaptor. If i like to use them, what to do?

Thanks

cheers and greetings to mr. solaris

o7

Axsom · Oct 15, 2018

Hello,

feiercrack said:
Hello Friends,

today, after some Months offline, i´ll start to play ED again ;-)

Jeesus, so many things have changed.. My Astra wont talk to me again, and so on pp etc...

Now, i had configured this awesome new script!

BUT: i cant deal with that : --> 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.

Where the heck can i find the "outlined" -other Mappings- in which " Legend" section??? is that ingame? or in a specific file???

Thanks

and:

i dont own those MFG Rudders, BUT i do own SIMPED F16/C Rudders, with Toebrakes via the famous R.U.S.B.A. USB Adaptor. If i like to use them, what to do?

Thanks

cheers and greetings to mr. solaris o7

I have just done the setup over the weekend and had the same question. I use the TFRP T.Flight Rudder Pedals, and think I've done it correctly. You may want to wait for a more advanced user to answer. I MAPPED mine in game and are working correctly, including the Map YAW. I didn't mess with the PITCH, figured I would later after I get more confrontable.

Clicker · Oct 16, 2018

feiercrack said:
Hello Friends,

today, after some months offline, i´ll start to play ED again ;-)

Jeesus, so many things have changed.. My Astra wont talk to me again, and so on pp etc...

Now, i had configured this awesome new script! Thanxx again for this masterwork!

BUT: i cant deal with that : --> 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.

Where the heck can i find the "outlined" -other Mappings- in which " Legend" section??? is that ingame? or in a specific file???

Thanks

and:

i dont own those MFG Rudders, BUT i do own SIMPED F16/C Rudders, with Toebrakes via the famous R.U.S.B.A. USB Adaptor. If i like to use them, what to do?

Thanks

cheers and greetings to mr. solaris o7

Welcome back!

The legend and mappings referred to are on Aussiedroid’s post on steam (link at top of post #1 of this thread)
The mappings referred to are mostly to do with 3rd party pedal functionality, such as yours.

Here’s a link to the legend...
https://steamuserimages-a.akamaihd.net/ugc/918042004704782536/EA3EA7FB4397AF2FCB4582A0DFC42B548DDCFC37/

So, you can use your rudder pedals. Use the “Without MFG...” bind file included in the download and just need to bind your rudders to the axis you want to use them for, within Elite Dangerous as far as I know.

Hope this helps,
Clicker

Mettius · Oct 18, 2018

I just hooked up the new Thrustmaster TPR rudder pedals and unfortunately the virtual controller created by the scripts don't include it, so they are masked from ED, and hence I can't map them to control bindings.

I had a quick look and I see in the Target.tmh and of course there is not an alias for the TPR. Was about to sift through the code and see if I can figure out how to add it. But was rather hoping to play ED tonight instead.

Anyone already have a fix?

Mettius · Oct 18, 2018

OK, I don't think that is actually the problem. The rabbit hole is getting deeper.

Still don't have it working though.

Clicker · Oct 18, 2018

Mettius said:
I just hooked up the new Thrustmaster TPR rudder pedals and unfortunately the virtual controller created by the scripts don't include it, so they are masked from ED, and hence I can't map them to control bindings.

I had a quick look and I see in the Target.tmh and of course there is not an alias for the TPR. Was about to sift through the code and see if I can figure out how to add it. But was rather hoping to play ED tonight instead. Anyone already have a fix?

Ahhhh...these are new in the new version of TARGET, "TARGET_v3018(328v2)", so you need to grab that from the thrustmaster site and install.
Alas, these are yet to be included in Aussiedroid's script.

You might look at adding the following to the main script file...

Code:

  		Configure(&TFRPHARudder, MODE_EXCLUDED);

...with the other "Configure..." lines, then mapping the pedals YAW directly in ED.

This might get you going until such a time as this can be added and tested.

Hope this helps.

Clicker

Perseus · Oct 18, 2018

I've recently bought the Warthog stick, T16000m and TFRP rudder pedals. The devices worked without tweaks after I set up ED profile in the game but I found nearly all the devices sensitive.
I did a basic GUI script but when I tried to set the profile in game, I found that the axis of the Warthog (x and y) matched the same on the T16000. I need the T16000 to do yaw (which it does in the script) and lateral/vertical thrust.
How do I give the two sticks different identities in GUI in terms of axis?

Clicker · Oct 18, 2018

Perseus said:
I've recently bought the Warthog stick, T16000m and TFRP rudder pedals. The devices worked without tweaks after I set up ED profile in the game but I found nearly all the devices sensitive.
I did a basic GUI script but when I tried to set the profile in game, I found that the axis of the Warthog (x and y) matched the same on the T16000. I need the T16000 to do yaw (which it does in the script) and lateral/vertical thrust.
How do I give the two sticks different identities in GUI in terms of axis?

G'day,

Assuming both are connected to a USB port when you start the TARGET GUI app, can you select them both to be included as a combined controller?
If so, you should be able to build a profile that will suit you by ensuring the DX-Axis defined for each stick are different.
(ie DX_Y_AXIS v DX_XROT_AXIS etc)

If the app won't let you include both joysticks in the one profile, that's a sure sign they're not supported in that configuration.

I have a feeling, it should work as I've read somewhere that people use 2 joystick setups but have no idea if they were using TARGET to combine them into a single entity.

Let us know how you get on.

Clicker

Perseus · Oct 18, 2018

Clicker said:
G'day,

Assuming both are connected to a USB port when you start the TARGET GUI app, can you select them both to be included as a combined controller?
If so, you should be able to build a profile that will suit you by ensuring the DX-Axis defined for each stick are different.
(ie DX_Y_AXIS v DX_XROT_AXIS etc)

If the app won't let you include both joysticks in the one profile, that's a sure sign they're not supported in that configuration.

I have a feeling, it should work as I've read somewhere that people use 2 joystick setups but have no idea if they were using TARGET to combine them into a single entity.

Let us know how you get on.

Clicker

Cheers!
I'll give that a go and post back.

Perseus · Oct 18, 2018

It worked, no problem!
I also managed to get the buttons on the two sticks separated.
Thanks again.