20 replies to this topic

[Guided Bullets]

i wish when i press P, my mech POWERS ON. Not toggle the power on.

in some instances, my mech shutsdown, then very quickly i press P to power on, the mech turns on, but turns off right after that.

anyone else has the same problem?

[Lancer Deistler]

There is a queue function to p implementet since Patch 1.2.182. If you just tap the key once it shouldn't shutdown after powering up. Maybe your keyboard registers the tapping wrong? You should check this. Otherwise send a ticket: http://mwomercs.com/support

[Redshift2k5]

I just never touch the P button

ever

Hasn't given me any trouble yet

[Beeman]

Well, O is the override button by default, isn't it? You should be using the override button to override thermal-induced shutdown.

[riverslq]

don't bother
they're not going to fix it
their words
its as intended, like ecm.
they're not really going to listen.

[Kadaje]

I've ran into this, you either want to 'override' before shutdown, or just ride it out. More often than not it does power me down after the heat wearing off allows me to power up. I remapped the 'Override' command to the 'E' key so when i hear the heat warning and know im about to overheat i just tap 'e' and it overrides for 5 seconds, if I miss it I just ride down the shutdown and hope it's short.

[Vahnn]

Rebound F to Shutdown, left shift to Override.

Awwwwwwwww yeah!

[Guided Bullets]

Yes, its just once.

Just that when you overheat slightly, your mech powers off then powers on automatically. But at this very point, you press P, but instead of turning on, it turns off (because your mech is at the 'ON' state).

[FrostPaw]

Yes this happens to me too, it's that nagging doubt that if you don't press it you're sitting there for longer than you need to.

Actually I believe if you allow yourself to shutdown and passively do nothing but rage at the screen for not spamming that override key hard enough, it will power back up with the minimum amount of shutdown time anyway. It's just really hard to sit there passively during a fire fight.

Still, it's a ******** system. Why the power key needs to be queued up is beyond me, why the override button needs to be repressed because it only lasts 5 seconds is also a mystery. People who design game controls.....they're some weird alien brained hybrid of common sense sometimes.

[Guided Bullets]

I suggest P for power on ONLY. I mean WHO powers off their mechs????

Then for those rare instances where you have to power off the mech, SHIFT+P does it.

[dario03]

Guided Bullets, on 24 February 2013 - 04:32 AM, said:

Yes, its just once.

Just that when you overheat slightly, your mech powers off then powers on automatically. But at this very point, you press P, but instead of turning on, it turns off (because your mech is at the 'ON' state).

I'm gonna go with this. I've had it happen a few times and it seemed weird on a couple of them but for the most part I think its from just waiting to long to hit P. So now I just either wait or instantly hit O then P.

[Moonsavage]

I think it's a case of the mech turning itself on just before we press "P" - and the "P" shuts it down again.

[El Penguin]

I had this issue before but I think I either got the hang of it or it just doesn't happen to me anymore. If you overheated just barely and forgot to override before, just press "p" once during the shutdown animation and it'll start back up right after it's done shutting down. I haven't had a issue with it anymore honestly. Just be careful pressing "p" when powering back up. Like others said, it may shut you back down.

[pistolero]

yes it happens regulary

makes me wonder if those things get ever "playtested" before they are released at all

edit:

if it is to difficult to keep a working system ( like before the implementation of the new system ) in the game

why not make 2 different keys : 1 for power down and 1 for power up ?

Edited by pistolero, 24 February 2013 - 05:33 AM.

[Asmosis]

I always seem to get stuck in a power down loop. Adding the ability to queue a power down while powering up was a stupid decision when you factor lag into the equation.

If im pressing P (or O or w/e) i've already queued a power down before i even begin to power up. I have no idea if the server accepted my power up request because it seems to ignore it unless i press it 5 or 6 times.

I have no idea why they didnt just make it:

P = power down, if powered down does nothing.
O = override, if powered down, powers back up.

one button should serve one function. having the same button perform opposite functions then giving it hte ability to queue is just bad. If they absolutely MUST have power up/down on the same key there should be a 2 SECOND delay AFTER you have powerd up before it powers down again. It *definitely* should not queue it before you have even powered on.

I mean seriously, who accidently powers up when they are powered down and needs to shutdown immediately? I can't even think of a scenario where that series of actions would be useful.

[Sturmbringer]

you guys DO realize that when youre overheated you have to press O and NOT P button right ?

man.. those kids nowadays..

[El Penguin]

Sturmbringer, on 24 February 2013 - 05:47 AM, said:

you guys DO realize that when youre overheated you have to press O and NOT P button right ?

man.. those kids nowadays..

Actually you press P to control if you want to power down or up. Pressing "o" disables the auto shutdown for 5 seconds so if you barely skim over 100% heat you can avoid shutting down and also any damage taken from it.

[Lightfoot]

There seems to me anyway to be a delay in shutdown/startup now. Press P once and wait........ 3-4 seconds for the action to complete. Override Automatic Shutdown is faster, never tried it to start-up from a initiated shutdown.

[D Isbell]

Asmosis, on 24 February 2013 - 05:36 AM, said:

I always seem to get stuck in a power down loop. Adding the ability to queue a power down while powering up was a stupid decision when you factor lag into the equation.

If im pressing P (or O or w/e) i've already queued a power down before i even begin to power up. I have no idea if the server accepted my power up request because it seems to ignore it unless i press it 5 or 6 times.

I have no idea why they didnt just make it:

P = power down, if powered down does nothing.
O = override, if powered down, powers back up.

one button should serve one function. having the same button perform opposite functions then giving it hte ability to queue is just bad. If they absolutely MUST have power up/down on the same key there should be a 2 SECOND delay AFTER you have powerd up before it powers down again. It *definitely* should not queue it before you have even powered on.

I mean seriously, who accidently powers up when they are powered down and needs to shutdown immediately? I can't even think of a scenario where that series of actions would be useful.

This is my thought exactly. If you're overheating, press O. If you catch it in time, you get to run hot, if not, you'll start to power up ASAP. P can just be power off. Or if they want, P could still cycle power, but O could be used to power on as well, at least during shutdown. I guess the only question this leaves is: Do you want the 5 seconds of override in effect the moment you power up from an overheat shutdown if using O?

[Kaspirikay]

New heat system is lame.