Release Aussiedroid's Enhanced Thrustmaster Warthog Script

[Aussiedroid]

Hey imacken, not sure, it sounds like TARGET must still have it reserved access to the files. Perhaps TARGET hasn't closed down properly?

.. and thank you for the feedback, good to hear the looping fix has worked for others.

 

[CMDR Touille]

Thanks Aussiedroid, that has certainly solved all the looping/folder flashing issues I had. I'll try things out properly a bit later.
One thing I have noticed though - and it was the same in the previous version - is that I am not able to delete or move the temporary folder that I put your scripts in as a system error comes up saying that '.... the folder or a file in it is open in another program'.
Only a reboot of Windows will release it.
Don't know if it's a TARGET thing or your script.

If you launch via Target Script Editor, check Options/General (1rst TAB)/Script option at the bottom : if it's checked, the script run as a windows service and still run if you close target script editor without stoping the script; "DO NOT STOP THE SCRIPT WHEN THE EDITOR EXITS" ... if it's unchecked i don't know

 

[imacken]

Thanks guys, that option wasn't checked.
Stopping the script also leaves LED1 on, and the LED intensity very high. Only way of changing that is to go back into TARGET GUI and switch them.

 

[CMDR Touille]

HOLD S4 (Pinky Trigger) on Joystick & Move Friction Control Axis (INCR on Throttle) downward until the light is OFF before closing script : in AD_EliteDangerous_v2.2.tmc at the Bottom


if (&o == &Throttle & x == THR_FC & Joystick[S4]) {
LED_BRT = (AxisVal(Throttle[THR_FC], &axdata) - 32766) / 256 * -1;
ActKey(PULSE+KEYON+LED (&Throttle, LED_INTENSITY, LED_BRT));
}

// Throttle: LED On-The-FLy Backlight Control
// HOLD S4 (Pinky Trigger) on Joystick & Move Friction Control Axis

Ps : Sry the Forum is not Code Friendly / You are lucky, Aussiedroid comment Almost all the code, so, if you read a little you will learn "how to use" his script and how the code "work"

 

[Aussiedroid]

If you launch via Target Script Editor, check Options/General (1rst TAB)/Script option at the bottom : if it's checked, the script run as a windows service and still run if you close target script editor without stoping the script; "DO NOT STOP THE SCRIPT WHEN THE EDITOR EXITS" ... if it's unchecked i don't know

Thanks for sharing CMDR Touille, I didn't know this

- - - Updated - - -

Thanks guys, that option wasn't checked.
Stopping the script also leaves LED1 on, and the LED intensity very high. Only way of changing that is to go back into TARGET GUI and switch them.

While the script is running you can adjust the intensity as CMDR Touille mentioned. LED 1 is the FA Off light. Since FA is On by default the light is on by default, and is turned off when you turn on the FA Off switch. LED2 should operate in the same fashion. You could also lock on the FA Off on before you exit which should turn off the LED as well.

Hope it helps.

 

[imacken]

Thanks guys, that was helpful!

 

[imacken]

Aussiedroid, sorry to be so pathetic, but I tried your script, and I just can't understand your controls at all. I looked at your diagrams, but still, I don't get what the symbols mean for different presses, etc. Do you have any 'idiot's guide' explaining things?
Sorry!

 

[Aussiedroid]

Aussiedroid, sorry to be so pathetic, but I tried your script, and I just can't understand your controls at all. I looked at your diagrams, but still, I don't get what the symbols mean for different presses, etc. Do you have any 'idiot's guide' explaining things?
Sorry!

It's no issue at all mate. It looks more complicated that it really is .. but hard to represent all that info on the diagrams

Most of the symbols are identified in the Legend section of the guide. Each button or toggle can have multiple mappings depending on the modifiers pressed or the status in the game (ie in SRV or Ship) plus a few other states. These are colour coded in the Legend section to help make sense of the Key Mapping Diagrams. For example the primary trigger on Joystick is used for primary fire on both Ship & SRV and will also act as select on UI mode based on the situtation/state in the game.

To explain in a bit more detail, regardless of the state, there are two main types of controls:

First is the Normal Press/Long Press/Extra Long Press which allows different commands to be returned depending how long you hold the button down (PIPs are a good example of this). If you tap a direction for the PIPs quickly then just one PIP will move to that system, if you hold it for a short time, it will put 4 PIPs to that system & 2 to one of the others (There is also a 3rd alternative if you hold the button even longer!).

Second is the modifier buttons. These are primarily the Pinky Trigger & Thumb Hat Button on the Joystick. To use a modifier you hold the modifier down and then press a second button/toggle etc to fire the command. Modifiers on their own generally do not do anything (although in my case holding both Joystick modifier buttons 'squeezing the joystick' does go back/exit on the UI), but when combined with something else it opens up a new layer of commands.

Anything that uses a modifier will have a [1] or [2] in front of the description in the Key Mappings. If it does not have a number present then that mapping is just that button/toggle used independently.

