Release Aussiedroid's Enhanced Thrustmaster Warthog Script

[Clicker]

CMDR Clicker a few comments back hit the same issue, and found, IIRC, starting up Event Viewer or Device Analyzer before running the script seemed to fix it. Believe he also has a trouble ticket with TM for it. System restart/unplug/reinitialise etc may be worth a try too. Not really sure what causes it

To be clear, running the event tester doesn't fix the issue. I use it to test if both the joystick and throttle have combined properly and working.
To do this I test a button on each that I know fires a key. If the key doesn't show up in the tester I cycle the power on my powered USB hub that the HOTAS is connected to.
This usually does the trick.
If it doesn't, then I recompile the script and try again...this also usually does the trick.
If it doesn't, I reboot the PC....this also does the trick if the previous two options do not work.

Yes, it still happens to me occasionally, maybe once per fortnight.

Thrustmaster support basically gave up after I followed their instructions...which was limited to "uninstall the drivers and target, make sure you have the latest firmware installed, re-install as per the instructions...to the letter".
Which, of course I did.

So, now I just live with it...it's annoying...but, hey, what can I do?
(and don't say fresh install of Windows, coz I aint going there anytime soon)

Clicker

 

[imski]

OK, so I've finally had a chance to download this but I'm getting this error:

Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Script stopped!

Runtime Error: Symbol not found: TFRPHARudder in main ( line 73 in AD_ED_v3.3.0.tmc )

Can I just go ahead and delete the section referring to the TFRPHARudder in the tmc file?

(I have the cheaper TM pedals)

 

[Jezzer]

Many thanks for the latest update.

J

 

[Aussiedroid]

OK, so I've finally had a chance to download this but I'm getting this error:

Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"
Script stopped!

Runtime Error: Symbol not found: TFRPHARudder in main ( line 73 in AD_ED_v3.3.0.tmc )

Can I just go ahead and delete the section referring to the TFRPHARudder in the tmc file?

(I have the cheaper TM pedals)

Sounds like someone didn't ready the instructions

You need to be running the latest TARGET/Drivers/Firmware for the new script to run.

Thanks, AD

Many thanks for the latest update.

J

My pleasure Jezzer, hope you like the improvements!

Cheers, AD

 

[cmdr awesome]

Hi Aussidroid - great script!

You may want to add this to the startup batch file - I find it useful anyway:
ECHO LAUNCHING MAPPINGS HELP
rundll32 "C:\Program Files\Windows Photo Viewer\PhotoViewer.dll" , ImageView_Fullscreen C:\Aussiedroid-ED-Warthog-Script-3.3.0\Maps\Advanced-Map.jpg

 

[imski]

You’re right, I’m just so used to everything you put up working I’ve become complacent!

Thanks

 

[ptimale]

Hello

google translation

Hello, I am French and I try to use your Target script

I have a warthog + joystick and TPR Rudder

My first question:
1) Is it normal that when the script is executed, that in device analyzer, only the Rudder TPR is near?
In the Windows game controller I have Thrustmaster Combined and TPR T.Pendular Rudder.
3) I do not understand how to use the "Vol-Miscellaneous" functions (Turbo, FSD, Super-navigation, hyperspace jump)
I do not understand the Pinky Switch function on the Throtle

Thanks for getting great work

A Fan lol

 

[Aussiedroid]

Happy Holidays & New Year All!

Hi Aussidroid - great script!

You may want to add this to the startup batch file - I find it useful anyway:
ECHO LAUNCHING MAPPINGS HELP
rundll32 "C:\Program Files\Windows Photo Viewer\PhotoViewer.dll" , ImageView_Fullscreen C:\Aussiedroid-ED-Warthog-Script-3.3.0\Maps\Advanced-Map.jpg

Thanks mate! .. and thanks for the suggestion. Just tried that out and is very cool. I don't know a lot about batch files and didn't know you could do the above. I'll look to include this in the next version. Others may find this helpful too!

You’re right, I’m just so used to everything you put up working I’ve become complacent!

Thanks

All good, glad its all working mate!

Hello

google translation

Hello, I am French and I try to use your Target script

I have a warthog + joystick and TPR Rudder

