Probably a dumb that's question easily answered, but it's hard to come up with search terms that don't produce way too many hits to be of use...
From a stop, how many times do I have to hit 'w' for full throttle forward? How many times 's' for full back throttle from a stop?
TIA,
-Loc
0
Throttle Control on Keyboard
Started by Loc Nar, Oct 29 2012 07:32 PM
7 replies to this topic
#1
Posted 29 October 2012 - 07:32 PM
#2
Posted 29 October 2012 - 07:53 PM
just hold it down till it goes all the way up
#3
Posted 29 October 2012 - 08:18 PM
Thanks, I understand that much at least. While I can use the actual analog throttle once I tweak my .cfg files, I am programming a joystick profile in TARGET (Thrustmaster's incredible mouse/keyboard emulator program) for my heavily modified (see mechpit post...) Thrustmaster Cougar HOTAS. The reason for this is to give me a 'virtual throttle' option. With TARGET, I can program analog axes to produce digital events, and I already have a scheme that goes forward/x/backward to full throttle. However, I can program exactly how many keystrokes in a chain, and also assign specific values to each zone I divide the axis into so I can come up with a nicely tuned variable output of w,x, and s pulses.
On that note, I am almost done with a variable Left/Right scheme for rudder pedals to work better than full left (20 pulses per second, at 32ms each by default...), null and rull right. My scheme is essentially a pulse width modulation deal that changes the pulse rate depending on how for the rudder (or any analog axis it is assigned to...) pedals are depressed.
The throttle works differently however, and relies on a predetermined number of keystrokes to ratchet up to full throttle and back down etc. I need to know how many for this to work, hence my question...
A lot more detail on this and more in my my mechpit thread... http://mwomercs.com/...440-my-mechpit/
On that note, I am almost done with a variable Left/Right scheme for rudder pedals to work better than full left (20 pulses per second, at 32ms each by default...), null and rull right. My scheme is essentially a pulse width modulation deal that changes the pulse rate depending on how for the rudder (or any analog axis it is assigned to...) pedals are depressed.
The throttle works differently however, and relies on a predetermined number of keystrokes to ratchet up to full throttle and back down etc. I need to know how many for this to work, hence my question...
A lot more detail on this and more in my my mechpit thread... http://mwomercs.com/...440-my-mechpit/
#4
Posted 30 October 2012 - 01:25 AM
it would depend on what the impulse length is. As the indicator moves with length of time the key is pressed. I would suggest setting it to 100 and adjusting it from there. 100 gets you to max half throttle, then set it to 200, which get to max then try 190, still max then try 180, not enough try 185. just zero in on it. We can't answer because we don't know what the impulse length of the command is, nor the repeat latency. I would so love anything approaching analog turning.
#5
Posted 30 October 2012 - 08:28 AM
I tried this briefly to simulate an analog rudder, and the 'hold' time for the key is critical.
I'm confused why you don't go right to the analog control. It's easy to setup in game or with the defaultProfile.xml workaround.
See this post: http://mwomercs.com/...-configuration/
I'm confused why you don't go right to the analog control. It's easy to setup in game or with the defaultProfile.xml workaround.
See this post: http://mwomercs.com/...-configuration/
#6
Posted 30 October 2012 - 10:21 AM
I am not having difficulties with getting my controls working; I have my analog throttle working just fine. I'm just including a user selectable 'virtual throttle' scheme as well in the TARGET program I am making, which I am going to shortly making available to anyone who wants it. By default the analog throttle is enabled in my program.
I am a cockpit builder, so I care about details of user interface, whether I am currently utilizing it or not. The reason how long holding the key for affects throttle, is because by default holding a key generates 20 keystrokes per second (which by default are 32 milliseconds apiece). If you just tap the key though, there is definitely an exact number to ratchet up to full from a stop. TARGET allows me to control both the duration and the delay, and I'm exploring permutations of controls. If someone actually knows the answer, cool, but I'm not looking for help to solve problems I am not having...
Again, I am not having difficulty with my throttle and do not need 'solutions'. For academic purposes, I would like to know know many strokes of the 'w' it takes to get to full forward and how many 's' strokes to get to full reverse from a stop.
-Loc
http://mwomercs.com/...440-my-mechpit/
I am a cockpit builder, so I care about details of user interface, whether I am currently utilizing it or not. The reason how long holding the key for affects throttle, is because by default holding a key generates 20 keystrokes per second (which by default are 32 milliseconds apiece). If you just tap the key though, there is definitely an exact number to ratchet up to full from a stop. TARGET allows me to control both the duration and the delay, and I'm exploring permutations of controls. If someone actually knows the answer, cool, but I'm not looking for help to solve problems I am not having...
Again, I am not having difficulty with my throttle and do not need 'solutions'. For academic purposes, I would like to know know many strokes of the 'w' it takes to get to full forward and how many 's' strokes to get to full reverse from a stop.
-Loc
http://mwomercs.com/...440-my-mechpit/
#7
Posted 01 January 2013 - 12:52 PM
Yeah, currently not possible going about it that way.
If you could get GlovePIE / PPJoy virtual axes working in MWO, I could probably bodge it for you by creating virtual axis and mapping speed to that (See proof of concept here).
As I said in that thread, I suspect it would work but only via manually setting up actionmaps.xml etc. Either that or we may need the PPJoy "lowid hack" to make the virtual joystick appear as joystick 0, I didn't try that.
If you could get GlovePIE / PPJoy virtual axes working in MWO, I could probably bodge it for you by creating virtual axis and mapping speed to that (See proof of concept here).
As I said in that thread, I suspect it would work but only via manually setting up actionmaps.xml etc. Either that or we may need the PPJoy "lowid hack" to make the virtual joystick appear as joystick 0, I didn't try that.
#8
Posted 15 January 2013 - 03:38 AM
I have now found a replacement for PPJoy that works with MWO, and have posted a keyboard throttle as proof-of-concept code in this thread.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users