Cell Host 126 disconnect

[akmarine]

Flew for about 10 minutes and BAM disconnected cellhost 126. It shows 3rd person view and brings me back to the mission map. But after that, Im still in the game and can chat with people.

This happened to me 3 times in a row. What. The. Hell.

Where do I access my dump logs to see what may have caused this?

[fox403]

all been disconeted again,,this is going down pan!!!!

[mrblue]

[fox403]

and its just happend again everybody!!!!!

[fox403]

6th time today sever crashes mm says sorry,, locks my thread! so not allowed tell anyone about server crashing it seems ?

[uglyboy]

well it's kind of known anyway

[fox403]

not to them thats logging in,,alot people thinking its there computers ,,spends time chaseing drives spending money upgrades that might not be needed,,need info on the prob

[uglyboy]

If the server crashes and someone thinks he crashed because it's his pc fault, it's really clueless then, just try to relog to see Server Off or like before when cellhost 126 hit and everyone complained at the same time. Individual 20033 etc is a different matter. And still you got to be clueless again to search driver update to fix a connection issue.

[akmarine]

Yeah the servers taking a dump a lot. Even if it's not server wide, it hits various players individually at the same time. Evile, lucky420, and I all had connection 126 and yet others didn't have it happen to them. Somethings going on. They said the netcode 2 was back on, maybe it's not working well with the new patch? *shrug*

[GOPHUR]

If the server crashes and someone thinks he crashed because it's his pc fault' date=' it's really clueless then, just try to relog to see Server Off or like before when cellhost 126 hit and everyone complained at the same time. Individual 20033 etc is a different matter. And still you got to be clueless again to search driver update to fix a connection issue.[/quote']

Driver updates don't fix connection issues Ug. I think you coincidentally updated when we did a host fix for connection issues.

Regardless, update your drivers. I got 20% fps increase on my nVidia.

Are the 20033 errors largely fixed in live? I'm not seeing any reports.

Is the 126 error message not descriptive enough?

Are you guys just crashing when the host dies and not getting an error message?

What is causing people to think that when the host dies it is them?

[GOPHUR]

If the server crashes and someone thinks he crashed because it's his pc fault' date=' it's really clueless then, just try to relog to see Server Off or like before when cellhost 126 hit and everyone complained at the same time. Individual 20033 etc is a different matter. And still you got to be clueless again to search driver update to fix a connection issue.[/quote']

Are 20033 errors reduced on server?

Is the 126 error message not telling you enough info?

Why do people think it is them when the server crashes? Do you not get an error message?

[mrfancyp]

I got the error message and almost immediately a message that I was reconnected to the host. At the same time I despawned to mission screen.

About a minute later I got the same message about restablishing the connection. Chat still worked, but I couldn't spawn in (even after the server was unlocked) due to an empty unit list. I went back to brigade screen, then attempted to make a new mission, but after clicking the create mission button the client seemed to freeze for a few seconds (mouse input still possible). That reminded me of a similar problem in 1.31 or 1.32 where CTHLs would sometimes leave you in the mission screen but unable to do anything.

So it seems that restarting the game is necessary after this error occurs.

[akmarine]

^

Yep, you can chat to people but can't spawn in or make missions. You get cell host 126 but not booted from the game. You still have to relog to play though. This has only happened to me starting yesterday.