5 replies to this topic

[1Exitar1]

Today I have played 3 matches so far and in 2 of those matches my override has not engaged or turned itself off. Some of you might think that I might have just forgotten to hit the button, but I always call out 'Override' on comms and then hit the button myself. I had forgotten to turn it on one too many times in the past and just gotten into the habit of calling it out.

Anyone else having this problem?

[CFC Conky]

Not yet.

Good hunting,
CFC Conky

[1453 R]

Always hate the constant "OVERRIDE CHECK!" bellows at the start of a match, and the subsequent half-dozen people in the match that die to 100% completely and totally avoidable Heat Seppuku after engaging their override and then completely and utterly forgetting their heat bar exists before blasting themselves to 300+% heat in the first thirty seconds of a match and Stackpoling.

Like, yes, I get it, I get it. Shutting down mid-firefight is Capital-B Bad and should never be allowed. But holy crimmeny Frogmas, can we start following the "OVERRIDE CHECK!" screams with "Also don't be a complete and total nimdut and blow a million miles past your heat bar so you melt into magma and die the first time you see a single enemy 'Mech because the OVERRIDE also seems to apply to your brain"?

[Swamp Butt]

Cool shot anyone?

[Tarl Cabot]

Potential connectivity issues. It is a switch that is checked/sent once to the server. Record your matches so you can then review them to see what happened, including possibly hitting the override button, turning it off.

[1Exitar1]

Tarl Cabot, on 03 March 2025 - 11:41 AM, said:

Potential connectivity issues. It is a switch that is checked/sent once to the server. Record your matches so you can then review them to see what happened, including possibly hitting the override button, turning it off.

I tried recording after posting the original post and my graphics card did NOT like it! I find that odd because I have an AMD RX7900XTX, so a pretty good card. The game stuttered so badly that it was unplayable. It doesn't matter though because I haven't had the problem since.