|
Davada Abattoir
Junior Member
Join date: 16 Mar 2004
Posts: 3
|
03-30-2004 17:45
I can usually log into Second Life, but within a minute or two, I get kicked from SL with an error about mangled upstream network traffic. For the 30 seconds or so I'm in, the game seems normal enough. This problem began yesterday with the 1.3 patch, and I haven't made any changes to my system in the interim before or after the problem started.
I tried re-installing Second Life, but that had no effect. I'm on a Comcast Cable modem which has worked flawlessly with Second Life up until now.
|
|
Catherine Omega
Geometry Ninja
Join date: 10 Jan 2003
Posts: 2,053
|
03-30-2004 17:54
Do you have a wireless LAN? Those are always a good source for network corruption. What are your packet loss (Help > About Second Life) and ping times (Alt-1) like before SL craps out on you?
|
|
Carnildo Greenacre
Flight Engineer
Join date: 15 Nov 2003
Posts: 1,044
|
03-31-2004 00:38
If it's anything like what was happening to me a month or so ago, the only symptom is a series of entries in the SecondLife.log file about bad data coming over the network, followed by a crash or logout. No correlation with packet loss, bandwidth, hardware changes, or anything else.
_____________________
perl -le '$_ = 1; (1 x $_) !~ /^(11+)\1+$/ && print while $_++;'
|
|
Davada Abattoir
Junior Member
Join date: 16 Mar 2004
Posts: 3
|
04-03-2004 15:09
I'm on an Ethernet wire link to a router to a cable modem to my home. On Thursday it didn't happen once, on Friday I could stay logged in for 15 minutes or so, and today I get booted after 15 seconds or so. Very strange.
|
|
Joe Foo
Registered User
Join date: 7 Mar 2004
Posts: 51
|
04-08-2004 10:54
Perhaps the problem has always been there, but with the 1.3 version of SL, enough bad data recieved by the servers will boot you off the system rather than tolerate it. The only reason I can think this would b eimplemented is they might be trying to prevent some obscure binary combination which causes the server to crash.
|