

#1
Posted 27 January 2013 - 01:31 AM
There is no clear indication when you should press P to power-up, so I tend to (Im sure others do too) press it multiple times, causing myself to get stuck in a permanent shutdown state, or power-up just to shut-down instantly again.
I suggest that "O" should perform as it used to as the ONLY and exclusive way to power-up from shut-down, and to act as it does now, to provide 5 seconds of 'grace' before shutting down.
"P" should only be used to shut-down and power-up during normal operation.
Much less confusion this way.
#2
Posted 27 January 2013 - 07:35 AM
Calimaw, on 27 January 2013 - 01:31 AM, said:
There is no clear indication when you should press P to power-up, so I tend to (Im sure others do too) press it multiple times, causing myself to get stuck in a permanent shutdown state, or power-up just to shut-down instantly again.
I suggest that "O" should perform as it used to as the ONLY and exclusive way to power-up from shut-down, and to act as it does now, to provide 5 seconds of 'grace' before shutting down.
"P" should only be used to shut-down and power-up during normal operation.
Much less confusion this way.
it is allready exactly how you want it. 'o' overrides heat shutdown, 'p' shuts the mech down or starts it up.
However, there is a bug that came with the last patch, that in SEEMS like your mech is still in overheat shutdown: the red flashing stays and no hud appears, but you can move and shoot. If you then press 'p' to shut down your mech and restart it afterwards, everything returns back to normal.
So yes, you are right, it's stupid the way it is right now, but it is like that because of a bug, not because 'p''s and 'o''s tasks aren't clear
#3
Posted 27 January 2013 - 07:58 AM
#4
Posted 27 January 2013 - 08:10 AM
#5
Posted 27 January 2013 - 03:31 PM
Should I first press override (not according to patch notes) or is this a bug?
#6
Posted 27 January 2013 - 03:33 PM
The new system is complex, un-intuitive and random.
Terrible changes.
#7
Posted 29 January 2013 - 11:32 PM
1) If the button is pressed BEFORE an automatic shutdown that the system does not perform an automatic shutdown within the next 5 seconds...
2) If the button is pressed during ANY time during an automatic shutdown that the shutdown sequence is reversed, and the 'mech begins to powerup from the position in the sequence that it was pressed. This means if you were halfway to a full shutdown, you would startup at half the duration.
This to me clearly represents what "Override" means. It means to force power of control from 1 entity, to another.
If at any point a user wants to shut-down after an override, they should press P. Reason being is that they have absolute control over the system (since they overrid the system), thus they control the power state of the 'mech.
P should be used for powering on and off during normal operation.
The logic SHOULD be as follows.
During NORMAL operation the USER is in control.
In the event of AUTOMATIC SYSTEM MANAGEMENT the SYSTEM is in control; less the USER OVERRIDES the SYSTEM.
Clear? Clear.
#9
Posted 30 January 2013 - 06:55 AM
#10
Posted 30 January 2013 - 07:01 AM
#11
Posted 30 January 2013 - 09:09 AM
I spend far too long shutdown after overheat unable to restart, press P and nothing happens then press it again and I power up then shutdown, whereas before I simply hit override and powered up. It's frustrating to say the least and I've died several times from this abysmal system.
#12
Posted 31 January 2013 - 04:22 AM
#14
Posted 31 January 2013 - 09:02 AM
I iz confuzzled
#15
Posted 31 January 2013 - 10:27 AM
sycocys, on 31 January 2013 - 04:22 AM, said:
Can't say I have, it doesn't have a heat issue with lasers or other weaponry, weigh anywhere near even a tonne or have a fusion engine.
Powered down you still have to wait, depending on the retained heat deems how long, but if I haven't overriden beforehand, missed the moment, and hit P to repower up there is a reason for it. I don't want my arse handed to me whilst I'm sat powered down waiting for the system to deem heat disappated to a reasonable level and I want to move whether it damages me or not.
A better implementation would have been :
Pressing 'o' before overheat disables the override completely for 5 seconds so your mech carries on whilst damaging itself.
Pressing 'o' after overheat powerdown overrides and restarts the mech as in the previous incarnation.
Pressing 'p' repowers after cooldown.
Essentially what we have now and what we did have, all in one.
Override 'overrides', whatever the current status.
Edited by GazT4R, 31 January 2013 - 10:28 AM.
#16
Posted 31 January 2013 - 10:46 AM
The only difference is that now you have to wait until your mech shuts down before you can perform this power-up override versus catching it in the middle which really shouldn't happen - it would jam up all of your controls, sensors, weapon systems, and if it managed to somehow power up your controls would probably work backwards if at all because the software controllers in your system would be reading massive fault errors - then crash and you'd shut down hard. You'd have to manually clear the fault codes out of your system before it would let you restart.
-Usually you dissipate enough heat that by the time you have your hud back your running hot but not overheated, try loading your self up with about 150% or more heat letting it shut down and powering back up on the caldera. -
I tried the over-ride, it's worked for me but I'm just not acquainted with the control yet to keep the timing on in battle.
#17
Posted 31 January 2013 - 10:59 AM
- Generally forced to boat multiple/large lasers or PPCs
- Overheat like a demon since no 2.0x DHS outside the engine
- Hitbox the size of a barn
I have all but stopped using my Awesome since the last patch because it overheats a ton. And when it does, it's often tough to bring out of shutdown because I mash P and I have no idea if it's doing anything or not. So while I sit there in a zombie state, mechs from two time zones over are having fun coring me out.
I like Calimaw's suggestion for simplicity. And I also don't disagree that it's hard to interrupt a shotdown/force restart.
So if it's deemed more realistic the way it currently stands, fine, we at least need some sort of notification that the system is shut down and now able to be powered up. And we need to know that it actually is powering up once we restart it. Having the screen just flashing orange means I have no idea what state my mech is currently in.
The devs might want to give this a quick review before they introduce a 6,000 MC hero mech that's going to be sitting with an orange HUD all the time -- I can imagine the rioting THAT will cause on the forums.
#18
Posted 31 January 2013 - 03:40 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users