sweet thx, will test that out...
No I meant the presets like numpad 3...
Im trying to bind it in place of the srv v boost on the coolio down...but not having much luck so far.... seemed a good place as there is an srv v boost elsewhere...

Ill keep trying and learning this target stuff :D
 
sweet thx, will test that out...
No I meant the presets like numpad 3...
Im trying to bind it in place of the srv v boost on the coolio down...but not having much luck so far.... seemed a good place as there is an srv v boost elsewhere...

Ill keep trying and learning this target stuff :D

Ah ok, I had a look at the Coolie Down in the script and it is currently not mapped. This should mean that you can map it directly in Elite Dangerous in a spare slot for the 75% Throttle keypress. Are you having any issues doing this?

Alternatively, you could map this in the script rather quickly by changing in ADEliteDangerous_v2.3.tmc:

Code:
//	MapKey(&Throttle,  CSD, 0);

to

	MapKey(&Throttle,  CSD, [B]PULSE+SetSpeed75[/B]);

Note though, that if you update it in the script it will override any mapping in ED that also use that button. This means you will need to remap the Camera Blur Plus & Galaxy Map Pitch Down in ED again after you save the script. After remapping in ED you should see these appear as NUM+3 just as it would if you pressed the keyboard button instead of the Joy XX mapping.

If you wanted to try the Throttle Trimmed Preset as well you can change this in the ADEDSettings_v2.3.tmh. Rather than just setting the speed to 75% once per press, setting this Throttle preset will prevent the throttle from being able to go beyond 75% (top of blue zone) at all.

Example (you can choose any order/combo you like):

Code:
[U]Default[/U]

	define ThrottlePresetUP 	mThrottleFwdOnly
	define ThrottlePresetMID 	mThrottleFullScale
	define ThrottlePresetDOWN 	mThrottlePrecision


[U]Custom with Trimmed Throttle instead of Forward Only Throttle[/U]

	define ThrottlePresetUP 	[B]mThrottleTrimmed[/B]
	define ThrottlePresetMID 	mThrottleFullScale
	define ThrottlePresetDOWN 	mThrottlePrecision

Hope it helps.
 
thanks....yeah got it....what i didnt realise was the event viewer (showing coolio down as pgdn) is diff to in game.....
was only testing via target keymap event viewer.......which seems to suck and show incorrect stuff...lol

Ive actually warmed to the new trimmed throttle over the numpad-3 setting......ill keep fiddling, but great job....without this my life with warthog would suck.....
now to save up for the crosswinds lol
 
Last edited:
May Update!

Update 2.3.2: Commanders Maintenance Release

List of Changes:

NEW: CruiseOnThrottle check for the China Hat Switch on Throttle. (This will keep default mapping with short & long presses if you are not using FSD on Throttle, else it will remove FSD from the switch, moving Orbital Lines to Up & keeping Next in Route on Down (no long press mapped)).

IMPROVEMENT: Swapped Repeater / Combo Fire Modifier buttons on Pri/Sec Fire. Hold Pinky Trigger+Fire for R-Fire & CMS Hat Switch+Fire for C-Fire.
IMPROVEMENT: Jettison All on Cargo Scoop Toggle will now correctly close the Cargo Scoop after action.

FIXED: Error found in IdleMaster Function. This is now mapped correctly to the new Throttle Preset toggle location. Note: For the function to work, you will need (if you use) to place Forward Only Throttle in the UP Position as per default mappings, else you will need to modify the button mapping in the macro function.


Fly Safe CMDRs!
 
June Update!

Update 2.3.3: Commanders Maintenance Update

List of Changes:

NEW: Escape Vector Macro now includes Landing Gear & Cargo Scoop checks. If they are deployed, the macro will override the toggle & retract for a quick escape.

IMPROVEMENT: Escape Vector Macro timings have been improved.
IMPROVEMENT: Combined Flight Assist Off & Alternative Flight Controls onto the Speedbrake. Hold Pinky Modifier & either direction to enable Alt. Flight (note: you do not need to keep holding the pinky while holding the Speedbrake On).

FIXED: Chat Macros will now enter text correctly when the Comms Panel is already open (Should now work in ALL scenarios!)
FIXED: Removed Video Manual Capture from China Hat Switch on long press when CruiseOnThrottle is enabled (why was that mapped there?!)
FIXED:
Restored correct SRV Digital Steering mappings in ED Profile back to the Mic Hat Switch L/R.
FIXED: Thruster Forward/Back digital mappings on Coolie Hat Switch. This will again allow users to have access to Reverse thrust when using Forward Only Throttle mode (note: Reverse Toggle button will only work if remap to Forward Only in ED Settings, negating the benefit of the Throttle Axis Profiles in script).

