I currently use a G940 throttle/pedals and mouse combo when playing MW:O.
The issue is that when you switch to map or go to chat, the throttle drops to zero. I had this issue in a previous patch and I believe it was rectified. I guess something reintroduced it.
A fix would be appreciated as keeping up with the team is a real problem if commanding.


Throttle Cuts To Zero When Going Into Chat Or Map
Started by Floydii, Apr 20 2013 01:49 PM
8 replies to this topic
#1
Posted 20 April 2013 - 01:49 PM
#2
Posted 20 April 2013 - 02:20 PM
Floydii, on 20 April 2013 - 01:49 PM, said:
I currently use a G940 throttle/pedals and mouse combo when playing MW:O.
The issue is that when you switch to map or go to chat, the throttle drops to zero. I had this issue in a previous patch and I believe it was rectified. I guess something reintroduced it.
A fix would be appreciated as keeping up with the team is a real problem if commanding.
The issue is that when you switch to map or go to chat, the throttle drops to zero. I had this issue in a previous patch and I believe it was rectified. I guess something reintroduced it.
A fix would be appreciated as keeping up with the team is a real problem if commanding.
Happens here too with simple joystick details in My profile
#3
Posted 20 April 2013 - 04:04 PM
I also have this happen to me. also happens when Im pressing tab. also some of the buttons do not map to my thrustmaster hotas x. such as center to legs and scoreboard.
#4
Posted 22 April 2013 - 04:23 AM
Also happens to me when using the numpad keys to set throttle level. I can team chat fine but global chat cuts throttle. Might be to do with the new lance chat option? Didn't happen last patch.
#5
Posted 22 April 2013 - 04:34 AM
Lagahan, on 22 April 2013 - 04:23 AM, said:
Also happens to me when using the numpad keys to set throttle level. I can team chat fine but global chat cuts throttle. Might be to do with the new lance chat option? Didn't happen last patch.
Actually it started with the last patch and is still there...annoying.
#6
Posted 23 April 2013 - 12:27 AM
Since the 3/19 patch, eight of the controls which worked prior to the patch will not function. Also, when checking map or typing text, mech comes to complete stop. Tried some player fixes, and staff fixes. None have worked.
#7
Posted 23 April 2013 - 01:22 AM
Same here.
I play old fashioned KB/Mouse only and about 70% of the time the throttle will drop to 0 when I call up the battle map (B ). About 1 time in 4 if I have used the number pad to set speed, I will remain at the set speed. But holding down the "W" key with the map up stops you dead.
This is particularly annoying as in a voiceless PUG seeing which way your fellows PUGers are flocking can help get in a not too despicable position. However if its at the cost of speed your OUT of position ...
Edit forgot to turn OFF smileys...
I play old fashioned KB/Mouse only and about 70% of the time the throttle will drop to 0 when I call up the battle map (B ). About 1 time in 4 if I have used the number pad to set speed, I will remain at the set speed. But holding down the "W" key with the map up stops you dead.
This is particularly annoying as in a voiceless PUG seeing which way your fellows PUGers are flocking can help get in a not too despicable position. However if its at the cost of speed your OUT of position ...
Edit forgot to turn OFF smileys...
Edited by Caswallon, 23 April 2013 - 01:23 AM.
#8
Posted 23 April 2013 - 01:27 AM
I used a Joystick with throttle and had the same issue.
If I set it to the middle (0%) and then used the keyboard to accelerate (with throttle decay off), the speed would stay in any "screen".
So It looks like the joysticks "emulate" a keypress for the speed and that doesnt work in chat/score/map screens.
If I set it to the middle (0%) and then used the keyboard to accelerate (with throttle decay off), the speed would stay in any "screen".
So It looks like the joysticks "emulate" a keypress for the speed and that doesnt work in chat/score/map screens.
#9
Posted 23 April 2013 - 04:40 AM
reporting this one also. Happened so far only once, and it was constant bug till client got restarted.
I am using Kb with mouse.
I am using Kb with mouse.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users