looks great, however as I'm also using VA all the reprogramming will be too much to me at this stage
ps: Sry Aussiedroid to be off topic
Hi Aussiedroid,
Thanks for reply
I agree to use button on the HOTAS using Target, there has many combine key to get this jobs done and it easy to do.
for version 2.3 if your code cleanups that will have a lot of new coming for try to use it because your work has a big advantage for dynamic curve profile switching.
It is a deep learning curve for players who don't have coding experience but payoff is a big advantage
I'm also playing around with an autofire option in my current beta build. Similar to your setup, using a modifier and fire button to trigger, then stays held until you press the fire button again. Seems to work pretty well so far, but also playing around with some timed options, with a fixed hold time to see if that may be better. Still a bit on the fence, but I think I might go with an open solution leaving disengagement manual so it is more useful for both exploration and combat if situation calls for it. Hi Aussiedroid,
Thanks for reply
I agree to use button on the HOTAS using Target, there has many combine key to get this jobs done and it easy to do.
for version 2.3 if your code cleanups that will have a lot of new coming for try to use it because your work has a big advantage for dynamic curve profile switching.
It is a deep learning curve for players who don't have coding experience but payoff is a big advantage
Cheers
MapKey(&DEVICE, BUTTON_NAME, Keystroke);
KeyAxis(&TWCSThrottle, DX_THROTTLE_AXIS, 0, AXMAP2(9, PULSE+KP9, PULSE+KP8, PULSE+KP7, PULSE+KP6, PULSE+KP5, PULSE+KP4, PULSE+KP3, PULSE+KP2, PULSE+KP1));MapAxis(&Input device, physical axis name, dx_axis name, option1, option2);MapAxis(&Throttle, THR_RIGHT, DX_Z_AXIS, AXIS_NORMAL, MAP_ABSOLUTE);KeyAxis(&Throttle, THR_RIGHT, 0, AXMAP2(9, PULSE+KP9, PULSE+KP8, PULSE+KP7, PULSE+KP6, PULSE+KP5, PULSE+KP4, PULSE+KP3, PULSE+KP2, PULSE+KP1));That solved it! It was TTHR. Thanks a lot man!
Edit: Throttle control works so much better like this.
Thanks!CMDR Touille & Mr. Gr3y to the rescue again
Interesting alternative config on the throttle DuckingHostile! I could see how that could work well. Personally, I like the finer detail/control, but I do set a reasonable deadzone (perhaps a bit more than I should) to ensure I have a clear, easy to hit target in Full range. Always great to see what others come up with!
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);
}