7 replies to this topic

[Dude42]

Pretty much as the title says. The patch does seem to have helped some. Now instead of disconnecting every single match for 8-10 games in a row it'll disconnects a bit more intermittently. But it is definitely still an issue.

With this message in the Omicron log:
CGameRules::OnDisconnect: Client has disconnected: cause=eDC_ProtocolError, desc=Remote disconnected: Malformed packet
CGameClientChannel::Release

[Marvyn Dodgers]

Have you rund the repair tool to see if it helps?

http://mwomercs.com/...public-release/

[Dude42]

Marvyn Dodgers, on 22 May 2013 - 03:15 PM, said:

Have you rund the repair tool to see if it helps?

http://mwomercs.com/...public-release/

Yes. I have been battling this issue since I started MWO last month. I've submitted support tickets. I've run the repair tool. I've done way more than that. There used to be a fairly large thread here, for this issue. With the new patch they cleared the threads out. You might note my use of the word "still" in the title. So now I guess I have to deal with people unfamiliar with the issue asking silly questions. Cool. Here is the original thread.
You can read it if you'd like to know what people have tried. I'm not alone with this one.

The patch notes specifically mentioned this issue. I agree the patch helped. The issue is not as prevalent as it was before. At least for me. It is certainly still frustrating to be randomly disconnected back to mechlab mid match.

Edited by Dude42, 22 May 2013 - 03:43 PM.

[Marvyn Dodgers]

One thing that Krist (PGI) also posted recently (sorry, don't have the link handy) is that work things like this it might help to shut down computer, modem and router for at least a minute and restart all and see if it helps. Admittedly, this sounds like it is just a "have you rebooted" suggestion, but at this point I don't think they have enough consistent data points to track it down.

In any case, after trying this, please submit a support ticket to let them know what did/didn't work.

[Dude42]

Marvyn Dodgers, on 22 May 2013 - 03:49 PM, said:

One thing that Krist (PGI) also posted recently (sorry, don't have the link handy) is that work things like this it might help to shut down computer, modem and router for at least a minute and restart all and see if it helps. Admittedly, this sounds like it is just a "have you rebooted" suggestion, but at this point I don't think they have enough consistent data points to track it down.

In any case, after trying this, please submit a support ticket to let them know what did/didn't work.

Please see my reply to you above. Please read my posts in the thread I gave you the link to. I am aware that rebooting the network equipment may help. There are 5 PCs and multiple devices/people using the network at pretty much all times. I cannot be rebooting the network repeatedly. Actually here. Just in case. I do not want to repeat myself to that degree.

[Marvyn Dodgers]

Apologies for not reading the original link, good luck with resolution and my bad.

[Dude42]

Marvyn Dodgers, on 22 May 2013 - 03:55 PM, said:

Apologies for not reading the original link, good luck with resolution and my bad.

No problem. I just want to make them aware it's still occurring, not start troubleshooting again And thanks for trying, sorry if I came off a bit abrasive. Just frustrated with the issue.

[Marvyn Dodgers]

NP, I can understand the frustration (though luckily haven't experienced it yet)

Good hunting