My first question:
1) Is it normal that when the script is executed, that in device analyzer, only the Rudder TPR is near?
In the Windows game controller I have Thrustmaster Combined and TPR T.Pendular Rudder.
3) I do not understand how to use the "Vol-Miscellaneous" functions (Turbo, FSD, Super-navigation, hyperspace jump)
I do not understand the Pinky Switch function on the Throtle

Thanks for getting great work

A Fan lol

Hi ptimale,

Thank you!

1) Can I ask if the controllers are working for you in that configuration? When the script runs, it should 'combine' the Joystick and Throttle into a single virtual device. I do not own the Thrustmaster Pedals to test, but I believe these remain a separate device, but can be mapped in Elite Dangerous (I may be wrong though).

There are some user preferences for the Pedals, specifically for the T.Pendular Rudders:

define UseRuddersTPR 1

This should remain as '1' if you wish to combine the toe pedals into a single axis, which is useful for using in Elite Dangerous. Else, if it is '0' it will remove the axis manipulation in the script and run as a default device.

2) Regarding the Pinky Switch / Trigger function, this is the Modifier button on the Joystick. Modifiers are basically a combination of two buttons to allow another mapping on the same button, trigger or toggle. To activate a function such as the FSD, you will need to firstly hold down the Pinky Trigger, then while you are holding down the Pinky Trigger, move the throttle to the full position. The script will then activate the function.

Modifiers are used heavily in the script to allow mapping of all functions/actions. Once you get it to work a few times, hopefully it will start to make more sense.

To practice, I normally recommend to try using the Modifier 2 (CMS Hat Switch Button) and try to activate your ship user interface panels using the Microphone Hat Switch directions on the Throttle. You will see if you only press the Microphone Hat Switch while docked it will do nothing. If you Hold the CMS Hat Switch button, then press a direction it will display the user interface panel such as Systems, Comms, Nav panels. Press again to exit or use Modifier 1 (Pinky Trigger) + Modifier 2 (CMS Hat Switch) to exit.


Cheers, AD

 

[ptimale]

Hello, Aussiedroid

I confirm a foix the script target executer I have the joystick and the throttle combined and the TPR alone









I am under windows 10 x64 1809

Thank you for doing tests I understood how to use the button "edit"

Thanks again for this great script

 

[Darkfyre99]

Thank you once again for updating your awesome script. [hotas] [smile][up]

 

[Aussiedroid]

Thank you once again for updating your awesome script. [hotas] [smile][up]

Thanks a lot! Hope you are liking the upgrades

 

[Darkfyre99]

Thanks a lot! Hope you are liking the upgrades

Unfortunately, when I finally had a chance to run it, after making the necessary setting changes and copying over my message macros, I'm getting this error:

Mapped plugin module "C:\Program Files (x86)\Thrustmaster\TARGET\Plugins\sys.dll"Script stopped!


Runtime Error: Symbol not found: TFRPHARudder in main ( line 73 in AD_ED_v3.3.0.tmc )

Which is this line right here:

        if(UseRuddersTPR == 1)      Configure(&TFRPHARudder, MODE_FILTERED);    // Enables Differential Toe Brakes on T.Flight TPR Pedals (for mapping through Target Script)Configure(&TFRPHARudder, MODE_FILTERED);

The equivalent line of code in the last script I was using is:

        if(UseRudders == 1) Configure(&TFRPRudder, MODE_FILTERED);        // Enables Differential Toe Brakes on T.Flight Rudders (for mapping through Target Script)

I have the T.Flight Rudder Pedals. I tried disabling both rudder settings completely through setup, but I get the same error message, only on line 72. I'm tempted to comment these two lines out, but I looked at your other files, and that particular symbol is everywhere, so I have a feeling I'd break more things if I did that.

My knowledge of Thrustmaster's scripting language is extremely rudimentary, which is something I really should fix one of these days, so I can start adding to and/or tweaking elements of your awesome script to better suit my particular needs. (Curse you limited time!) Any help would be great.

 

[Darkfyre99]

I got it working!!!

Naturally, it was something incredibly basic. I needed the latest version of the target.tmh file. Reinstalled the target software, and I'm good to go. [up]

 

[Aussiedroid]