CODE CLEANUP: Various minor code changes, some formatting & comment updates as well.
MAP CLEANUP: Added alternative mappings (based on CruiseOnThrottle user pref.) for the China Hat Switch to the Throttle Arm Reference Map.


Fly Safe CMDRs!


*Update 2.3.3.4 : Fixed mis-mapped Reduce Blur in Camera Mode.
 
Last edited:
Hi AussieDroid,

Got a new PC, backed up ED bindings but not TARGET's ... so, ended up here.

Impressive work, but I am largely dead in the water, learning new bindings. Thanks for the documentation, but if you'd had a map of what keys mapped to what button presses, as well as outcome, I might be able to understand it better.

Being in VR, I absolutely need the "Reset HMD". This is mapped to [L CTRL] + [END] in the ED controls..... I figured out that END maps to the ENG OPER L switch, and can see that in the Event Tester. But what does [L CTRL] map to? I have tried with modifier 1 (grey 4-way depressed on stick), with modifier 2 (pinky switch), both at the same time.... but nothing.

I can't figure it out at all. What am I doing wrong?

Been a while since I aimlessly drifted in space, lost like a total noob :D

Two others:

* safe drop from SC?
* I think secondary fire should be the grey button at the base of the stick, but it would not fire the KWS...?

Sorry, I am probably just an idiot


====================

EDIT: OK, I think I figured out the FSD one: I should probably "in the AD_EDSettings_v2.3.2.tmh file. Set [CruiseOnThrottle] to '0' to move the FSD to the red hat". I would assume I'd just flick the red switch then to drop.

I'll remap the Track IR to Reset HMD, so that should take care of that, and check the mapping for 2ndary fire. If that doesn't work, I can remap it to the ECM/SCB button, as I don't use either...

Thanks!
 
Last edited:
Hey Mangal Oemie,

Thank you and sorry for the late reply. Feel sorry for you loosing your script .. that would hurt! Hopefully the learning curve isn't too great starting with something new! Sounds like you have sorted things out?

A note on the fire buttons (which you have probably already figured out now), secondary fire is possible from both the primary red trigger and also the little grey button at the base of the joystick. This gives you the option to combine fire groups to one button or fire the group separately. Not sure why it might not be firing the KSW though, unless it something obvious like not being assigned in your panels. Now one other thing to note here, I did find a small error in my fire switch logic, but I don't think that should have caused the button not to fire. I have that fixed for my next update 2.4.0.

Safe drop from Supercruise should function the same way on the throttle as it does on the China Hat Button. Double tap should get you out in an emergency and just single trigger should drop you down as a safe drop.

You are not the first to raise the Reset HMD button (or the lack of direct mapping/setup). Been a low priority for me as I do not have VR :( You seem to know a little about the scripting side so probably not a hard change to make yourself, but in a future update I will look to improve this and provide some sort of user preference so this can be set easily. Its on the to-do list :) Remapping TrackIR button is probably the best location without having to move other things around.

Let me know if you are still having any issues :)

Cheers,
AD
 
All good, Aussie! And I am now, as I am getting used to the scheme, deeply impressed by the richness of the mapping, and how it all fits together.

- reset HMD: done. Just set it to END, and I am good, there. So yeah, maybe make it a config switch? People will have either TrackIR or VR, not both, so it could just be a 0 or 1 setting for that
- figured out the switch for FSD/SC and now using the red throttle switch, works perfectly for me
- didn't I say I was an idiot? Tested KWS without having a target selected :p -- the default for the low grey button is fire 1+2 at the same time, so I just click that away to separate even before starting ED. I actually like it low at the base, interferes less with stick direction, which helps with FAOff flying/combat

I went from deeply confused to being about 90% comfortable with it. I reckon after the weekend it will be second nature.

So, let me add myself to the long line of Warthog pilots thanking you profusely for this amazing scheme. I had gotten used to flying without lateral thrusters, which are now easily available. I no longer need to choose between selecting next target or next contact, because now the difference between the two is just a modifier switch. And I spent a bit of time updating the 12 chat macros to relevant phrases. Really awesome stuff.

[yesnod]
 
That is awesome to hear mate! I really appreciate the feedback too :) Its always very interesting to know what others find good (or bad for that matter). Has lead to a lot of improvements in the past, often things I do not think of.

I coded up a user preference with a simple toggle for the headlook based on your hardware last night. Hopefully test it out later today. I have simply set it up to toggle the mapping of the TrackIR Center toggle on the Throttle to change to ResetHMD for VR or if you have neither for it to default to built in headlook center.

I would be interested to know what chat updates you made too, if you don't mind sharing? TBH the ones I have in there now I am not 100% happy with either, but I seem to be terrible coming up with good alternatives lol.
 
