Hmmm...

switching from a DXInput event to a keystroke didn't change the behaviour, and the same problem was present in the latest build of the 2.3 beta, which squashed a similar bug.

Here's my script:

Code:
include "target.tmh"
int main()
{
	Configure(&HCougar, MODE_EXCLUDED);
	Configure(&Joystick, MODE_EXCLUDED);
	Configure(&Throttle, MODE_EXCLUDED);
	Configure(&T16000L, MODE_EXCLUDED);
	Configure(&LMFD, MODE_EXCLUDED);
	Configure(&RMFD, MODE_EXCLUDED);
	Configure(&TFRPRudder, MODE_EXCLUDED);
	Configure(&TWCSThrottle, MODE_EXCLUDED);
	if(Init(&EventHandle)) return 1;
	SetKBRate(32, 50);
	SetKBLayout(KB_ENG);
	MapKey(&T16000, H1U, PULSE+DXHATUP);
	MapKey(&T16000, H1R, PULSE+DXHATRIGHT);
	MapKey(&T16000, H1D, PULSE+DXHATDOWN);
	MapKey(&T16000, H1L, PULSE+DXHATLEFT);
	MapAxis(&T16000, JOYX, DX_X_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
	SetSCurve(&T16000, JOYX, 0, 0, 0, 3, 0);
	MapAxis(&T16000, JOYY, DX_Y_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
	SetSCurve(&T16000, JOYY, 0, 0, 0, 3, 0);
	MapAxis(&T16000, RUDDER, DX_ZROT_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
	SetSCurve(&T16000, RUDDER, 0, 0, 0, 2, 0);
	MapAxis(&T16000, THR, DX_SLIDER_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);
	SetSCurve(&T16000, THR, 0, 0, 0, 0, 0);

}
int EventHandle(int type, alias o, int x)
{
	DefaultMapping(&o, x);
}

It doesn't work the way you want to because you have it on a pulse. Because of that, when you press a hat direction, it sends only one pulse, even if you keep the button held down. You need to put the button on Hold mode. That way it simulates a key press and sends many pulses when you have the button pressed down. This makes the menu scrolling a lot more comfortable. :)

I think the button setting is on hold by default, so the correct setup would be:

MapKey(&T16000, H1U,DXHATUP);
MapKey(&T16000, H1R,DXHATRIGHT);
MapKey(&T16000, H1D,DXHATDOWN);
MapKey(&T16000, H1L,DXHATLEFT);

Quote from the TARGET user manual:

The Type field defines the type of behavior for the key combination:
 Pulse simulates a brief (temporary) press on the keyboard, even if the button remains activated or in the
“on” position.
 Hold simulates pressing and holding the keyboard keys until the button is released.
 Press simulates a continuous press on the key combination, even if the joystick button is released.
 Release releases a combination of keys that has been “pressed” before.

Hope you get it working.

E: typos.
 
Last edited:
Great profile Aussiedroid.

May I ask, what's the key sequence for an auto docking request?

It depends on what keys you have bound to UI navigation.
For me it's:
1 - Left UI
2 - Contact UI
3 - System UI
4 - Right UI
QWEASD - UI Navigation
SPACE - confirm
Make sure left UI is on first page (Navigation). At the end (Q - Q) it returns there.
Docking Request: 1 - E - E - SPACE - S - SPACE - Q - Q - 1
 
Last edited:
Great profile Aussiedroid.

May I ask, what's the key sequence for an auto docking request?

Thanks RAJA!

This is the main sequence I use:

Code:
	mRequestDock = CHAIN(
			LOCK+PULSE+TargetPanel, D(),
			PULSE+UINextPanel, D(),														
			PULSE+UINextPanel, D(),
			PULSE+UISelect, D(),
			PULSE+UIDown, D(),
			PULSE+UISelect, D(),
			PULSE+UIPrevPanel, D(),
			PULSE+UIPrevPanel, D(),
			PULSE+UIBack, LOCK);

D() is set to 75ms
 
It depends on what keys you have bound to UI navigation.
For me it's:
1 - Left UI
2 - Contact UI
3 - System UI
4 - Right UI
QWEASD - UI Navigation
SPACE - confirm
Make sure left UI is on first page (Navigation). At the end (Q - Q) it returns there.
Docking Request: 1 - E - E - SPACE - S - SPACE - Q - Q - 1


Hmm, so it's not already bound to a key as a macro? I was looking for a single keypress or modifier combo in the profile that is pre-programmed to do this. I've looked through the keymap in the openeing post, but must have missed it.

- - - Updated - - -

Thanks RAJA!

This is the main sequence I use:

Code:
	mRequestDock = CHAIN(
			LOCK+PULSE+TargetPanel, D(),
			PULSE+UINextPanel, D(),														
			PULSE+UINextPanel, D(),
			PULSE+UISelect, D(),
			PULSE+UIDown, D(),
			PULSE+UISelect, D(),
			PULSE+UIPrevPanel, D(),
			PULSE+UIPrevPanel, D(),
			PULSE+UIBack, LOCK);

D() is set to 75ms

Thanks, dude. I just havent managed to work out which joystick/throttle button I need to push to initiate the sequence.
 
Thanks, dude. I just havent managed to work out which joystick/throttle button I need to push to initiate the sequence.

No problems. That is just the main macro code with the key press sequence, the rest needs to be coded too for it to work first. :)

You will need to map the macro to which ever button you want in your script. You can see an example in my script, but a simplified version would be something like:

MapKey(&Throttle, APENG, PULSE+mRequestDock);

Also will need to create the function (such as - int initCustomCommands()) to house the macro & initialise the variable (int mRequestDock) & initialise the function (initCustomTextCommands();).

Each of the key map definitions (UINextPanel etc) will also need to be set in your key map settings file, example:

define UINextPanel USB[0x08] // E

Good luck!
 
Great Work on this. Thank you for the days spent on this script as well as the detailed examples and explanations. Will give it a whirl.

Cheers
 
Last edited:
Download Now Available!

Update 2.3.0: COMMANDERS UPDATE

List of Changes:

NEW: Added All new 2.3 Keybindings for Multicrew, HoloME, Camera Suite & Friends View.
NEW: Added Text Chat Macro Presets. (3 Modes for a total of 12 presets, depending on Pinky Toggle position)
NEW: Supercruise on 100% Throttle added! (HOLD Pinky Trigger for Supercruise & CMS Hat Switch for Hypercruise)
NEW: Explorers Rejoice! Primary & Secondary 'Repeater Fire' Mode Added! Thumb Modifier + Pri/Sec fire to lock ON. Fire again to disable.
NEW: SRV Handbrake on Throttle Idle Indent returns! (Now working!)
NEW: Added New Signal Lights Macros to Autopilot Engage button. (Short will flash lights 3x. Long Mode will flash 6x. For a-bit-a-fun:) )
NEW: Added Alternative Mapping for Std 1-Tier & 2-Tier PIP Control. (Short press remains 1 PIP at a time, while Long Press changes to 4 PIPs and 1 in each of the minor PIPs. No extra long press for those that struggle with the 3-Tier timings.)
NEW: Added default code for Thrustmaster MFD Panels & T.Flight Rudder (Disabled by Default & Untested!)
NEW: Introduced User Preferences section in the AD_EDSettings file for easy script customisation for alternative or optional settings. Check it out!

IMPROVEMENT: Added Optional Auto-Chaff & Engine Boost on Escape Vector Macro.
IMPROVEMENT: Moved Retract/Deploy hardpoints to the Throttle Arm (Red Button), plus Escape Vector Macro with Pinky Trigger Modifier.
IMPROVEMENT: Moved Alternative Flight Control on Joystick CMS Hat to FA Off Hold location on the Throttle.
IMPROVEMENT: Moved FA Off Hold to Down on Coolie Hat Switch for easier access to combine with latteral thrusters.
IMPROVEMENT: Moved Galaxy map panning to thumb hatswitch on throttle, and rotate to other hat. Moved Galaxy map up/down to thumb.
IMPROVEMENT: Moved Headlook Center to Joystick, Pinky Trigger plus Up on CMS Hat.
IMPROVEMENT: Combo fire Modifier moved to Pinky Trigger Modifier, plus Primary Fire.
IMPROVEMENT: Redesigned the script loading diagnostic print out to better fit the default TARGET GUI window.
IMPROVEMENT: Removed duplicate Next in Route on Joystick.

FIXED: SRV Boost on Throttle Arm Slew Control.
FIXED: A number of mappings that lost configs & updated some keyboard shortcuts.
FIXED: Updated to latest HCS Voicepack default keys (~99% of keys now mapped).
FIXED: Alternative Flight Control axis directions as they are now invertable in 2.3!
FIXED: Macro Startup Cleanup.

CODE CLEANUP: Moved Cargo Scoop code into a function.
CODE CLEANUP: Moved OSD toggle into a Macro (ShowGameStats).
CODE CLEANUP: Added TARGET print out for Throttle Presets & Cargo Scoop, and improved text.
CODE CLEANUP: Added link to related Frontier Forums Thread in script info section.
CODE CLEANUP: Revalidated mappings post 2.3 official release. Test OK.


** Please visit the ModDB link in the OP to get the latest version **
 
Last edited:
I was wondering just the other day what type of revisions you were going to make for 2.3; especially curious how you setup the new camera suite. The addition of text chat macros are a nice touch, (I am presently doing similar with the G-keys on keyboard).
Good job and thanks for sharing.
 
Last edited:
Cheers Mister Tang & RAJA!

Still feel I need more time with the camera, but think I have come up with something fairly usable/intuitive to suit the profile for now. :)
 
