throttle keeps ramping to 100 percent, want to move "zero" throttle

[onesoul]

I could use some throttle help.

I have two problem:
1) throttle steadily ramping to 100 despite the actual throttle position.  In other words, when I set 50% forward throttle, I expect the mech to HOLD 50% throttle.  Instead, the mech throttle (light green line) steadily climbs and of course the mech speed (green bar) climbs too 100%.

2) For those with flight throttles, "zero" throttle is usually pulled pretty far back (about -700).  Is there any way for me to make -700 be "zero" in MWLL?  Thus -700 to 1000 is forward and -700 to -1000 is reverse.

I've already tried the 'k' ramping key toggle, but it apparently has no effect.

I'm using a Saitek X52 joystick and throttle (http://www.saitek.com/uk/prod/x52.html) with a pretty plain config.
The Saitek throttle profile is default (no bands) and the values are -1000 to 1000.
Actionmapper joystick Z axis has the same range (-1000 to 1000), a small dead zone and 1.0 sensitivity.
(So zero throttle is handle straight up.  Back for reverse, forward for forward).

If anyone wants my x52 config and actionmapper to save considerable configuration effort (and/or help me troubleshoot), just ask.  Who handles the wiki?  I think it just has an x52Pro config.

thanks,
onesoul

UPDATE 20110802 (so you don't have to search the entire thread):  Fixed the ramping with (TLL)CapperDeluxe advice.  The actionmapper has a note for the (X) throttle entries of "For joysticks, use the Vehicle set throttle". That should read use ONLY the Vehicle set throttle value.  I had the invjoyz set everywhere I could find "throttle".  That was the problem.

I returned sensitivity to 1.0.

I still had to use (X) turn left/right, (X) aim up/down, (X) bank left/right for the joystick.  The non-(X) wouldn't work with the joystick.  That works great, so no complaints.  Now I see why the Devs didn't rename (X) to (G).  I'm only 1 data point.  I don't know if other joysticks would produce results consistent with mine.

Unfortunately, the throttle sometimes doesn't work when the Mech is forcibly stopped (ex: hill too steep to climb).  I have to throttle back to 0 (or reverse) to get moving again.  Pretty sure I saw this is a bug.

Next task is getting -700 to be zero throttle. 8-)

Thanks for the help everyone!  Now I can go get slaughtered faster!  See ya'll on the field!

[=CJW=YalK]

4 words:

Key Board and Mouse

I fiddled with a joy stick, even a Game pad at one point and finally went back home to the ole' KB and M

I had the same issue with the throttle and other problems so gave up....

Plus I played with a Keyboard for throttle for all other Mexhwarrior games so....went back to my roots

Sorry couldn't help more

[(TLL)CapperDeluxe]

for my throttle that same thing happened and I fixed it just by lowering the sensitivity value in the actionmapper. So if at 1.0 its still too sensitive try it down even lower, like 0.1.

[onesoul]

4 words:  Key Board and Mouse

Not really an option.

When I really got into Mechwarrior (I have the original Battletech, CityTech, Aerotech box sets) video games, I bought the Logitech Wingman 3D Force Feedback joystick and never looked back to keyboard for MW games.

Holy crap!  MW1 is available for download!  I played that old series (CH:I, CH:R) on my Tandy 1000TL.  It only had enough CPU power for a 3 'mech lance.  http://www.abandonia.com/en/games/471/Mechwarrior.htm

[onesoul]

for my throttle that same thing happened and I fixed it just by lowering the sensitivity value in the actionmapper. So if at 1.0 its still too sensitive try it down even lower, like 0.1.

The 0.1 sensitivity just really slowed the ramping rate, so it takes *forever* to reach full speed.
I set it to 0.7 as a balance but it still ramps.

So, not solved.

[CGB [CoffiNail]]

try for a sweet spot between .7 and .1?

[onesoul]

