AussieDroid,

Have you heard anyone having this issue? I have a Thrustmaster FCS (stick and throttle - pedals too). I went into TARGET and was able to put curves in and everything. But when I go into ED and try to actually map my buttons the Throttle (gas slider) and the "twist" on my stick end of being the same button from ED. Not sure why this would happen, I went to REDDIT and on the HOTAS page someone else is having similar issues. Any ideas? Is there something I am just forgetting to do?

Hey CMDR,

Nothing directly, but not a lot of discussion on the FCS specifically here. The only thing that comes to mind is the hard limit on the number of buttons and axes you can combine into a single virtual device, which I believe is a Windows/DX limitation. If there are too many, perhaps its bugs out and maps multiple inputs to the same DX key allocation.

Perhaps just for testing, remove your pedals from the equation and see if the combined stick and throttle only give the same results?

AD
 
Hey All,

Just wondering if anyone else with their Warthog has had issues since upgrading to the Fall Update (1709) for Win10?

I've had a range of issues myself impacting many things, but specifically with the Warthog, when I tried to create the virtual device it would fail with an error. Google didnt have much on the issue (sorry dont have the error code on hand). Going to troubleshoot further tonight, try some reinstalls & try the USB dance of the ports to see if I can resolve.

Cheers,
AD
 
No issues here. Though running a script and creating the virtual device took some seconds (once) yesterday. It still worked and nothing unusal today.
 
Thanks mate!

I'd actually noticed a slow response when creating the virtual device recently too. Actually, that was before the update, but when running the script now it remains slow before it errors out. Didn't have a chance to trouble shoot the issue further yet, but perhaps its just something local/specific to my machine.
 
Hi AD

My apologies for delaaaaaaay. I have not been playing for a while. Yes. the problem was the mic switch (the left eng switch set to 'motor').
I now check all switches prior to startup. Everything seems just fine now. Many thanks for Sooooooo much help! :) (See no ///////////// at all).

Cheers

Paul
 
I feel a bit silly posting here as the discussion is at a higher technical level than I function at, but is there an idiots guide to installing this script?
Bought my Warthog last week and never used scripts before.

Is there a YouTube video or something like that?
 
You can download the software itself from here (its the 'TARGET-Software' the other ones are documentation):
https://support.thrustmaster.com/en/product/hotaswarthogflightstick-en/

Then you can start the scripteditor and load the script (or edit it), or you can just make a link to the script file (.tmc) with the '-r' comand line option. Like this:

"C:\Program Files (x86)\Thrustmaster\TARGET\x64\TARGETGUI.exe" -r C:\Users\Hossi\AppData\Roaming\Thrustmaster\TARGET\Scripts\Elite_warthog.tmc
 
I've got the TARGET software, but there are bits of the instructions I don't fully understand. Like the navigating to bit in the target software. I don't understand how I go from the script editor to generating a file the TARGET GUI can open.
 
There are two different programms for the TARGET-Software
-TARGETGUI.exe
-TARGETScriptEditor.exe

The GUI is a good start for creating your own configuration. It is more or less self explanatory. But you can not use the more advanced script features. Still its a good startingpoint if you want to create your own script. Select 'new configuration', work through the dialogs, and in the end select 'view script'(opens in WordPad). Copy the script and open the ScriptEditor and paste it in there.

The GUI can also be used to run .tmc script files via link with the '-r' (run) command line option

The ScriptEditor can be used to create and run scripts. Once you've copied the script from the GUI you can safe it as a .tmc file. You can also run it directly from here. And you can edit, debug and test it. For the more advanced features you will need this one, but it has a steep learning curve.
 
So I can load Aussiedroids script in the editor, that's about as far as I've got. I was told I need an fcs file for the GUI, is that not correct?
 
.fcs files are for use with the TARGET_GUI. But if you want to use TARGET_Script thats the .tmc files.
If you can load the script into the editor, just click 'run' (the green triangle).
 
So I can load Aussiedroids script in the editor, that's about as far as I've got. I was told I need an fcs file for the GUI, is that not correct?


Hey CMDR Adaama,

There are no silly questions :)

Scripts can be loaded in either the Script Editor or Target GUI. Script Editor as the name suggests is the best one to load up if you want to modify the script or test things. The Target GUI is a bit more streamlined and good for running existing scripts. I normally run the script when I play in the GUI. There is a Run button in the top right.

