3 replies to this topic

[Nemesis Duck]

The reality is Clans have to deal with heat to be effective. When a shutdown occurs during an engagement, it's imperative to restart your mech quickly so that you can react to the changing battle. Unfortunately, it means clanners are falling victim to the feeble shutdown/startup mechanic more often than the IS. Having a mech shutdown twice in a row because it queues up a shutdown-command is disasterous, ridiculously unrealistic and ruins immersiveness since no real combat machine would function like this.
A good solution is to seperate the shutdown/startup command into two distinct, mappable commands: one for shutdown and one for startup. This will ensure a mech behaves predictably when reacting to a shutdown event.
It's unfortunate but the only reason I can think of as to why this mechanic has remained as it has is it gives spectators something to laugh at. I don't want to think that's the reason so please quell the sadistic company impression the combined shutdown/startup command creates by seperating it into two distinct commands.
Thanks.

[Firewuff]

Or just learn not to how to not button mash

[Rogue Jedi]

Assmodius, you do realise that if you overheat to shutdown pressing the shutdown/power up button does not turn the Mech back on don't you?
Are you manualy shutting down then repeatidly pressing the button (instead of just pressing once then waiting for the Mech to power up), or are you pressing to power up after an automated shutdown and finding that a power down command is queued when you power back up?

I am not opposed to having the ability to seperate the shutdown/power up command so long as there remains the option to leave them both assigned to the same button, as it is rair that I need to power down and I do not want to have to remember 2 seperate commands or it.

[Nemesis Duck]

Au contraire mon frere. It goes like this:

A shutdown occurs due to overheating (hit 100% heat). The time the mech is shutdown for is variable and dependent on how much over 100% I went.

I have 2 options when I shutdown:

1. Wait for the mech to power on it's own. The time I am shutdown is determined by how much over 100% I went.

2. Power up early and risk damaging components.

For example:

I shutdown and I want to power on early because the enemy is shooting me and has a cherry red CT. In that situation it's worth risking component damage to get the kill and stop his barrage. I reach for the power on button but just before I press it the mech begins to power on it own automatically because it had dissapated heat to under 100%. I dont realise the mech is powering up automatically because all this is all happening during a firefight and the shutdown time is variable, but since the start up sequence had started, attempting to power on queues up a second shutdown instead that occurs after the initial power on sequence finishes. It's pretty lame when this happens.

Solutions:

1. Separate the buttons

2. Create a timeout to stop queuing up shutdowns while the mech is in power up sequence. Although I can imagine where queuing up a shutdown would be useful in certain situations.

For example:

I'm powered off and begin to power up but an enemy appears in the distance and he hasn't seen me yet, so I queue up a second shutdown to power back off as quickly as possible and avoid detection.

I prefer the 2 button solution because queuing up a second shutdown is useful, having explicit control over my mech is important, and random behavior caused by a variable shutdown time is unacceptable.