First up ... WOW!

Just WOW! You have obviously put in so much effort here...and to keep it updated and conintue to maintain over a year+...exceptional!

I recent bought my second X55 after my first one started playing up (wires inside throttle broke) after 2 years of playing ED (for me that was around the 950 hours mark I figure)
In the three months I've owned the second one, I've had the throttle apart twice to get rid of excess grease and free up the movement.
I've had the joystick apart 3 times to grease the twist yaw and the stick off the base 6 times to grease the shaft.

Why am I telling you this? Well, obviously I've just taken the plunge and bought myself the TM Warthog HOTAS and a set of TM TFRP Rudder peddles (30% off sale at my local PC shop here in NZ).
I've lusted after one of these HOTAS for a long time but they are bloody expensive, retailing at $800-$900 here in NZ, and well, my birthday is looming, my company just advised we're getting bonus this year and well, 30% off!
Wife doesn't know yet so I'm reading up as much as I can before connecting it all up...this will also give me some time to work out how to gently break it to her...hmmm maybe time to look at eternity rings she keeps hinting at!

Whilst I'm very familiar with how I've mapped my X55, your mappings are very different in many places....in a lot of ways yours makes more sense.
I'm a little daunted by the modifiers and I've avoided using anything similar with the X55 to keep things relatively simple (I don't use quite a few functions and still use keyboard for other things).
I can see though that you've really gone a long way to map absolutely everything and to learn all of this will take time and practice.

So, I'll be taking a very long look at what I've got bound on my X55 and where they're the same or different to yours and focus on that first before looking at the extras!

Thanks for the effort and no doubt you'll hear more from me some time soon.

Cheers
Clicker
 
Hey there Clicker! Appreciate the comments. I came from an X55 myself, found a lot of things I could basically map the same, but the different configuration/layout does mean some things moved around. Warthog will feel heavy to begin with after the X55, but you will quickly adjust :) You will love it I am sure :) 30% off sounds like a decent deal too!

With regards to the Modifiers, certainly appreciate how they can be daunting. On paper it makes things look a mess, and far more complex than they actually are. Once you have the concept in mind & practiced a few of the basics, the muscle memory starts kicking in. Ideally, it would be great to have it without them, but there are simply not enough buttons even on the Warthog to cover everything, and some prime located hat switches etc are well suited for multiple functions so combining them I found was the best way forward. There is a lot under the hood of this script, but most of the most utilised commands are quick to pick up within a couple of hours in the cockpit (so I have been told by others anyways lol).

Hope the script gives you a starting point to see what is possible with the Warthog. I always encourage others to modify it as much as you want, so if you find anything you want to move around or change, happy to offer some advice on how to do it.

PS - I am almost finished with a rather big update to 2.4.0, with some new features, fixes and other things.. so stay tuned :)
 
June Update! #2

Update 2.4.0: Mystery Update

Special Note: To existing users, thank you all for using my script profile [heart]. I have just hit 600 downloads via ModDB & your support/feedback has been fantastic! If you are still using an older version, please upgrade to this version. This milestone update rewrites large sections of the code, introducing better error checking & functionality along with the new features below. It is a considerable upgrade that eliminates a range of unreported small querks/bugs and finalises all point update integration since 2.0 versions! At this point, all features I wanted to add are included and working 100% to my liking, and nothing remains on the to-do list outside of some better chat responses at some point when I finally get creative lol, so I suspect this will be my last public update (outside of bug fixes :p) until 2.4 gets a release later this year.

Hope you like the improvements!



List of Changes:

NEW: Repeater Fire now offers automatic disengagement option configurable in the user preferences. (Existing Manual disengagement can still be chosen for combat pilots - Automatic is perfect for Explorers & will disengage after scanner duration)
NEW: Headlook Center Function that can be configured in the user preferences. You can now choose your preferred headlook mode based on if you are using TrackIR, VR Headset or just the mouse. (This will remap the Engine Operate Ign/Norm LEFT UP toggle accordingly)
NEW: Mode Switch Menu Macro added. This new feature will simply navigate the game menu to exit current session & automatically get you back to Start to choose a new game mode. (Hold down both Pinky Trigger & CMS Hat Switch Modifiers then press the Red Throttle button)