Outside of other people's existing scripts, I learnt everything from the Target Basic Manual which you can get to via the Script Editor. So its a good place to start if you want to understand the coding further, but any questions I'm happy to help if I can.

Cheers,
AD
 
I know this thread has been quiet for a long time, but I'm just catching on to the amazing things this script can do. That said, I desperately want to add a button press (FA Off) to the use of my rotation axis (roll, yaw, pitch, thrusters). I know how to do this in the Target GUI, but as this profile is entirely script base, I don't even know where to start. Can anyone clue me in as to what script edits I would need to make to make the script hold FA off while I'm turning or applying non-throttle thrust?
 
I know this thread has been quiet for a long time, but I'm just catching on to the amazing things this script can do. That said, I desperately want to add a button press (FA Off) to the use of my rotation axis (roll, yaw, pitch, thrusters). I know how to do this in the Target GUI, but as this profile is entirely script base, I don't even know where to start. Can anyone clue me in as to what script edits I would need to make to make the script hold FA off while I'm turning or applying non-throttle thrust?

Hey Fail Forward,

I'm away from my gaming PC right now (at work), but can dig up the code parts used for the FA-Off in my script. I have it set to have both a hold and push depending on which way you move the switch. In ED bindings I think I have this set to hold as well to ensure it works correctly. I'll get back to you in 6-7hrs with how I do it :)

Cheers,
AD
 
Hey Fail Forward,

I'm away from my gaming PC right now (at work), but can dig up the code parts used for the FA-Off in my script. I have it set to have both a hold and push depending on which way you move the switch. In ED bindings I think I have this set to hold as well to ensure it works correctly. I'll get back to you in 6-7hrs with how I do it :)

Cheers,
AD

Wow, I wasn't really expecting to get a response on this. I'm hoping this isn't a dumb idea. I had set this up on my original profile so that on a hard turn (anything over 75%) it'd hold FA-Off, and then turn back on as soon as it went below 75 (so I wouldn't be spinning out of control trying to get my conda's fat butt out of dock). THEN I found your profile and never even got around to testing my idea. Your profile is just insane, and made the warthog purchase feel totally worth it... (Be moreso when my Crosswinds show up next month.)

Thanks again for your amazing work.
 
Wow, I wasn't really expecting to get a response on this. I'm hoping this isn't a dumb idea. I had set this up on my original profile so that on a hard turn (anything over 75%) it'd hold FA-Off, and then turn back on as soon as it went below 75 (so I wouldn't be spinning out of control trying to get my conda's fat butt out of dock). THEN I found your profile and never even got around to testing my idea. Your profile is just insane, and made the warthog purchase feel totally worth it... (Be moreso when my Crosswinds show up next month.)

Thanks again for your amazing work.

Hey mate,

No worries, glad you like the script!

I might have misread your request earlier - my apologies. For some reason I read it as you were looking for help on your script to sort out FA-Off mapping. Devil is in the detail :)

Reading back, that is a really interesting idea though, and I am thinking how it might be done. Right now, with my script as you may have already figured out, you could do this but would need to do manually as such. It's how I generally use FA-Off, I hold back direction on the two way switch on the throttle under the hat switch near thumb for a couple of seconds as I do a full turn then release. Short bursts when in combat and the like. Works fairly well, but to automate it would take it to another level :) Push it into the lock position forward to keep FA-Off enabled for extended periods.

I do have some code already that maps a key press to 100% throttle position (this is what is used for the Supercruise on Throttle function), so mapping a key press to an axis is possible, and could potentially be adapted for FA-Off at say 75% (or an adjustable level). This uses the AXMAP1 & LIST commands found around page 31-34 of the manual. This can set a zone, when it enters that zone a key can be pressed.

