d/c while zoning


all_hell

 

Posted

Since the last patch I have been booted to the log in screen multiple times when zoning. This can be exiting a mission, exiting an SG base, exiting Orobouros, or loading between zones. I get the splash screen, the progress bar moves to about 1/5 of the way and then just stops. After 30-45 seconds I get booted to the log in screen. This has happened on multiple characters and usually multiple times a night. There is no rhyme or reason that I can tell. Usually when I get booted out I cannot load anything back into the game unless I repair all files. And sometimes this does not work either.

Please have someone look into this.


"Most people that have no idea what they are doing have no idea that they don't know what they are doing." - John Cleese

@Ukase

 

Posted

which OS are you using?


 

Posted

Thanks for the link. I knew that other people were having similar problems but hadn't seen the post.

I'm running xp, 3 gigs of RAM.
Yeah, my system is old, but it worked fine before. That patch where they did something with the map code to try and reduce lag.

I do notice on the occasions that it takes me a long time to load in and I don't get D/C'd, I just see the LCMS message for a split second and I'm back to normal.

I am almost positive this is a connectivity issue.

http://us.ncsoft.com/gameadvisor
That link is to a testing application that support asked me to use. When I looked at the results, it showed me that basically, the CoH side is not getting the signal. Kind of like one modem calling another and not getting an answer.

There's some mysterious reason why I'm able to surf the web, listen to online radio but not able to log in sometimes. It's sporadic, but I can tell you that Fort Trident is a location that I can almost always log in at, but once I get there and try to leave, then I have troubles.

I had thought that maybe my poor system or CoH's "new" upgrades had a problem holding all that badge data, but there are plenty of badgers that don't seem to be having this problem.

And although I am upgrading my system, I'm 100% positive that the problem is on CoH side.

Mind you, I'm ALWAYS positive the problem is on their side, and sometimes it's on my side. <shrug>


"Most people that have no idea what they are doing have no idea that they don't know what they are doing." - John Cleese

@Ukase

 

Posted

Quote:
Originally Posted by Ukaserex View Post
I am almost positive this is a connectivity issue.

http://us.ncsoft.com/gameadvisor
That link is to a testing application that support asked me to use. When I looked at the results, it showed me that basically, the CoH side is not getting the signal. Kind of like one modem calling another and not getting an answer.
I tried running this just now, as sort of a control. Aside from client locks from driver issues if I use anything higher than Catalyst 11.4, I have little or no technical issues with CoH.

It couldn't connect to any of the checked servers, even though it was able to run pathpings after checking.

So... It might not be the best tool to use.

It does have a very detailed report though, and pointed me towards an issue I didn't even know I had. (Do NOT bother installing the SRS Essentials audio program, it isn't that great. And it doesn't clean up well on uninstall - it was still selected as my default audio out device, and still had a registry entry. :-S)

I did notice a disturbing amount of lost packets en-route for my pathpings... (Not on my end, and not on CoH end, but in between.)

So I will give it another run later in the day and see what it spits out.

Oh, note: The output is very detailed, so I would not suggest posting the output to any public forums.


 

Posted

Quote:
Originally Posted by Morgan Reed View Post
So I will give it another run later in the day and see what it spits out.
((Double posting just so the thread shows as updated - for those that might care.))

I ran it again later in the day, and I just ran it a third time in "so not prime time" (about 11:30PM Pacific time, 2:30AM Eastern time) to limit that effect on the test.

I am still receiving "connect failed" for every server connectivity check.
So I think that part of the tool is not trustworthy at all.

Interestingly, I am still getting > 10% packet loss at Level3s Atlanta hub(s)... (If domain name can be trusted.)