search

MechWarriorOnline / issue-tracker

MWO Issue Tracker
18 stars 1 forks source link

Multi-client crash if last remaining mech is a DC which dies. #199

Closed capn-cat closed 6 years ago

capn-cat commented 7 years ago

Since the recent 1.4.130 patch on 15 August I've seen this crash two times:

Crash Image

Both instances had the same parameters: Group Queue Last mech is a DC

At the point that the DC would have died, the game crashes for all connected players - or at least the group I was playing with who I was able to ask.

Tarogato-MWO commented 7 years ago

I can corroborate this crash. Happened in solo queue, last mech alive was a disconnect, we killed him with a back shot. I think it was a MAD-IIC, so I suspect the mech itself does not matter. My unit also mentioned it happening in CW when killing a disco mech when it was dropped from a dropship.

capn-cat commented 7 years ago

Thanks Taro. One other point of data - I'm fairly certain in both cases I got the rewards from the match, which would imply that the server stayed live and logged the results.

Did you or your teammates notice if you received XP and CBills from your matches?

bivant commented 7 years ago

Happened to me a minute ago. DC mech was also MAD-IIC, was killed in the back. Quick play solo queue.

capn-cat commented 7 years ago

I had it happen again to me this weekend, in faction play. It was still seemingly incurred by the death of a DC mech, however on this occasion all the other pilots were still alive. So the fact that on previous occasions it was the last surviving mech may just be due to the likelihood that the a spawn DC would be the last to die.

capn-cat commented 7 years ago

Potential fix for this issue in upcoming hotfix

Crash: Fixed a crash that could occur during combat when a 'Mech with no player attached was destroyed, such as when the player had disconnected.

tauSentry commented 6 years ago

@capn-cat, to the best of your knowledge, did this get properly handled in the hotfix?

capn-cat commented 6 years ago

Havent seen it since. :)

On 15 October 2017 at 12:56, tauSentry notifications@github.com wrote:

@capn-cat https://github.com/capn-cat, to the best of your knowledge, did this get properly handled in the hotfix?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MechWarriorOnline/issue-tracker/issues/199#issuecomment-336675778, or mute the thread https://github.com/notifications/unsubscribe-auth/Ab31lWCGa5YYtESnqBmcdnbRlrhiMdZgks5ssUolgaJpZM4PRGy8 .