Release Aussiedroid's Enhanced Thrustmaster Warthog Script

Clicker · Jul 30, 2017

AussieDroid and Leo,

For what it's worth, I have the TM TFRP pedals and theyre working fine.
Note however, Im using the TARGET GUI and not a script.

In the GUI, I've included all three components (stick, throttle, pedals).
For the pedals though, I set the differential toe brakes to none (blank).
I also set left throttle lever to none as well (blank)...let's face it, it is not needed in this game.
I did this when I started geting conflicts when trying to bind all the axis within the controller binds in game. (Ie "you are already using Joy-X-Axis"...etc)

I'm also using an EDTracker Pro as well which uses 2 more axis.

Everything works fine.

So, whilst this may not help your immediate issue, at least you know that it "should work".

If I can help in any way by trying certain things, please let me know.

Clicker

Dar|{cyde · Aug 1, 2017

Very nice. I can assure you the Mode_filtered stuff works, I have the TFRPs. I wrote it specifically for ED. It's necessary because you can't map each pedal to e.g. Thrust up and thrust down. You can only map one axis to Up/Down. Filtered keeps the pedals as a separate device, it does not integrate into the TM virtual stick. They simply run thru target, and don't do anything unless target tells them to. I'll fire up your scripts when I have time to make sure it functions, but your copy-pasta looks good.

Code:

printf("Starting Macros... Throttle Profile Preset: NOT DEFINED              (Toggle FLAPS Before You Fly!)\x0a"); }

Look at my stuff for how to get around that. You just have to query the throttle switch during initThrottleAxis(), similar to how the joystickcurves function does it. That way its always set properly.

Sorrell · Aug 2, 2017

Aussiedroid.....you have changed the way I play elite.......what can I say but, thanks! Took a couple of weeks to retrain myself, mind, but definitely worth the effort.

Aussiedroid · Aug 2, 2017

Sorrell said:
Aussiedroid.....you have changed the way I play elite.......what can I say but, thanks! Took a couple of weeks to retrain myself, mind, but definitely worth the effort.

Awesome! Thanks so much for the feedback Sorrell

Dar|{cyde said:
Very nice. I can assure you the Mode_filtered stuff works, I have the TFRPs. I wrote it specifically for ED. It's necessary because you can't map each pedal to e.g. Thrust up and thrust down. You can only map one axis to Up/Down. Filtered keeps the pedals as a separate device, it does not integrate into the TM virtual stick. They simply run thru target, and don't do anything unless target tells them to. I'll fire up your scripts when I have time to make sure it functions, but your copy-pasta looks good.

Code:

printf("Starting Macros... Throttle Profile Preset: NOT DEFINED (Toggle FLAPS Before You Fly!)\x0a"); }

Look at my stuff for how to get around that. You just have to query the throttle switch during initThrottleAxis(), similar to how the joystickcurves function does it. That way its always set properly.

Thanks mate! I have trust in your script code, not so much in my implementation lol. Would certainly appreciate your feedback/testing to confirm this works. Give me some peace of mind if users with pedals are having issues in the future.

I think indirectly, I may have resolved the throttle not setting when I added the new code to the Cargo Scoop function, since on release this will return throttle curves to your preference (if you have it enabled in user prefs that is). Not really the way, but will check out how you have done it and see if I can improve for next update. Generally, most users will not have issues with it as it defaults to standard -100->100 range, but if the throttle presets are different (such as myself using a -100->80) the extra FLAPS toggle is needed to align.

Cheers!
AD

Dar|{cyde · Aug 2, 2017

here's mine:

Code:

int initThrottleAxis() {
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]    MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_REVERSED);
    //configure throttle on Flap switch position
    if(Throttle[FLAPU]) EXEC("mThrottleFwdOnly");
    else if(Throttle[FLAPM]) EXEC("mThrottleFullScale");
    else EXEC("mThrottlePrecision");
[/TD]
[/TR]
[TR]
[/TR]
[/TABLE]
[TABLE="class: highlight tab-size js-file-line-container"]
[TR]
[TD="class: blob-code blob-code-inner js-file-line"]}
[/TD]
[/TR]
[/TABLE]

Aussiedroid · Aug 3, 2017

That is a simple fix! Why didn't I think of that

Shouldn't require me to change up any of the other code either.

Cheers,
AD

CMDR Corleone · Aug 3, 2017

Anyone here tried one of these, or a similar alternative model?

https://warthog-extensions-by-sahaj.com/product-category/extensions/black/

