4 replies to this topic

[Targetloc]

Was on frozen city with a friend on TS.


He was fighting a YLW at the top of the hill on the corner in frozen city where the building is right next to the mountain the cave is in. It was bright red CT when he shouts, "Crap, I just crashed." He was reversing at the time so his zombie mech backed out leaving me an opening.

I stepped in to take the kill, standing in the exact same position he was at and as soon as I clicked to fire, MY game crashed.


So whether that YLW was cursed, or its that specific spot on the map, we both crashed in the same place within 10 seconds of eachother.

[Ancient Demise]

It appears that people are crashing in groups, but I have not experienced crashes due to the same or similar locations. A few games tonight the majority of my team if not my whole group has had a CTD in a very short period of time and all while engaging the enemy (the other team does not appear to crash). Is someone else causing these CTDs? I do not think there is enough info to say for sure and I certainly do not want to start screaming hax but IMO something fishy is happening here...

[Rejarial Galatan]

netcode perhaps?

[Targetloc]

I don't think it's hax. There was a bug for a while where killing an Atlas would crash everyone's game.

More likely dealing damage to a specific bugged mech or a target that is position desynced from the server...

[RenegadeMaster]

This bug is entirely plausible, as I have crashed two different times this summer when I was about to get killed, although I have never crashed when I was about to kill another mech.

In my case when I looked at my omnicron.log file and its last few lines, I noticed that there was an error with a certain type of file relating to the death animation of my mech. So that means it could be possible for the same thing to happen when witnessing the death of another mech.