So for an example of this, and one you will use regularly, the Panel controls. You will see on the Throttle Thumb Hat Switch, if you use this in flight by itself it will control your lateral thrusters. Nice and easy, but if you hold the Thumb Button on the Joystick down (the one on the side with the 4 way hat) then press a direction that you were using for thrusters, it will open up a Panel instead. Press that combo again and it will close the panel. Let go of the Modifier and the button returns to default thruster control. It will become very quick flicking between them when you get a handle on it.

Another example would be hold down the Joystick Trigger & then short pressing the Autopilot button on the Throttle which should activate the Auto-Pilot sequence.

They are probably the main things, but if still struggling perhaps print out or refer back to the guide in the game and see if you can get them going based on one of the above configs explained above. Once you see a few in action I think it will click very quickly

Let me know how you go.

AD

 

[imacken]

Thanks Aussiedroid for that detailed response. I've played around with your script a bit more, and I'm getting the hang of it.
Two immediate questions, firstly, how do I invoke headlook and secondly, what are the implications of changing the directions on your hat movement? I am used to using the throttle mouse for headlook, and I find your up/down/left/right to be more like my left/right/up/down!

 

[Aussiedroid]

Thanks Aussiedroid for that detailed response. I've played around with your script a bit more, and I'm getting the hang of it.
Two immediate questions, firstly, how do I invoke headlook and secondly, what are the implications of changing the directions on your hat movement? I am used to using the throttle mouse for headlook, and I find your up/down/left/right to be more like my left/right/up/down!

No worries.

Headlook is on the Joystick, hold Pinky Trigger & Down on the Target Hatswitch on the Joystick.

Inverting the axes, or swapping them around should not cause any issues to anything else. I use TrackIR so maybe I have them the wrong way around lol

 

[CMDR Minion Blob]

Thank you for posting this. Repped.

One question: I'm an Oculus CV1 user so I no longer use my TrackIR for ED. I currently use the Cougar UI virtual joystick mapped manually instead of scripting. I would like to try your configuration without the head look and TrackIR calls. Would there be anything else you can think of I would need to disable in the script to adapt it for VR-only profile?

 

[CMDR Touille]