I got it working!!!

Naturally, it was something incredibly basic. I needed the latest version of the target.tmh file. Reinstalled the target software, and I'm good to go. [up]

Cool! Yeah it requires the latest version to support the new TM Pedals. I think there was a firmware update for the Joystick too if you have an older version it may be worthwhile updating that too.

Enjoy, AD

 

[logimen]

Hello,

I appreciate time you spend on making this script.

I tried to use it with my Hotas Warthog but I came into few problems and have a questions.

1. I bought Thrustmaster T.RJ12 adapter and I want to use T3PA pedals from Thrustmaster's T300GTE Racing Wheel. Do I must to check t in script as TDRP enabled or maybe dont change this or even something else ?

2. When using script I cant manually rebing keys in ED. Everytime I change key maps, click "Apply" and exit controls menu they back to its previous state. Is there any mechanism which prevents from changing these ?

3. Generally I think script is nice work, no doubt, but its a little complicated to configure for newbies in ED like me Because Im not newbie in terms of computers, software etc.
Its my opinion only but would be nice to see a GUI for configuration like assigning text chat presets to selected POW Switch, select functions like pri-sec fire combined or not etc

 

[Aussiedroid]

Hi There Logimen,

Hello,

I appreciate time you spend on making this script.

I tried to use it with my Hotas Warthog but I came into few problems and have a questions.

Cheers for the kind comment, and appreciate your feedback. Always happy to help if I can.

1. I bought Thrustmaster T.RJ12 adapter and I want to use T3PA pedals from Thrustmaster's T300GTE Racing Wheel. Do I must to check t in script as TDRP enabled or maybe dont change this or even something else ?

That is a cool idea, never considered racing pedals as an alternative! I suspect that the T3PA pedals would have different axis definitions that are needed in the script. Given the two pedals (T16000/TDRP & TPR) currently supported required different identifiers too. At a high level, the code for this should be the same (this is mainly the code in the Event Handler at the end of the main script file plus a little code to align with user preferences selections) but would need to align to the T3PA pedals specifically.

I am happy to add this code in a future release, but would need some assistance to determine what these definitions should be & to test. Previous code that has been added was supplied by other users who verified it works their end since I do not own any of the hardware to try myself. Unfortunately it makes it a bit hard for me to figure out & ensure its working as you can appreciate.

The code included by the way only does one thing, which is combines the toe pedal axis into a single axis for mapping in ED. Depending on what you want to map you may be able to just map it direct into ED without any coding.

2. When using script I cant manually rebing keys in ED. Everytime I change key maps, click "Apply" and exit controls menu they back to its previous state. Is there any mechanism which prevents from changing these ?

