Second Life and Virtual Worlds
I got a surprise this morning. Looking through the open source communications I see an ongoing problem with items not registering changes in the viewer and scripts breaking. I suspected some of this was from the Interest List changes and would hold that project back. (Note: scroll down for info on the video. It is not related to my surprise.)
[youtube NIocN3YAaME]
BUG-840 – Viewer 3.4.2 (Beta) breaks almost every sliding door script in SL.
We have had about a week with the new rollouts. There doesn’t seem to be any major problems. Nothing had to roll back. I’m not clear whether the Interest List or the maintenance package will roll to the main channel this week. We’ll see something post later today when the Lindens make a final decision.
The bot users have seen a huge drop in the data being delivered to them. Even beyond the amount added with the Interest List bug. Andrew Linden was considering what changes, other than the bug fix, may account for the saving in bandwidth use. Some of those items are:
The whole point of the Interest List update was to improve server side culling, meaning to have the server only send object information for the objects an avatar can see. That has improved.
Kelly Linden has been working on fixing some problems with avatar banning from land. Those fixes have rolled out. BUT… there is a problem in the Phoenix Viewer. One can ban an avatar using Phoenix and it appears to be banned. But, that data is not getting to the server. So, the system does not ban the avatar.
The work around is to do bans with a viewer other than Phoenix.
Whirly Fizzle described it this way: “Oh, re estate bans, Zi Ree, one of the Phoenix/Firestorm developers found a bad bug in Phoenix viewer yesterday which *may* account for some reports of estate bans failing. Phoenix has an estate ban feature called GTFO. If a user bans a resident using this option, the residents name will be added to the estate ban list but the resident doesn’t actually get banned. If anyone sees reports of estate bans being ineffective, please make sure they didn’t ban using Phoenix viewer. I’d so, remove the ban & reban using Viewer 3/Firestorm etc.”
Simon Linden noted, “I don’t remember the details, but I believe Kelly did find some cases where he thought bans could be bypassed, or issues when the ban list was full.”
If you regularly read this blog you know that the Multi-Threaded Region-Crossing code rolled to the main channel last week (5). We’ve had the code running for a week as I write this. So, how is it working for you?
WolfBaginski Bearsfoot has written up his experience now that the code is in place. See: Region Crossing: A Report On Experience. Wolf thinks crossing are not as good as they once were… I suppose he means like ‘ever.’ Personally I can’t remember when they were better. But, later he says there is little if any change when walking across regions, which is my experience.
It is small, but I do think I get control of my avatar a bit faster after a crossing. But, it is hard to say.
As reported earlier this week, things are moving forward with server releases. There isn’t much new to report. See: Second Life News 2013-5 (1). Things have gone pretty much as expected.
The Lindens think the package running on the Le Tigre RC channel will get promoted to the main channel in week 6. This is the package with the fix for regions not showing up in search. Yawn.
The Multi-Threaded Region-Crossing code rolled to the main channel this week. That mostly seems to have worked.
Don’t expect to see much difference when you cross a region. I think my avatar responses to navigation instructions faster after a crossing. But, it is not significant enough a change that I can be sure.
WARNING: There is currently a problem that appears to be part of the Region-Crossing update. If an estate manager or other land owner bans and ejects a user, the region will crash when they leave the region. Oops! It is currently unclear what the details are. Try ejecting without banning then ban. I have no idea … Read more