Jump to content

Warthog Throttle TARGET Script with DX Outputs for All Switch and Rocker Off States


ReflexArc

Recommended Posts

1 hour ago, speed-of-heat said:

this is what i use:

        MapKey        (    &Throttle,     IDLERON,      PULSE+DX71);
        MapKey        (    &Throttle,     IDLELON,      PULSE+DX72);
        
        MapKey        (    &Throttle,     IDLEROFF,      PULSE+DX73);
        MapKey        (    &Throttle,     IDLELOFF,      PULSE+DX74);

 

which works fine 

 

 

Looking at it again it never saved after I made the changes. As soon as I saved it and ran it, DCS saw 50-51, all good!


Edited by GaryR

Asus Z790-PLUS D4, Corsair 1000X PS / Intel i9-13900KF @5.8Gz - Corsair H150i Liquid CPU cooler, 64GB Corsair Vengeance DDR4 @3192mhz / 2TB M.2 NvMe Boot Drive (DCS World Beta installed here), 1TB M.2 Data drive, 1TB WD SATA drive, Zotac Gaming GeForce RTX 4090 Trinity 24GB - Nvidia 551.76 driver / 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz  / Win11 Pro Ver.  23H2 - Build 22631.3374 TIR 5, TM Warthog HOTAS\VirPil stick base, MFG V3 Crosswind Pedals, TM MFDs  on 2 8" Lilliputs/ Simgears ICP / Varjo Aero VR

Link to comment
Share on other sites

not as far as i know/remember

the only thing to remember is if you have any switches not set to pulse you might need a couple of goes to make sure its picking up the right ones


Edited by speed-of-heat
  • Thanks 1

SYSTEM SPECS: Hardware Intel Corei7-12700KF @ 5.1/5.3p & 3.8e GHz, 64Gb RAM, 4090 FE, Dell S2716DG, Virpil T50CM3 Throttle, WinWIng Orion 2 & F-16EX + MFG Crosswinds V2, Varjo Aero
SOFTWARE: Microsoft Windows 11, VoiceAttack & VAICOM PRO

1569924735_WildcardsBadgerFAASig.jpg.dbb8c2a337e37c2bfb12855f86d70fd5.jpg

Link to comment
Share on other sites

Looking at your script I saw it was identical other than the DX#s, which caused me to re-open the file and see my changes were not saved.. Once saved all was well, works perfectly! Thanks for all the help Speed! 

  • Thanks 1

Asus Z790-PLUS D4, Corsair 1000X PS / Intel i9-13900KF @5.8Gz - Corsair H150i Liquid CPU cooler, 64GB Corsair Vengeance DDR4 @3192mhz / 2TB M.2 NvMe Boot Drive (DCS World Beta installed here), 1TB M.2 Data drive, 1TB WD SATA drive, Zotac Gaming GeForce RTX 4090 Trinity 24GB - Nvidia 551.76 driver / 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz  / Win11 Pro Ver.  23H2 - Build 22631.3374 TIR 5, TM Warthog HOTAS\VirPil stick base, MFG V3 Crosswind Pedals, TM MFDs  on 2 8" Lilliputs/ Simgears ICP / Varjo Aero VR

Link to comment
Share on other sites

  • 4 weeks later...
  • 10 months later...

Trying to get this up and running for my Warthog Throttle (with the aftermarket TDC slew switch from Delta Sim Electronics), and can't quite figure out what all is needed to make this work all work. Can someone point me to a single place where the most up-to-date versions of these files are located and what the specific install instructions are (i.e. what folders the files need to be in, etc.). Thank you for the help!

 

V/R,

Gunmetal73

Link to comment
Share on other sites

11 hours ago, gunmetal73 said:

Trying to get this up and running for my Warthog Throttle (with the aftermarket TDC slew switch from Delta Sim Electronics), and can't quite figure out what all is needed to make this work all work. Can someone point me to a single place where the most up-to-date versions of these files are located and what the specific install instructions are (i.e. what folders the files need to be in, etc.). Thank you for the help!

 

V/R,

Gunmetal73