IMPROVEMENT: Swapped Rotation Correction & Silent Running toggle positions. (This gives higher priority toggle to Silent Running - easier access in combat etc)
IMPROVEMENT: Finally resolved the issues with Escape Vector Macro! Some further refinements to the timings, but also better management of the hardpoint flag to ensure it works every time. This will now force hardpoint deployment then retract as part of the process (doesn't impact the time). (Note: Deploying hardpoints via Primary Fire will throw the alignment out of the macro. Technical issue I can't seem to overcome :( As such, by default I have disabled primary fire deploying hardpoints. This may not suit everyone; don't worry, I have you covered as well. If you reenable in ED Controls under Weapons, and find the alignment goes out for the macro, simply Long Hold down the hardpoint button to reset the hardpoint flag, then try again. This will take you an extra second but still much faster than doing it all manually!)

FIXED: Introduced error check code to prevent keypresses triggering during script load. (This also removes the need for the previous workaround StartupCleanup function .. yay!)
FIXED: Small coding error in Secondary Fire logic (didn't seem to be impacting anything though).
FIXED:
Mismapping for Pitch Up on Galaxy Map.

CODE CLEANUP: MASSIVE rewrite introducing 5 new functions for core code features. Created functions for Silent Running, Microphone, Hardpoints, Docking/Signal Lights, Primary/Secondary Fire Module. This cleans up all features added since public release, more modular & easier to modify as needed for those that want to customise the default setup or use some of the code in their own scripts.
CODE CLEANUP: Added new output messages in TARGET for Voice Comms, Repeater Fire & Silent Running, & cleanup of a few other messages.
CODE CLEANUP: Updated Script Load Printout to add new User Preference settings.



Fly Safe CMDRs!
 
Last edited:
Hiya,

I have a quick question.
Are your keyboard bindings compatible with HCS Voicepacks?

I guess I could print yours and theirs out and compare, but thought I'd ask first.

Cheers
Clicker
 
Hiya,

I have a quick question.
Are your keyboard bindings compatible with HCS Voicepacks?

I guess I could print yours and theirs out and compare, but thought I'd ask first.

Cheers
Clicker

Yes it is, approx 99% are mapped correctly. A few are changed as required, but these are marked out in the KeyMap file so you can easily remap if you want to :)
 
Hi Aussiedroid
I have a question how do I activate the Defensive Pattern Delta and what button on my HOTAS Warthog do I use. And Thanks for the Script I love it
 
Hi Aussiedroid
I have a question how do I activate the Defensive Pattern Delta and what button on my HOTAS Warthog do I use. And Thanks for the Script I love it

Hey Ironside,

Thanks mate!

To activate, you need to hold down the Pinky Trigger Modifier on the Joystick + Hardpoint 'Red' button on the Throttle. The Chaff & Engine boost parts of the macro can be enabled in the user preferences. :)

Also to add, any command that has a number at the start such as [1] or [2] etc means you need to hold down a modifier key, such as the Pinky Trigger. Can be hard to read off the map as its pretty busy.

Cheers!
 
Last edited:
That is awesome to hear mate! I really appreciate the feedback too :) Its always very interesting to know what others find good (or bad for that matter). Has lead to a lot of improvements in the past, often things I do not think of.

I coded up a user preference with a simple toggle for the headlook based on your hardware last night. Hopefully test it out later today. I have simply set it up to toggle the mapping of the TrackIR Center toggle on the Throttle to change to ResetHMD for VR or if you have neither for it to default to built in headlook center.

I would be interested to know what chat updates you made too, if you don't mind sharing? TBH the ones I have in there now I am not 100% happy with either, but I seem to be terrible coming up with good alternatives lol.

Fantastic work :)

My chat updates are rather specific to the context of my player group and superpower affiliation, so I don't think they are particularly applicable broadly. I split it in hostile with stuff like "This is AEDC protected space, CMDR, please state your intentions", "Die Fed Scum", etc., neutral/friendly for strangers (greetings, bits of info on AEDC) and in-group hails.

What's maybe more useful is explain how I update them, with little chance of error:

1. write out your desired message in a separate file
2. copy/paste it right underneath
3. take a fragment of an existing message, and copy the bit between two letters (i.e. from closing ' to opening ' for the next letter)
4. At the start of your message type " PULSE+' " in front of it << double check from an existing message
5. Now paste this copied fragment after each letter, including the last one, but remove it till the last comma, so you end up with something that ends D(xx),
6. Now go through all the D(xx) pieces, and make sure it is set to 50 for a capital letter, 15 for a non-repeated lower-case letter, () for the first of a repeated letter, any white space, or punctuation mark (!, ?, ., ,, etc.)
7. copy all this in place of an existing message
8. copy the original written message (which should still be unmodified), and copy it where in the script currently the comment/message is included.

Hope that helps!
 
Thanks for getting back to me :)

Ah gotcha, yeah I am looking for more general chat responses I guess, something that might suit most people as a starting point. Considered setting up a set of Wings responses and another set for Multicrew but don't do much multiplayer myself so not sure how much others would use either. Anyways, the default ones that are in there already cover a lot of general things even if they may be badly written lol :p WIP...
 
Back
Top Bottom