Gonna need to test this and play a bit I think & unfortunately I am going to be unavailable for a little while due to some eye surgery this week so may be a while till I can get to test it myself. Not sure how I may ultimately integrate it, but if you wanted to customise your script copy & play around yourself, something like this may work (untested - just spit-ballin' an idea ofc):


KeyAxis(&Joystick, JOYX, 0, AXMAP1(LIST(0,25,75,100), FAOFFKeypress, FAOFFKeypress, FAOFFKeypress));


Would need something like that for each axis in question. Could probably exclude Roll/Throttle, and just have on Yaw/Pitch. Guess it depends how it plays, but don't think Roll changes much when FAOff is on.

The logic here is that it should set 3 zones, 25% either direction (left/right) and a 50% center zone. When you enter/exit each zone it should fire the FAOFFKeypress ie 'PULSE+FlightAssist'. Move it left to the last 25%, FAOff is enabled, and would remain on till you release axis (hold is set in ED bindings file after all so will remain on). When you release axis and enter the middle 25-75 zone it presses it again to release the hold for FAOff. It should stay off while in this zone, but return to the 0-25 or 75-100 zones it will trigger again and hold FAOff again.

Assuming it works, if I was to include in a public release of the profile script, I would probably wrap that in a new user variable like 'AutoFAOFFMode' or 'CombatFAOFFMode':

if(AutoFAOFFMode == 1){
Do the KeyAxis command above etc
}

if == 0, essentially ignore and just default to the manual option already implemented (Same sorta logic I used for the CruiseOnThrottle settings for users to chose their preference). I think it would probably go into the Core Settings section of the main script near where I have the CruiseOnThrottle command.

Like I said, just an idea at this stage, but might just work :)

I'll look into this further when I can. If viable (and ultimately practical to use) can look to include in future update.

If you do get a chance to play yourself, I would be most interested to know if it works and off course what the experience is like. :)

Cheers,
AD



Edit: Actually thinking about this some more, that may not work as expected due to the combination of the axes when changing direction on the ship. :( If you had JoyX & JoyY both with a similar command it may get mixed up between actions; such as if you use a diagonal incorporating both axes - it might invert things or get out of alignment. Might still be able to be done, but may need to track the state of the FAOff as it moves between axes with some variables perhaps. If JoyX has FAOff, then do not enable/retrigger when JoyY is used or something like that. Hmmm .. will have to think this through some more I think or maybe I am over thinking this lol
 
Last edited:
Hey mate,

No worries, glad you like the script!

I might have misread your request earlier - my apologies. For some reason I read it as you were looking for help on your script to sort out FA-Off mapping. Devil is in the detail :)

Reading back, that is a really interesting idea though, and I am thinking how it might be done. Right now, with my script as you may have already figured out, you could do this but would need to do manually as such. It's how I generally use FA-Off, I hold back direction on the two way switch on the throttle under the hat switch near thumb for a couple of seconds as I do a full turn then release. Short bursts when in combat and the like. Works fairly well, but to automate it would take it to another level :) Push it into the lock position forward to keep FA-Off enabled for extended periods.

I do have some code already that maps a key press to 100% throttle position (this is what is used for the Supercruise on Throttle function), so mapping a key press to an axis is possible, and could potentially be adapted for FA-Off at say 75% (or an adjustable level). This uses the AXMAP1 & LIST commands found around page 31-34 of the manual. This can set a zone, when it enters that zone a key can be pressed.

Gonna need to test this and play a bit I think & unfortunately I am going to be unavailable for a little while due to some eye surgery this week so may be a while till I can get to test it myself. Not sure how I may ultimately integrate it, but if you wanted to customise your script copy & play around yourself, something like this may work (untested - just spit-ballin' an idea ofc):


KeyAxis(&Joystick, JOYX, 0, AXMAP1(LIST(0,25,75,100), FAOFFKeypress, FAOFFKeypress, FAOFFKeypress));


Would need something like that for each axis in question. Could probably exclude Roll/Throttle, and just have on Yaw/Pitch. Guess it depends how it plays, but don't think Roll changes much when FAOff is on.

The logic here is that it should set 3 zones, 25% either direction (left/right) and a 50% center zone. When you enter/exit each zone it should fire the FAOFFKeypress ie 'PULSE+FlightAssist'. Move it left to the last 25%, FAOff is enabled, and would remain on till you release axis (hold is set in ED bindings file after all so will remain on). When you release axis and enter the middle 25-75 zone it presses it again to release the hold for FAOff. It should stay off while in this zone, but return to the 0-25 or 75-100 zones it will trigger again and hold FAOff again.

Assuming it works, if I was to include in a public release of the profile script, I would probably wrap that in a new user variable like 'AutoFAOFFMode' or 'CombatFAOFFMode':

if(AutoFAOFFMode == 1){
Do the KeyAxis command above etc
}

if == 0, essentially ignore and just default to the manual option already implemented (Same sorta logic I used for the CruiseOnThrottle settings for users to chose their preference). I think it would probably go into the Core Settings section of the main script near where I have the CruiseOnThrottle command.

Like I said, just an idea at this stage, but might just work :)

