double log in required

[TheflyingElk]

Hey guys, This question pertains to a oddity rather than a big problem,
every time I log onto AH I have to go though the load process twice, each time I try to log into a online arena the first attempt always gives me a host connection lost message. If I then go through the log in process again the system almost always lets the game load completely. Do I have a port problem or do I have no problem at all, Is this a common issue or just a oddity I should live with? I just have to sit through the load process twice is the only issue. I just hope it is not a symptom of a bigger problem on the horizon.

[Skuzzy]

Your computer might be taking too long to preload textures.  If you have the "Preload skins" option checked in the "Video Settings", uncheck it.

If it still happens, then uncheck the other preload option and see if it happens.  If it stops, then set the "Maximum Texture Size" to one notch lower and try preloading the textures into system RAM alone.

Things like this are normally caused by the computer not having enough available resources when the game starts and Windows has to swap out a bunch of things to make room for the game.  The second you try, everything is still loaded in memory, so the game does not timeout.

[Skuzzy]

Someone also mentioned he was having similar issues and they discovered the cable connection had excess noise on it.

[REP0MAN]

Originally posted by Skuzzy
Someone also mentioned he was having similar issues and they discovered the cable connection had excess noise on it.

I'd be interested to hear how this conclusion was reached Skuzzy. Ingress can indeed cause packet loss, I agree. But to routinely cause multiple log-in cues is very abnormal as the level of ingress (noise on the line) would have to consistently match the intensity and frequency to achieve this result. My electronics nerd brain is really curious how it was caused and how they tracked it down.

On topic...

It definitely sounds more client based than network based. As I said above, the routine-ness of the issue seems to be too 'routine' for just a packet loss issue. If it were, you would most likely see packet loss effects in other aspects of the game; not to mention, your total internet experience.

[Skuzzy]

I agree it is probably more client based, I just tossed it out there as another member had a similar problem and once the noise problem was cured on the line it went away.

I can see it causing a problem as multiple packet retries (due to higher than normal bit error rates) could cause a timeout to happen and dump the client.

[REP0MAN]

I agree that elevated ingress levels will cause problems, don't get me wrong. Definitely something to look at. Ingress is something that I deal with daily. Many times, a customer will see slow page loads or digital video tiling at certain times of day. Example: Customer has issues with tiling and slow page loads/time out between 7pm and 10pm. I sweep the node (in the morning hours) and find minimal noise floor elevation, no CLI leakage and some minor tilt issues that quickly were EQ'd out. I clear the work order. Two days later, same work order is in the pool. Night crew runs out the node DURING the times customer states he has issues. They find a HUGE ingress issue and trace it one street over to a neighbor who has his HAM radio base station (calling UK, South America type of station) on and operating during these times. It created a constant noise addition during these times which caused similar issues for our customer. The station happened to be about 75' from the node vault. They found that he was transmitting far beyond what is allowed to. The FCC fixed the rest. Of course, this is a unique example but a relevant one none the less.

If client dump is the result, wouldn't the client see a CTD? Or, would it not CTD from that early in the log in process?

[TheflyingElk]

Turning off the preloads did the trick, now I get a real fast load and launch! Thanks again:aok

[Skuzzy]

The symptoms are the same for excess bit error rates or resource issues when trying to connect to the arena Rep0.  It is just a timeout happening on the client side which presents the host connection lost message.

Retries of packets with CRC errors happens in the operating system before we get the packet.

[REP0MAN]

cc, thanks Skuzzy. That explains a bunch for me.

Happy New Year bud