My scripts are in C:\Program Files (x86)\Thrustmaster\TARGET\scripts, to use the WarthogThrottleALLSwitchPos script you need WarthogThrottleALLSwitchPos.tmc and the targetdx128.tmh in this folder. IIRC i had to add a couple lines to get what I want but it ran as-is..

  • Like 1

Asus Z790-PLUS D4, Corsair 1000X PS / Intel i9-13900KF @5.8Gz - Corsair H150i Liquid CPU cooler, 64GB Corsair Vengeance DDR4 @3192mhz / 2TB M.2 NvMe Boot Drive (DCS World Beta installed here), 1TB M.2 Data drive, 1TB WD SATA drive, Zotac Gaming GeForce RTX 4090 Trinity 24GB - Nvidia 551.76 driver / 3 Samsung LC32G53TQWUXEN 32" 7680x1440 at 144Hz  / Win11 Pro Ver.  23H2 - Build 22631.3374 TIR 5, TM Warthog HOTAS\VirPil stick base, MFG V3 Crosswind Pedals, TM MFDs  on 2 8" Lilliputs/ Simgears ICP / Varjo Aero VR

Link to comment
Share on other sites

  • 6 months later...
  • 10 months later...

Do you run the latest Target with older scripts?
If so, use the previous defines.tmh, sys.tmh and hid.tmh instead of the new ones.

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

  • 3 weeks later...
On 10/30/2023 at 4:18 PM, Lange_666 said:

Do you run the latest Target with older scripts?
If so, use the previous defines.tmh, sys.tmh and hid.tmh instead of the new ones.

Sorry, can you elaborate on this please?

I've been using this for over 2 years now, I know I had to do something before to make it work, but now I don't remember what that was.
Like patpat above, I've just installed windows 11, and used the latest version of the TM software.

I'm getting the same error as above
Compile Error: Identifier name expected in targetdx128.tmh at line 883

I made a shortcut to the script launcher that says
"C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r "G:\Saved Games\DCS\WarthogThrottleALLSwitchPos2.tmc"

The WarthogThrottleALLSwitchPos2.tmc has a 2 in it because I modified it somehow, for one of the buttons I think.


And now I don't know what to do....... please HELPPPPPPPPPPPPPP!!!!!!!


Edited by jonsky7
Link to comment
Share on other sites

4 hours ago, jonsky7 said:

Sorry, can you elaborate on this please?

After installing the latest version 3.0.23.608 (which includes F-16 Throttle) none of my scripts would compile and would always come with an error:

Compile Error: Identifier name expected in targetdx128.tmh at line 883

It's the first line where the extra DX buttons (above 32) are defined.

I just replaced the defines.tmh, sys.tmh and hid.tmh files with those from a previous version 3.0.20.826 and then it worked again.
Actually, both sys.tmh and hid.tmh don't need to be replaced because they are the same as the previous version but defines.tmh differs (i guess because the F-16 Throttle also goes beyond the standard 32 DX buttons per device).
 

Solution: just replace the new defines.tmh with the the old one.

I'll drop that old one here:

 

defines.tmh


Edited by Lange_666
  • Like 1

Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind combat pedals, TrackIR4, Rift-S.

Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!

Link to comment
Share on other sites

4 hours ago, Lange_666 said:

After installing the latest version 3.0.23.608 (which includes F-16 Throttle) none of my scripts would compile and would always come with an error:

Compile Error: Identifier name expected in targetdx128.tmh at line 883

It's the first line where the extra DX buttons (above 32) are defined.

I just replaced the defines.tmh, sys.tmh and hid.tmh files with those from a previous version 3.0.20.826 and then it worked again.
Actually, both sys.tmh and hid.tmh don't need to be replaced because they are the same as the previous version but defines.tmh differs (i guess because the F-16 Throttle also goes beyond the standard 32 DX buttons per device).
 

Solution: just replace the new defines.tmh with the the old one.

I'll drop that old one here:

 

defines.tmh 42.53 kB · 0 downloads

 

Thanks very much,

I haven't done a great deal of testing but I think I got it working with a slightly different method.

I edited the targetdx128.tmh and removed the definitions for DX33 to DX64 (line 883 to 914)

I think because like you say, they've added more buttons to the defines.tmh, so not as many are needed in the targetdx128.tmh file.

targetdx128.tmh

  • Thanks 1
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...