5 replies to this topic

[Sythiss]

so hi there first.
with mechwarrior so close to coming out i thought i would grab up the chance to buy a friends thrustmaster a10 controller.
now im staring at the manual and such but i have never been one for flight simulators.
My basic question is this. According to dev blog 5, W throttles you up and S throttles you down. But how the heck do i translate that into TARGET script. not only that, but it doesn’t have a middle throttle, its down or up like a planes throttle, Is there a way to hold a button and have the throttle reversed.
A silly question for some i imagine. But im trying to learn these things so i dont have to struggle when we get access.
that or will people be creating scripts that one could download ??

[Romulus Stahl]

Most games/sims use the throttle as a axis input, you would not have to assign a key input to it. I can't speak for MWO but I imagine it will work much the same.

[Uri Brauer]

It has been said that joystick support isn't in yet... so throttle may be as described for the time being.

I'll be mapping it onto an axis of my left T.16000M in TARGET, so you can refer to that. Not sure if I'll just go for the lazy option (W / deadzone / S) or something more complex (W pressed 90% of the time when the stick is 90% forward etc... which I think can be done...). I'm not going to do that until I'm in beta, though.

[Sythiss]

firstly YAY house stiener. secondly i guess ill have to wait for the beta to be open to everyone. At worst ive programmed it now. Several days and much re reading of the manual have given me some insight. But at the same token im sure people far more programing minded than me will upload target info

[Uri Brauer]

KeyAxis and AXMAP2 seem to be the best bet.

OK, simple version with three zones controlling the throttle keys:

KeyAxis(&T16001, JOYY, 0, AXMAP2(3, 'w', 0, 's'));

Obviously you'll use different entries in the first two fields...


This version looks like it should give a halfway position...

KeyAxis(&T16001, JOYY, 0, AXMAP2(5, 'w', REXEC(1, 50, "ActKey(PULSE+KEYON+'w');"), 0, REXEC(2, 50, "ActKey(PULSE+KEYON+'s');"), 's'));

...but I can't tell if it'll work or not. Spamming the 'w' key every 50ms might cause problems. A more studied version can probably be built using functions to press and release the button more slowly, but I can't be bothered for what should be a temporary solution.

Edited by Uri Brauer, 24 July 2012 - 02:27 PM.

[Serpentstar]

Sythiss, if you do the programming with TARGET, you can assign the functions the game is looking for to your specific joystick. This is what I am currently doing. I still don't have ungrouped weapon fire or reverse enabled. (or chat either) but this is my current setup for my Warthog. Once I have a good handle on this, I will probably move over to PGP so I can use the rest of my devices (Rudders and TrackIR)

Never mind that, way to long. I can provide you my fcf file if you want, but that probably won't help you much since you don't have the Warthog.

Edited by Serpentstar, 25 July 2012 - 02:45 PM.