Thank you for a fantastic profile..
One minor issue, the trimmed throttle ( -75% - 75%) seems more like -50% - 50%
If I switch to this, then hit numpad 3 (75%) the throttle bar jumps up.....in vr this is rather annoying, as fumbling for keyboard is a pain, meaning ive had to bind 75% to another button on the throttle, were ideally id just like to switch throttle curve as I approach a station.
 
Thank you for a fantastic profile..
One minor issue, the trimmed throttle ( -75% - 75%) seems more like -50% - 50%
If I switch to this, then hit numpad 3 (75%) the throttle bar jumps up.....in vr this is rather annoying, as fumbling for keyboard is a pain, meaning ive had to bind 75% to another button on the throttle, were ideally id just like to switch throttle curve as I approach a station.

Hey evilscoop,

Thanks for the feedback!

Just to check first, did you change in the ADEDSettings.tmh file to include mThrottleTrimmed on one of the Throttle choices? It is not used by default, and has the mThrottlePrecision set instead.

So anyways I had a look at the trimmed throttle range and I think you are right. See "ADEDMacros v2.3.tmh" (See the SetSCurve command)

Current Code:

Code:
mThrottleTrimmed = EXEC(
			"TrimDXAxis(DX_Z_AXIS, SET(0));"
			[B]"SetSCurve(&Throttle, THR_RIGHT, -50, 0, -50, 0);"[/B]
			"printf("Throttle Profile: TRIMMED [-75 -> 75]\\x0a");"
			"SetThrottle();");


