Binding fwd/rev thruster control to analog

[Galaxian]

My weak search-fu didn't turn anything up so 'llI send out a ping for this one:

Is it possible to bind the Z axis (ship fwd/rev) thruster control to an analog input?

I've got the X and Y thrusters bound to the microstick on my Cougar and would like to bind Z thrusters to the Ant. elevation rotary for analog control.

Thanks

[Galaxian]

Thanks.

I have programming for the on/off actions already in place. Currently, rolling the knob fwd or back from the center detent 'holds' the thruster key down for the appropriate direction until I move it back to center, which 'releases' the key.

I'm looking for analog control, same as the X and Y thrusters so I can have variable inertial thruster output fwd/rev.

[Vice]

Variable forward/reverse control is managed with the main engine via the throttle control, so the IDS needs to be activated for that control to be enabled. It's helpful to keep the IDS on an easily accessible button so you can activate variable engine control when needed quickly. You can retain drift with the IDS on by holding the opposing drift thruster key/button, then just adjust throttle to where you want it. However, it's often easier (and faster) to rotate and use a lateral/vertical thruster or the afterburner with the IDS off, depending on circumstances.

[Galaxian]

Thanks for the replies. Good information.

However the implied answer to my original question of whether or not the fwd/reverse inertial thrusters can be bound to an analog control, like the vertical and lateral thrusters can *seems* to be 'no'.



I've been using Foxy for years and haven't tried out TARGET yet.

I'll post up my config on the interesting programming thread just for fun.

[Vice]

However the implied answer to my original question of whether or not the fwd/reverse inertial thrusters can be bound to an analog control, like the vertical and lateral thrusters can *seems* to be 'no'.

Correct, for static on/off controls, on/off input is needed. For variable control, throttle for main engine is required. Forward and reverse control is managed by the ship's engine, which operates differently from maneuvering thrusters, it is bound to the IDS. You can use the techniques detailed above to utilize variable forward/reverse control (or variable forward/reverse thruster control using lateral thrusters).

Some profiling software will let you map variable analog input to static key controls, but for the true variable control, throttle or angled maneuvering thrusters are needed.

[Galaxian]

Roger. Got it.

So.... If the fwd/rev thrusters are tied to the main engines, is it possible to maintain analog engine control, minus the speed cap imposed by IDS, while in Inertial, thus allowing variable accel/decel while IDS is disengaged?

I know it's asking for basically the same thing, but I had to ask....

And while I'm at it.....

which end of the tunnel does the smoke come out of......

ROFL

I did just get an idea though where I can use bands on an analog axis to simulate variable control with "press (hold for ) release" macros.




Thanks!



[Edited on 11-19-2010 by Galaxian]

[soulsacrifice]

Thing is, you can control the vertical and horizontal thrusters with both button input and axis input. I always thought it would make sense to have analogue input for forward and reverse thrust in inertial mode. The axis bound to thruster control isn't being used anyway and it could free up buttons for some people.