There is nothing in the binding or script files that should be preventing you from changing/saving/applying the mappings. I suspect this may be a bug, as I have seen several posts such as this one around during beta and live build where users were experiencing the same issue. I assume as Frontier went on holidays after the release that it may not have been patched out yet. I would check you have admin access to the bindings folder, and file is not read-only (shouldn't be), try copying out all other binds in case of conflicts etc, but otherwise may need Frontier to address?

You may be able to manually edit the binding file in a text editor and save it manually before loading ED. I've done that to get around some enforced restrictions before.

Technically you could change any mapping you like, but bear in mind most of the functions and mappings are managed within the script. This will mean you will need to align the script as well as the mapping in ED. There are some hat switches for example that are separate from the script though, and those can be changed without any other modification. Likewise axis mappings should be fine to change.

If you can outline what you are trying to change, I can take a look and see if its viable (or easy at least ) or if it may need more coding changes in the script too.

3. Generally I think script is nice work, no doubt, but its a little complicated to configure for newbies in ED like me Because Im not newbie in terms of computers, software etc.
Its my opinion only but would be nice to see a GUI for configuration like assigning text chat presets to selected POW Switch, select functions like pri-sec fire combined or not etc

Oh yeah totally agree! I think I have put as much time into creating the reference maps (learning Photoshop etc) and Steam Guide to help explain it as much as possible as I have coding the script LOL. Also added a beginners map too to try to ease the learning curve in the last release, but I am not sure what else I can do tbh. Doesn't help that the game has so many binds either.

Text chat presets are easy to change but very time consuming unfortunately. Hopefully you will find once you setup your preferred user preferences to your liking you will not need to change them very often. Again, just a bit of a learning curve Generally a few hours in the cockpit should have most of the essential controls down, and from there you can expand to learn more of the advanced controls.

I would love to add a GUI or something but honestly do not know where to start. I don't think it can be done via the Target Script.

Cheers, AD

 

[logimen]

Hi There Logimen,



Cheers for the kind comment, and appreciate your feedback. Always happy to help if I can.



That is a cool idea, never considered racing pedals as an alternative! I suspect that the T3PA pedals would have different axis definitions that are needed in the script. Given the two pedals (T16000/TDRP & TPR) currently supported required different identifiers too. At a high level, the code for this should be the same (this is mainly the code in the Event Handler at the end of the main script file plus a little code to align with user preferences selections) but would need to align to the T3PA pedals specifically.

I am happy to add this code in a future release, but would need some assistance to determine what these definitions should be & to test. Previous code that has been added was supplied by other users who verified it works their end since I do not own any of the hardware to try myself. Unfortunately it makes it a bit hard for me to figure out & ensure its working as you can appreciate.

The code included by the way only does one thing, which is combines the toe pedal axis into a single axis for mapping in ED. Depending on what you want to map you may be able to just map it direct into ED without any coding.

Yeah, as you said T3PA pedals have three different axles and needs to combine two of them (clutch and gas will be best) into one. It will be no problem if TM wants to add this funcion in his driver but we know they will not do this because of they ecosystem.

I can try to provide you neccesary informations if you want to add this pedals in script but also if you can, please make a little script just for combining pedal axles and nothing more
At this moment I dont use this script because Im new to my hotas warthog and there is plenty of buttons and macros to learn. Too much for me, specially when I want to play after work and dont have time to mess with all this stuff
Will try later.

There is nothing in the binding or script files that should be preventing you from changing/saving/applying the mappings. I suspect this may be a bug, as I have seen several posts such as this one around during beta and live build where users were experiencing the same issue. I assume as Frontier went on holidays after the release that it may not have been patched out yet. I would check you have admin access to the bindings folder, and file is not read-only (shouldn't be), try copying out all other binds in case of conflicts etc, but otherwise may need Frontier to address?

You may be able to manually edit the binding file in a text editor and save it manually before loading ED. I've done that to get around some enforced restrictions before.

Technically you could change any mapping you like, but bear in mind most of the functions and mappings are managed within the script. This will mean you will need to align the script as well as the mapping in ED. There are some hat switches for example that are separate from the script though, and those can be changed without any other modification. Likewise axis mappings should be fine to change.

If you can outline what you are trying to change, I can take a look and see if its viable (or easy at least ) or if it may need more coding changes in the script too.

So this must be a bug like you said. I checked but my bindings file is not in read only mode and I have administrator access to ED folder.


One more time, thanks for your time and nice work.

Sorry for my english.

 

[Aussiedroid]

Hi logimen,

It may be that the wheel and pedals are not supported through TARGET if you have different software loaded with the device, I am not sure, you may need to check with TM on what is needed to included in a script file.

Its time consuming & difficult to create a test script just for this, as I said, I cannot test this at all. You should be able to modify the existing script fairly easily though, for testing you can replace the TPR pedal code as needed. Would need to change the parts underlined below. The parts you should need to change are:

Around Line 73 in AD_ED_v3.3.0.tmc, to match your device identifier:

        [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]UseRuddersTPR == [COLOR=#ffffff]1[/COLOR])      Configure([U]&TFRPHARudder[/U], MODE_FILTERED);

Around Line 532 in AD_ED_v3.3.0.tmc, to match your device identifier:

        [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]UseRuddersTPR == [COLOR=#ffffff]1[/COLOR]) { 
            [COLOR=#1e90ff][B]if[/B][/COLOR] (&o == [U]&TFRPHARudder[/U]) {
                GetAxisData(&o, x);   
                [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]x == [U]TFRPHA_LEFT[/U] | x == [U]TFRPHA_RIGHT[/U]) {
                    axdata[COLOR=#ffffff].[/COLOR]locked = [COLOR=#ffffff]1[/COLOR];  
                    Differential_Toe = -[U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_RIGHT[/U]]/[COLOR=#ffffff]2[/COLOR] + [U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_LEFT[/U]]/[COLOR=#ffffff]2[/COLOR];
                    GameOutput(&o, [U]TFRPHA_RIGHT[/U], AxisVal[COLOR=#ffffff]([/COLOR]Differential_Toe, &axdata));
                    [COLOR=#1e90ff][B]if[/B][/COLOR]  ([U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_LEFT[/U]] < [U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_RIGHT[/U]]) TRPCOMBO = [U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_RIGHT[/U]];
                    [COLOR=#1e90ff][B]else[/B][/COLOR] TRPCOMBO = [U]TFRPHARudder[/U][COLOR=#ffffff][[/COLOR][U]TFRPHA_LEFT[/U]];
                    GameOutput (&o, [U]TFRPHA_LEFT[/U], AxisVal(-TRPCOMBO, &axdata)); }
                [COLOR=#1e90ff][B]if[/B][/COLOR](!axdata[COLOR=#ffffff].[/COLOR]locked & !axdata[COLOR=#ffffff].[/COLOR]relative) GameOutput(&o, x, AxisVal[COLOR=#ffffff]([/COLOR]o[COLOR=#ffffff][[/COLOR]x], &axdata)); } } }

You would also need to set the default curves for the axes, something similar to the function around Line 102 in the AD_EDFunctions_v3.3.0.tmh:

    [COLOR=#1e90ff][B]int[/B][/COLOR] initTFRPHARudder() {                                                                    
        SetSCurve([U]&TFRPHARudder[/U], [U]TFRPHA_RIGHT[/U], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]20[/COLOR], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]0[/COLOR]);                                    
        SetSCurve([U]&TFRPHARudder[/U], [U]TFRPHA_LEFT[/U], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]20[/COLOR], [COLOR=#ffffff]0[/COLOR], [COLOR=#ffffff]0[/COLOR]); }

Ensure define UseRuddersTPR = 1 too.

Let me know how you go or if you have any other questions.

If you get the code working, please share a copy back and I will add it to a future release.

Cheers, AD

 

[Clicker]

I would love to add a GUI or something but honestly do not know where to start. I don't think it can be done via the Target Script.

Cheers, AD

Hiya,

I think this is possible.

As you know, I have discovered and have been playing with some read/write file operations which exist in the TARGET support files.

To make this feature work, it would probably need an external program written (any visual studio type language would do).
It would need to be able to display a window with check boxes, radio buttons and free text fields that can write a simple raw txt file.

Once your script starts it can read in the contents of the text file and assign to the required variables.

The hardest or most fiddly part would be the chat responses..but I am certain this is do-able.

So, yeah, nah...it can’t all be done within TARGET script and would require a seperate, stand-alone (simple) app that the user can use to configure all your script parameters (and possibly the chats)

Like you, I’m not overly familiar with writing Windows based code, but will keep looking at this and see what I can whip up.
(By “whip” I do not mean soon, rather...”eventually” when I get some time)

Happy New Year!

Clicker

 

[Aussiedroid]

Hiya,

I think this is possible.

As you know, I have discovered and have been playing with some read/write file operations which exist in the TARGET support files.

To make this feature work, it would probably need an external program written (any visual studio type language would do).
It would need to be able to display a window with check boxes, radio buttons and free text fields that can write a simple raw txt file.

Once your script starts it can read in the contents of the text file and assign to the required variables.

The hardest or most fiddly part would be the chat responses..but I am certain this is do-able.

So, yeah, nah...it can’t all be done within TARGET script and would require a seperate, stand-alone (simple) app that the user can use to configure all your script parameters (and possibly the chats)

Like you, I’m not overly familiar with writing Windows based code, but will keep looking at this and see what I can whip up.
(By “whip” I do not mean soon, rather...”eventually” when I get some time)

Happy New Year!

Clicker

HNY Clicker!

Ah yes I do recall, but it did hurt my brain a bit trying to understand it lol. Wish I did know how to program other things, but given how long it took me to get into just the scripting language, I cringe at learning another lol.

Cheers, AD