4 replies to this topic

[Vloth]

Quote

• Loadout changes made after upgrading an unrepaired mech after a match can lead to all owned Mechs disappearance and HUD overlay

This is stated incorrectly. So if that is what you think is the problem, you are not understanding the actual problem/concern. This issue happens equally IF NOT MORE SO when you make loadout changes to fully repaired mechs as well. I have experienced this Client crash about 30x now in the past week. Each time my mech was fully repaired and rearmed. So what you state above in the known patch bugs is either an incorrect understanding of the bug causing the Client to crash, or an incorrect description of it.

[WAR ArkAngel]

Agreed. Additionally, I have found that it never glitches the Mechlab when I edit mechs while I'm not in a group. If I'm in a group and edit my mechs... it's almost a guarantee that my bay will freeze if I try to save a configuration after editing while grouped up and requires logging out and then back in to correct.

[armitage]

ya I have autorepair on and always wait until the mech is cleared before tinkering. It's happened 3 or 4 times now, but for me I haven't been in a group any of those times.

[Lefford]

Vloth, on 31 October 2012 - 07:15 AM, said:

This is stated incorrectly. So if that is what you think is the problem, you are not understanding the actual problem/concern. This issue happens equally IF NOT MORE SO when you make loadout changes to fully repaired mechs as well. I have experienced this Client crash about 30x now in the past week. Each time my mech was fully repaired and rearmed. So what you state above in the known patch bugs is either an incorrect understanding of the bug causing the Client to crash, or an incorrect description of it.

ive only had it happen if i messed with a mech that was not repaired after a match

[Icepick]

It has happened to me with fully-repaired mechs, or even on a mech I have never used in combat at all.