50% throttle should stop at 50% speed.  MW4 does it correctly.  Love MW:LL
but this is very annoying especially in fast mechs.

Why does the throttle keep climbing?

[(TLL)CapperDeluxe]

do you have your throttle axis only set on the Vehicle tab for set throttle value, or is it also set to one of the (X) throttle actions that are meant for the gamepad? because those can mess with a joystick throttle since they don't return to the origin when  you let go of it as a gamepad stick would.

[Spanish Inquisition]

It wouldn't kill you to just hit 5 on your numpad, would it?

[Spooky]

It wouldn't kill you to just hit 5 on your numpad, would it?

That's not a solution. If you have a throttle control on your joystick, you should definitely use it.

[onesoul]

do you have your throttle axis only set on the Vehicle tab for set throttle value, or is it also set to one of the (X) throttle actions that are meant for the gamepad? because those can mess with a joystick throttle since they don't return to the origin when  you let go of it as a gamepad stick would.

That's highly likely.  The actionmapper interface isn't intuitive.  A top level page to set defaults based on radio button input choice would be helpful.  ex:  keyboard, keyboard + joystick/mouse, keyboard + gamepad.

Are the (X) actions intended only for gamepad?

And for the actionmapper, I cannot assign the "center torso" action to anything, but the throttle is the 1st problem to solve.

[(TLL)CapperDeluxe]

do you have your throttle axis only set on the Vehicle tab for set throttle value, or is it also set to one of the (X) throttle actions that are meant for the gamepad? because those can mess with a joystick throttle since they don't return to the origin when  you let go of it as a gamepad stick would.

That's highly likely.  The actionmapper interface isn't intuitive.  A top level page to set defaults based on radio button input choice would be helpful.  ex:  keyboard, keyboard + joystick/mouse, keyboard + gamepad.

Are the (X) actions intended only for gamepad?

And for the actionmapper, I cannot assign the "center torso" action to anything, but the throttle is the 1st problem to solve.

not sure what you meant you cant assign the center torso to anything, it should be able to map to any button or key just not an axis. Maybe its the detect function thats not working when you try to press the button you're wanting?

the (X) actions are intended mostly for gamepad. Though a few will work quite well with a regular joystick, if not better. Its worth trying to use it for your pitch/yaw/turn type actions, however for throttle its a completely different type of input than a lever. Unless of course you plan to use the stick part for throttle as some do.

[onesoul]

Keypress autodetect completely hangs actionmapper.  I cant use it.  I cannot assign any thing to the center torso action.  Not keyboard.  Not joystick.  The center torso field always stays blank.   I havent tried editing the xml.

The (X) mostly used for gamepad explains the problem.  The actionmapper should have a tip about that. Its not obvious.

[~SJ~ Xarg Talasko]

How about renaming them (if possible) to something like (G) gamepad or (J) joystick? Or are those X_ Crysis parameters for non kb/m interfaces?

[onesoul]

UPDATE 20110802:  Fixed the ramping with (TLL)CapperDeluxe advice.  The actionmapper has a note for the (X) throttle entries of "For joysticks, use the Vehicle set throttle". That should read use ONLY the Vehicle set throttle value.  I had the invjoyz set everywhere I could find "throttle".  That was the problem.

I returned sensitivity to 1.0.

I still had to use (X) turn left/right, (X) aim up/down, (X) bank left/right for the joystick.  The non-(X) wouldn't work with the joystick.  That works great, so no complaints.  Now I see why the Devs didn't rename (X) to (G).  I'm only 1 data point.  I don't know if other joysticks would produce results consistent with mine.

Unfortunately, the throttle sometimes doesn't work when the Mech is forcibly stopped (ex: hill too steep to climb).  I have to throttle back to 0 (or reverse) to get moving again.  Pretty sure I saw this is a bug.

Next task is getting -700 to be zero throttle. 8-)

Thanks for the help everyone!  Now I can go get slaughtered faster!  See ya'll on the field!