You only need to add Reset HMD orientation
The easy way (if you don't play via steam ) is to set in ED Controls / Miscellaneous / Reset HMD Orientation to [F12] and use the TakeSteamScreenshot Button to reset your HMD orientation ( short press Landing Gear/Warning Silence Button, Aussiedroid script already map this to F12)'

For info in AD_EliteDangerous_v2.2.tmc:

MapKey(&Throttle, LDGH, TEMPO(EXEC(
"if(!Joystick[S4]) ActKey(KEYON+PULSE+TakeSteamScreenshot);"
.....
// Landing Gear/Warning Silence Button
// [Short: Steam Screenshot]

and in AD_EDKeyMap_v2.2.ttm:

define TakeSteamScreenshot USB[0x45] // F12


The other Way, you need to play with code and/or with the AD_EDKeyMap_v2.2.ttm and the forum is not code friendly so i can't help much here

 

[imacken]

Aussiedroid, another couple of issues. Firstly, there is still something odd going on with the script, as if I have run it a couple of times, then there are still some weird system things going on. For example, a few minutes ago, with the script running, I got Windows Explorer open when I clicked on my Elite Dangerous shortcut. Wasn't till I quit TARGET Script Editor that I was able to get it running again!
Also, I previously had Reverse Thrust bound to the speedbrake. How can I bind something to reverse thrust in your script, or is it already there?
Thanks again.

 

[CMDR Touille]

In AD_EDKeyMap_v2.2.ttm

Find:
// define ReverseThrottle DX10 // <Disabled>

Replace with : (without the // at the begin of the line)
define ReverseThrottle L_CTL+USB[0x15] // L_CTRL+R

In AD_EliteDangerous_v2.2.tmc

Find an Unmaped Button (easy way, speedbrake is already taken by function)
Find:
// MapKey(&Throttle, LTB, 0); // Left Throttle Button (RED)

if you want to use reverse key HOLD mode
Replace with (or add under : if // at the begin of line when you run the script the green text is ignored):
MapKey(&Throttle, LTB, DOWN+ReverseThrottle); // Left Throttle Button (RED)
MapKeyR(&Throttle, LTB, UP+ReverseThrottle); // Left Throttle Button (RED)

if you want to use reverse key TOGGLE mode
Replace with :
MapKey(&Throttle, LTB, PULSE+ReverseThrottle); // Left Throttle Button (RED)


IN ELITE DANGEROUS Controls configure Shortcut for reverse Throttle : Left CTRL+R and chose HOLD OR TOGGLE

Use the red Button Ingame for Reverse throttle. If you want to use speedbrake, it will be harder, you need to change more stuff (or lost some already here)


And sry for my english

EDIT : IT MAY NOT WORK, i Didn't check the ED Binding File Aussidroid give with the script, I checked only the script and didn't use this script and Binding (i use my one). If I check the Screen of mapping in OP 1rst Post LTB(Red Button) is USED. and Reverse is Already Mapped on Joystick CMS.
If you Tried and that don't work reverse the modification. Sry

 

[Aussiedroid]

Thanks CMDR Touille for helping!

You only need to add Reset HMD orientation

CMDR Minion Blob, I'll look to squeeze this somewhere into the official script on my next update, in the mean time CMDR Touille instructions should help

Aussiedroid, another couple of issues. Firstly, there is still something odd going on with the script, as if I have run it a couple of times, then there are still some weird system things going on. For example, a few minutes ago, with the script running, I got Windows Explorer open when I clicked on my Elite Dangerous shortcut. Wasn't till I quit TARGET Script Editor that I was able to get it running again!

imacken, this may be expected behavior. In the script there are a lot of keyboard commands used (Voice Attack, Macros etc), so if you had one of the toggles on for example, it would act like holding down/repeating a keyboard press. Generally speaking, it is good practice to reset your toggles before you exit the game to minimise this occurring (and to have you setup for next time you start the game). The only toggle that should be up is the Rotational Correction. Your landing gear may be up or down (but this one should not interfere with Windows). If nothing is held down/repeating, it should not be an issue running the script in Windows environment, but I do normally stop running the script myself after the session & exit the software.

AD

 

[imski]

Currently playing around with this and getting there, but I'm lost when it comes to adjusting my deadzones.

Launching Target doesn't expose any controls or axes that I can adjust and my old method of customising bindings with the game no longer seems to show me the deadzone setting option.

 

[CMDR Touille]

imski, in AD_EDKeyMap_v2.2.ttm

Find:

define JS_DEADZONE 1 // Set the JS Deadzone.. use the Device Analyzer to validate

Change 1 to something else, Save the file and run the script. Launch the device analyzer in target script editor and test

From target script manual :
"The Deadzones are value ranges where nothing happens if the axis cursor reaches the zone. The value is a % of the total axis range. This higher the value, the larger the Deadzone. Be careful with deadzones, as you can easily negatively impact your controller's behavior.

 The center Deadzone: You can use this one if you want to ignore small axis movements when the axis cursor reaches the center area (usually set between 0 to 5%). "

 

[T1-Jafo]

Question about the Curve

Goal: to change the axis range on the “Forward Only” mode using S-Curve settings to allow for use of the Afterburner block. Otherwise when Throttle is 81%-100% forward, makes it tough / awkward to access throttle handle buttons, and especially the Engine Fuel Flow Left switch.

Can be easily done utilizing a J-Curve setting of 50, 80 (or 80,99), but then how do you make it “Forward Only”?

My understanding is the S-Curve format is: ( {device}, {axis}, left dz, center-dz, right-dz, curve, zoom )
(Please forgive me if the format is incorrect, I am away from my gaming computer and typing this from memory with my phone, (damn auto-correct). I am interested in the parameter values, not the correct syntax).

The Forward Only setting I have borrowed from Aussiedroid, has the TRIM set to -1024 with S-Curve set to ( x, x, 0,-100, 0, 0) . ( I assume the Zoom/Scale value at the end is omitted).

I thought entering a left-deadzone vaule, (around 20), but that seems to have the opposite effect, (when checking with Device Analyzer).
I was able to get this to work with Target’s GUI interface, but it would not allow me, ( or I don’t know how), to set a negative value for center deadzone, with the GUI, which is needed for the ForwardOnly mode.

I hope this makes sense.

 

[Aussiedroid]

Hey MisterTang,

I think I am following you, but don't have time to test it myself as I am at work, so some ideas to try:

I use a shorter 80% range (Full range tho not forward only) in my cockpit due to the position of the throttle. Any further and, as you said, it cant reach the buttons on the arm. Or for me it means having to lean forward out of the seat to reach.

To get that 80% range I used this:

"SetJCurve(&Throttle, THR_RIGHT, 80, 100);"

This is basically saying that at 80% .. I want the axis to represent 100% of the range. It will scale it down from this to 0 accordingly.

Now, as you have already discovered, this sets the Fwd only range:

"TrimDXAxis(DX_Z_AXIS, SET(-1024));"

So my thought is that you may have to change this SetSCurve line to the SetJCurve line above:

"SetSCurve(&Throttle, THR_RIGHT, 0, -100, 0, 0);"


End result:

mThrottleFwdOnly = EXEC(  												
			"TrimDXAxis(DX_Z_AXIS, SET(-1024));"		                       
			"SetJCurve(&Throttle, THR_RIGHT, 80, 100);"
			"SetThrottle();");

Interested to know if it works

 

[T1-Jafo]

Interesting, it works, but not as expected.
Setting the TRIM to -1024 creates the correct starting point; however, with the J-Curve set to 80,100 it shortened it too much.

I am going to try changing the J-Curve to 40, 50 and see what happens.

EDIT - the 40, 50 is better, but still a little short.
Still playing around with different setttings, but on the right track.

- Thanks I will post final results.
(btw - this was by accident, but for the fun of it set the J-Curve to 80, 50 and watch the behavior in Device Analyzer).