1 reply to this topic

[Avengerus]

My mech CDA-2A(C) got stuck during a solo queue match on River City map.

In the beginning of the match I went on scouting mission down G line and spotted enemy mechs heading upper city.

I have followed them to E3-E4 while our team was pushing over the bridge.

Having attacked a few targets from E3 I was going to take cover behind the building in E4.

A second later my mech begun warping and after a few such "jumps" mech stopped and wouldn't move anymore.


Pressing movement buttons was only reflected on the throttle & speed indicator as full throttle but 0kph speed in forward or reverse:


reverse


There was no obstacles, mech was not damaged.

I was able to twist and fire weapons.


I asked my teammates for advice, but they suggested only to eject or commit suicide via overheating.

I exited the game and closed MWO client.


Then re-started client and loaded the game.

"Rejoin" option was available so I rejoined the match successfully.

Situation did not improve - my mech was alive, but still could not move at all.


After all my teammates were out of the game I revealed my position to the enemy.

This is where my immobilized mech died:


I am not sure whether this bug is related to the latest patch, but I've never had this problem before.

I don't think I can re-produce this bug.

Edited by Avengerus, 31 December 2017 - 03:27 PM.

[Tywren]

I had this happen on a different map once in CW (sulpher if it matters, but i don't think it does). The rubberbanding/warping caused you're mech to glitch into some segment of the map geometry, most likely the rise to come out of that flower bed, and you got stuck. Could have been worse, you could have glitched completely inside a building where no one could shoot you.

Edited by Tywren, 21 February 2016 - 11:18 AM.