I'll look into this further when I can. If viable (and ultimately practical to use) can look to include in future update.

If you do get a chance to play yourself, I would be most interested to know if it works and off course what the experience is like. :)

Cheers,
AD



Edit: Actually thinking about this some more, that may not work as expected due to the combination of the axes when changing direction on the ship. :( If you had JoyX & JoyY both with a similar command it may get mixed up between actions; such as if you use a diagonal incorporating both axes - it might invert things or get out of alignment. Might still be able to be done, but may need to track the state of the FAOff as it moves between axes with some variables perhaps. If JoyX has FAOff, then do not enable/retrigger when JoyY is used or something like that. Hmmm .. will have to think this through some more I think or maybe I am over thinking this lol

Well, I think I can parse out the logic that would be needed. I need to get up to speed on the scripting language.

Here's what we're looking for (at least from what I can gather):

psuedocode:
if(x_axis > 75% or y_axis > 75% or lateral_thrusters > 75% or vertical_thrusters > 75%) {
key_down FA_Off
}
if(x_axis < 75% AND y_axis < 75% AND lateral_thrusters < 75% AND vertical_thrusters < 75%) {
key_up FA_Off
}

I couldn't find from my 30 seconds of manual skimming between work stuff anything explaining the script language's IF command, but looking through your script it appears that IF can handle compound conditions. I saw the & symbol. I didn't see what the "or" symbol would be, though.

p.s.

Good luck with the eye surgery. Hope it's nothing serious.
 
Last edited:
Well, I think I can parse out the logic that would be needed. I need to get up to speed on the scripting language.

Here's what we're looking for (at least from what I can gather):

psuedocode:
if(x_axis > 75% or y_axis > 75% or lateral_thrusters > 75% or vertical_thrusters > 75%) {
key_down FA_Off
}
if(x_axis < 75% AND y_axis < 75% AND lateral_thrusters < 75% AND vertical_thrusters < 75%) {
key_up FA_Off
}

I couldn't find from my 30 seconds of manual skimming between work stuff anything explaining the script language's IF command, but looking through your script it appears that IF can handle compound conditions. I saw the & symbol. I didn't see what the "or" symbol would be, though.

p.s.

Good luck with the eye surgery. Hope it's nothing serious.

Thanks, just getting laser correction done to get rid of these pesky glasses, so hopefully wont be away for long.

See page 42 for the Operators that can be used with IF statements. OR can be done with | (or ||).

Your logic seems sounds. What I am not sure of, is how to determine the axis value in real time for the comparison to convert that to the script code. I'm sure there is some way to do this though. Failing that, the MapAxis mentioned previously may be an alternative, but instead of calling on the PULSE+FlightAssist directly, perhaps send that to run a function to do a check against all the axes and then output the correct status to either engage FAOff or disengage or do nothing.
 
Thanks, just getting laser correction done to get rid of these pesky glasses, so hopefully wont be away for long.

See page 42 for the Operators that can be used with IF statements. OR can be done with | (or ||).

Your logic seems sounds. What I am not sure of, is how to determine the axis value in real time for the comparison to convert that to the script code. I'm sure there is some way to do this though. Failing that, the MapAxis mentioned previously may be an alternative, but instead of calling on the PULSE+FlightAssist directly, perhaps send that to run a function to do a check against all the axes and then output the correct status to either engage FAOff or disengage or do nothing.

Oh, wow. Hadn't thought of that. What is the language behind this thing? Is it C? I'm familiar with C# and it looks a lot like that, but not quite. I'm pretty sure I saw a way to pull the axis values, so if the mapaxis can kick off a function I can definitely do this. I just need to figure out where all the parts go.

If I get it to work (probably not tonight) I'll post the function I end up using in case you want to play with it later (although, I'm sure you've already got it sorted in your head).
 
Back
Top Bottom