As I’ve been reporting in my weekly Simulator User Group meeting summaries and my Third-Party Viewer Developer meeting updates, there have been widespread issues with disconnects during region crossings – both via teleport and physical region crossings (e.g. via boat or aircraft or on foot).
Various theories have popped up over the weeks as to why the problem is occurring – with fingers most often being pointed at the server-side deployment of the Environment Enhancement Project (EEP). Whether or not EEP is responsible or not is hard to judge.
As I noted in my March 30th TPVD meeting notes, one of the problems with the issues is that they appear to strike randomly, and cannot be reproduced with any consistency; were a single cause behind them, it’s not unreasonable to assume that investigations would lead to a point where some degree of reproduction could be manifested.
It has been suggested by some users that de-rendering the sky (CTRL-ALT-SHIFT-6) before a teleport attempt can apparently ease the issue – although this is hardly a fix (and certainly no help to aviators and sailors), nor does it appear to work in all cases.
As trying to get to the root cause(s) of the problem is taking time, on Monday, April 8th, Linden Lab issued a blog post of their own on the matter, which reads in full:
Many Residents have noted that in the last few weeks we have had an increase in disconnects during a teleport. These occur when an avatar attempts to teleport to a new Region (or cross a Region boundary, which is handled similarly internally) and the teleport or Region crossing takes longer than usual. Instead of arriving at the expected destination, the viewer disconnects with a message like:
Darn. You have been logged out of Second Life.
You have been disconnected from the region you were in.
We do not currently believe that this is specific to any viewer, and it can affect any pair of Regions (it seems to be a timing-sensitive failure in the hand-off between one simulator and the next). There is no known workaround – please continue logging back in to get where you were going in the meantime.
We are very much aware of the problem, and have a crack team trying to track it down and correct it. They’re putting in long hours and exploring all the possibilities. Quite unfortunately, this problem dodged our usual monitors of the behaviour of simulators in the Release Channels, and as a result we’re also enhancing those monitors to prevent similar problems getting past us in the future.
We’re sorry about this – we empathise with how disruptive it has been.
As noted, updates are being provided as available, through the various related User Group meetings, and I’ll continue to endeavour to reflect these through my relevant User Group meeting updates.
Inara Pey: Living in a Modemworld 
Just like the good old days in SL :} Except now there are instant messengers outside of SL so you can PM your friends and say, “I’d died ! I’ll BRB!” :}
LikeLiked by 1 person
Reblogged this on Thar She Blows! and commented:
Finally The Lab reacts! They must have noticed there’s something wrong with their product. Typically lazy Orca just steals Inara’s post and reblogs it hereabouts …
LikeLike
As per my SUG / TPVD updates, one of the problems with this issue is that it hasn’t been tripping any of the expected alarms at LL, and thus initially passed unnoticed – even Linden staff routinely in-world on a daily basis who were getting hit by it were initially pushed to believing it was an Internet connectivity issue between them and the servers, rather than anything within the SL services, simply because no monitors were registering a problem.
However, they have been digging into things for the last couple of weeks, and I suspect their blog post is indicative that this is turning into a bit of a head banger in terms of trying to find the root cause(s).
LikeLiked by 1 person
All staff notice from * Linden:
Everyone take the time *today* to go in-world (Linden or alt.) and make 10 teleports. Report back any problems.
And they would have noticed the scope of the problem early on. They themselves are the best alarm system.
LikeLike
Randomness is a symptom of partial disconnects or of capacitance-induced lag!
LikeLike
I suspect that the cause is some form of lag in the sim affecting teleports – in a teleport you briefly exist only as a data packet being transferred from one simulator to another. A loose wire or connector would be all it takes…yes, I’m suggesting a physical rather than programming error. If your data packet is delayed and arrives out of synch…you get dropped.
Maybe, in sims that manifest this problem most often, the old bit of “Turn off, unplug everything, plug everything back in, restore power” could be the missing fix. At the speeds that the simulators (servers) are running, a tiny bit of capacitance lag is all it would take.
That would also explain the seemingly random nature of the problem, too.
LikeLike
I have been experiencing this problem for the last few weeks.. Initially I thought it was a connection issue, but it wasn’t that… so I moved from the Firestorm Viewer to SL’s own, to see if that cured it, and admittedly it doesn’t happen so much, but it still happens.
Not sure if this may help, but today while boating I found a sim crossing that was particularly bad… While crossing between the Hay Harbor & Cats Paw sims, and vice versa, by boat as well teleporting, I was disconnected 8 out of 10 times!!
This really is a total pain, and it must be corrected as soon as possible.
LikeLike