I think this will need to be changed to (sets 25% instead of 50% end deadzone):

Code:
			[B]"SetSCurve(&Throttle, THR_RIGHT, -25, 0, -25, 0);"[/B]

I'll fix this in my next version & try to test it out today my end. In mean time just change the -50 to -25 in the SetSCurve command and should be working for you.

Cheers!
AD
 
Last edited:
Yeah changed to trimmed, trying custom atm... -100 to 80%
ahhh I didnt understand Scurve well enough, explains why my change to -75 worked out badly.....lol
will try that now and let you know

---------------------------
Its better and will do, but still not the same as num pad 3...oddly

On the steam post you hinted at throttle presets already setup, but hidden...and chance you can say were ?....ive hunted the script but cant find them....
 
Last edited:
Yeah changed to trimmed, trying custom atm... -100 to 80%
ahhh I didnt understand Scurve well enough, explains why my change to -75 worked out badly.....lol
will try that now and let you know

---------------------------
Its better and will do, but still not the same as num pad 3...oddly

On the steam post you hinted at throttle presets already setup, but hidden...and chance you can say were ?....ive hunted the script but cant find them....

No worries, I just put together a point update to fix this that should now be available to download too if you haven't edited yet. :)

The Throttle Presets themselves are in the AD_EDMacros file in the initSetThrottleCurves(). The three presets (UP, Middle, DOWN) can be configured in the AD_EDSettings file. Rename any of the Toggle positions from one of the 5 listed in the comments to the right.




Update 2.3.1: Minor Fix/Changes Release

IMPROVEMENT: Swapped 3 way Toggle for Joystick & Throttle Preset Curves (More logical layout & easier Joystick control when using FAOff)
IMPROVEMENT: Alternate 2 Tier PIP Macros mapped on Hold.

FIXED: 75% Trimmed Throttle Preset range fixed.

CODE CLEANUP: Additional Comments added/cleaned up.

OTHER: Chat Text Macro Reference Map added to pack.

Enjoy.
 
Back
Top Bottom