Aussiedroid · Aug 3, 2017

CMDR Corleone said:
Anyone here tried one of these, or a similar alternative model?

https://warthog-extensions-by-sahaj.com/product-category/extensions/black/

Not personally, as I have my Warthog setup in a cockpit (RSeat RS1) so position is correct. I did look into these when I got my Warthog and it can apparently give you a greater level of control the longer the shaft is. Not sure if that would equate to a significant improvement for ED, but perhaps there is someone who has one who can comment in more detail.

Boy those prices are a bit steep for a little bit of metal and a DIN adapter though!

Dar|{cyde · Aug 3, 2017

CMDR Corleone said:
Anyone here tried one of these, or a similar alternative model?

https://warthog-extensions-by-sahaj.com/product-category/extensions/black/

Yup, I have one. From Sahaj too, but before he made them in black. Mine's 10cm. General consensus that I read was 7.5 was great for jet/plane guys, 10cm was good middle ground, and 15cm was pretty much just for helis. I do enjoy helis a lot, so I went with the 10cm. The improved ability to do fine control is awesome, although your ability to yank and bank may be reduced a bit. The warthog is plenty accurate even with the longer stick. Even at about 30cm/1ft height, moving the top of the stick 1mm is detected. If you get one, you will forever laugh at people who use curves on their inferior joysticks. I run mine center mounted, feels awesome. Comes with proper cable too, not a ps2 cable with a pin yanked out.

Aussiedroid:
Tried your script, rudders don't work because you include an old version of Target.tmh. I got a 'symbol not found TFRPRudder' error. There's no need to include that file unless you've made changes to it. I just deleted it, target pulled its own version, and everything works. Excluded and Filtered mode are both fine. Also, rudder mode 0 will hide TFRPs and put them on the virtual stick (which only has 1 axis to spare). I'd recommend filtered by default, otherwise exclude. The eventhandler code will never fire if TFRP isnt present.

CMDR Corleone · Aug 3, 2017

Aussiedroid said:
Not personally, as I have my Warthog setup in a cockpit (RSeat RS1) so position is correct. I did look into these when I got my Warthog and it can apparently give you a greater level of control the longer the shaft is. Not sure if that would equate to a significant improvement for ED, but perhaps there is someone who has one who can comment in more detail.

Boy those prices are a bit steep for a little bit of metal and a DIN adapter though!

It is a bit steep, but way cheaper than buying the machinery to fabricate it myself!

Dar|{cyde said:
Yup, I have one. From Sahaj too, but before he made them in black. Mine's 10cm. General consensus that I read was 7.5 was great for jet/plane guys, 10cm was good middle ground, and 15cm was pretty much just for helis. I do enjoy helis a lot, so I went with the 10cm. The improved ability to do fine control is awesome, although your ability to yank and bank may be reduced a bit. The warthog is plenty accurate even with the longer stick. Even at about 30cm/1ft height, moving the top of the stick 1mm is detected. If you get one, you will forever laugh at people who use curves on their inferior joysticks. I run mine center mounted, feels awesome. Comes with proper cable too, not a ps2 cable with a pin yanked out.

I'm sorely tempted to gain some greater accuracy with the stick, I only play ED, exploring at the moment, but when I get back I do some BH, some mining, some trading, general jack of all trades. Would you recommend the 7.5 or the 10? I'm a bit torn.

My gut instinct is that the 7.5 may well be sufficient to aid in slow manoeuvres while tightening up dog fighting while the 10 might slow me down a little too much when I want to turn my Vulture fast, however, if you are going to spend money on something to enhance accuracy then don't mess around, go for the 10 and do it properly!

Aussiedroid · Aug 3, 2017

Dar|{cyde said:
Tried your script, rudders don't work because you include an old version of Target.tmh. I got a 'symbol not found TFRPRudder' error. There's no need to include that file unless you've made changes to it. I just deleted it, target pulled its own version, and everything works. Excluded and Filtered mode are both fine. Also, rudder mode 0 will hide TFRPs and put them on the virtual stick (which only has 1 axis to spare). I'd recommend filtered by default, otherwise exclude. The eventhandler code will never fire if TFRP isnt present.

I really appreciate you taking the time to test it out Darkcyde and for your further education on scripting

Learned a few new things today!

I always though the target file needed to be there, there you go! lol and looks like that had some follow on effects. Yeah, this would have been an old target file too. I think it came from one of the first scripts I downloaded last year. No edits in it so I will remove.

Interestingly, the reason why I added the '0' option for the pedals was that it would fail to run using my MFG Crosswinds, when I first added the pedal code. I (incorrectly) deduced it was trying to find/include the TFRP pedals regardless of the setting, so forced it to exclude using the 0 option when running it. Same symbol not found error. All making sense now; the penny has dropped!

Looks like I might have to drop another update soon

Thanks again!!

CMDR Corleone said:
It is a bit steep, but way cheaper than buying the machinery to fabricate it myself!

No doubt

I was just being a bit cheeky, some investments are worth it in the long run, and quality is always worth spending more in my books.

CMDR Corleone · Aug 3, 2017

Aussiedroid said:
No doubt I was just being a bit cheeky, some investments are worth it in the long run, and quality is always worth spending more in my books.

Yep. I'm not rich enough to buy cheap!

Dar|{cyde · Aug 3, 2017

Regarding extension length, I only have the 10cm so I can't really compare. There is lots of advice out there, Sahaj has threads on the DCS forums, SimHQ, probably a few others. Dig those up and see what people say. You have to consider ergonomics as well. With my pit, I cant mount my stick any lower, and its currently at about solar plexus height. Any higher would be uncomfortable, but its fine where it is. I would've liked to use the 15cm, but it wouldn't work with my currently layout. If you play off a desk or chair mount, you might have to re-engineer things for the longer stick.

CMDR Corleone · Aug 3, 2017

Dar|{cyde said:
Regarding extension length, I only have the 10cm so I can't really compare. There is lots of advice out there, Sahaj has threads on the DCS forums, SimHQ, probably a few others. Dig those up and see what people say. You have to consider ergonomics as well. With my pit, I cant mount my stick any lower, and its currently at about solar plexus height. Any higher would be uncomfortable, but its fine where it is. I would've liked to use the 15cm, but it wouldn't work with my currently layout. If you play off a desk or chair mount, you might have to re-engineer things for the longer stick.

I have brackets mounted to my chair arms (see here), I can move them up or down a bit so 25mm height difference is not a problem, I'm more concerned about the effect on gameplay and if the stick will still reach fullly backward without being hindered by the chair arm once it has a greater scope of movement.

I'll check out the resources you suggested to look for more info, thanks for the heads up!

Aussiedroid · Aug 4, 2017

Hey DarKcyde,

Quick question on the rudder code, is this needed?

I see there is another calculation above it being used, but is this used/needed for anything or can I delete it?

// Differential_Toe = AxisVal(Differential_Toe, &axdata);

Also, just to let you know I got the other improvements implemented last night ready for testing in game. Throttle now seems to default to correct default without needing to toggle, rudder code is working my end with the cleanup to 2 options in UseRudder etc. As usual, next thing I know I am looking at the clock and its 2am and I have been tinkering with the script all night haha.. anyways

I'm not sure why, but I had to setup my code a little differently for the Throttle, like this:

(Ignore the different namings, these aliases simply map directly to the macros names you use)

if (Throttle[FLAPU]) ActKey(KEYON+PULSE+ThrottlePresetUP); // Configure Throttle FLAP Switch Position on Script Run
else if (Throttle[FLAPM]) ActKey(KEYON+PULSE+ThrottlePresetMID);
else ActKey(KEYON+PULSE+ThrottlePresetDOWN);

Using EXEC didn't seem to trigger the change when viewing in Device Analyzer. Even without the aliases it didn't seem to work.

Cheers!
AD

Dar|{cyde · Aug 4, 2017

You need to call AxisVal to apply curves and deadzones. I wanted a deadzone only on my combo axis, but not my differential one, thus the commented bit. Not designed for public consumption remember, this is my living script. Use this, I cleaned it up a bit.

Code:

    [COLOR=#1e90ff][B]if[/B][/COLOR] (&o == &TFRPRudder) {  
        GetAxisData(&o, x);
        [COLOR=#1e90ff][B]if[/B][/COLOR][COLOR=#ffffff]([/COLOR]x == TRPLEFT | x == TRPRIGHT) {
            axdata[COLOR=#ffffff].[/COLOR]locked = [COLOR=#ffffff]1[/COLOR];
            Differential_Toe = -TFRPRudder[COLOR=#ffffff][[/COLOR]TRPRIGHT]/[COLOR=#ffffff]2[/COLOR] + TFRPRudder[COLOR=#ffffff][[/COLOR]TRPLEFT]/[COLOR=#ffffff]2[/COLOR];
            GameOutput(&o, TRPRIGHT, AxisVal[COLOR=#ffffff]([/COLOR]Differential_Toe, &axdata));
            
            [COLOR=#1e90ff][B]if[/B][/COLOR] (TFRPRudder[COLOR=#ffffff][[/COLOR]TRPLEFT] < TFRPRudder[COLOR=#ffffff][[/COLOR]TRPRIGHT]) TRPCOMBO = TFRPRudder[COLOR=#ffffff][[/COLOR]TRPRIGHT];
            [COLOR=#1e90ff][B]else[/B][/COLOR] TRPCOMBO = TFRPRudder[COLOR=#ffffff][[/COLOR]TRPLEFT];
            GameOutput (&o, TRPLEFT, 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));
    }

As for your using ActKey... I have no idea. Must be some differences in the way its coded somewhere. Exec should work, its a function like any other.

...aaand now its 2am here too. [where is it]

Aussiedroid · Aug 4, 2017

Thanks!

I don't understand this code very well. I've cleaned it up. Cheers.

Can't figure out why EXEC wouldn't work either. Just wouldn't fire the code. No biggie though, it is working.

Aussiedroid · Aug 4, 2017

August Update! #2

Update 2.4.3: THE FEEDBACK RECALIBRATION MAINTENANCE RELEASE

-> IMPORTANT!: Existing Users, please delete any existing/old Target.tmh files in your script folder. They will cause the script to crash!

List of Changes:

NEW: Added an Override to Enable/Disable Cargo Scoop Precision Mode. This can be handy if you want to use Precision Mode in Ship, but prefer it disabled in SRV or other adhoc situations. (Hold CMS Hat Switch + Toggle Cargo Scoop any direction)

IMPROVEMENT: Toggling the Throttle Preset Toggle is no longer required in order to set your Throttle Axis the first time!
IMPROVEMENT: TFRP Rudder Code has been updated & verified working 100%. (UseRudder now only has 2 settings EXCLUDED & FILTERED) (Thanks DarKcyde for testing!)

FIXED: Removed Old Target.tmh from the download distribution. This was causing issues with the TFRP Rudder pedal intialisation. (Note: !Existing users! Please delete any old versions remaining in your script folder - they are no longer required & will cause the script to error)

CODE CLEANUP: Moved SetLED variable (Backlight intensity for the Throttle) to AD_EDSettings file to allow users easier access to edit.
CODE CLEANUP: Removed redundant warning messaging in script status printouts during startup now Throttle presets work by default.
CODE CLEANUP: General updates for a number of comments throughout, & also added new section headings in AD_EDFunctions file for Macros & Functions.

Fly Safe CMDRs!

** Please visit the ModDB link to get the latest version **

Note: The Reference Maps remain from the 2.4.2 version. These are identical to version 2.4.3, except for the addition of the Cargo Scoop Precision Mode Override. Separate Mini-Map included for this.

MRated · Aug 9, 2017

So im having a little issue when using the voice attack bind. Because it is set to ctrl+v or alt+v everytime i use the bind, it fires a heatsink because that is bound to V. How would i go about fixing this?

Also i have gone into the preferences and set it to HMB (rift) but the center bind is not working correctly?

Aussiedroid · Aug 10, 2017

MRated said:
So im having a little issue when using the voice attack bind. Because it is set to ctrl+v or alt+v everytime i use the bind, it fires a heatsink because that is bound to V. How would i go about fixing this?

Also i have gone into the preferences and set it to HMB (rift) but the center bind is not working correctly?

Hey MRated,

Sorry to hear you are having issues. I'll check on things further after work this evening and confirm the mappings are correct. VA should be using the default key maps for 99% of the key mappings, and that should include the activating etc too. Out of curiosity, does this work for you if the Warthog script is not running? ie with the same keys or does it also fire a Heatsink?

I think in terms of a resolution, it would be to change the mapping for enabling/disabling VA. So change the CTRL/ALT+V etc to something else and then remap to that in VA as well. This would mean that you would not need to change anything within the VA profiles directly to remap Heatsink. Like I said though, I will double check the mappings first as there is always the chance I have made a mistake.

For the center bind, one thing to try is to see if the key press commands based on your head tracking preference is triggering correctly using the Event Viewer. Change the setting in the user preferences and see if other mappings change the output in Event Viewer. I don't own a VR kit myself, but selection does seem to work ok between standard and TrackIR in my testing.

I'll double check it all as soon as I can and get back to you.

Cheers,
AD