Server

#SL News 2 Week 44

by

Well the roll out went nowhere near as planned. There were problems starting out that pushed the rolls back one day, from Tuesday to Wednesday. And that pushed Wednesday’s roll back a day. But, then the actual roll to the main channel rolled out the wrong version…

Server/Scripting Meeting

The Main channel was to get the code running on Blue Steel. Instead, an older version of the server code from a couple of weeks ago was rolled out. So, the main channels has regressed. I don’t know which version. Lydia Craig reported end up on version 12.10.12.265813 when the release notes said it should be 12.10.19.266079, which would be a one week regression.

Only a few people have noticed the glitch and posted in the forum Deploy thread.

Read more

#SL News 1 Week 44

by

The Tuesday roll out to the main channel has been postponed to Wednesday. Wednesday’s Release Candidate roll outs have been postponed to Thursday. This delay is from some backside problems.

Main Channel

As expected the main channel is getting the package running on Blue Steel & Magnum. This is what they call a backend infrastructure change. We won’t see any changes in operation, unless it breaks something.

Mesh Alpha Rendering Problem – See Invisaprim Below

Blue Steel

This is getting an upgrade of the code now running on Le Tigre… I’m not sure whether this is supposed to mean Blue Steel and Le Tigre will run the same code or not. Until the detail release notes come out I won’t know.

This channel may get the server fixes that are hoped to fix some of the Sudden Massive Lag problem event managers are seeing. BUG-355 

Read more

#SL News 2 Week 43

by

I’ve been distracted on weekends, so I’m just getting to writing up the last of the news from last week (43). There is no great news, but there are some interesting things.

Large Group Edit

The code for this change rolled out Wednesday. It had problems and was rolled back the same day. It is however currently running on the Snack Release Candidate Channel. You can get the details of that in: Second Life Large Groups Edit Week 43.

Server Scripting Meeting Oct. 2012

Part of the reason for getting this change up and running is to get it where Third Party Viewer Developers can test their viewers against the new server code. To use the new Group Editing code on the server viewers need to change the viewer code. Getting the code on a release channels allows TPV Dev’s to get their QA people and Beta testers involved.

The Problem

The package with the Large Group Edit code had a problem with the llSenor() function. It stopped returning a sorted list of objects. The sort is on distance. Not being able to figure out what is close or far meant breedables were not able to find food or each other… you know… to breed… The lack of loving was tragic.

The problem has been fixed. So, this week (44) we should see it move into one of the main release candidate channels.

Read more

Pages: 1 2

#SL Large Groups Edit Week 43

by

Getting this update out is proving to be a problem. Not so much the large group editing as the things it is packed with. You know, everyone bundles…

Oskar Linden posted in the SL Forum about the problems with the roll out to the Magnum Release Candidate Channel. See: Large Groups Fixes LIVE on AGNI.

The short story is the roll out was rolled back Wednesday due to issues in the llSensor() function.

Read more

Second Life News 1 Week 43

by

Interest List

Andrew Linden is still working on rewriting the interest list code. He says he is seeing light and should have working code soon. He hopes to have it done this week (43).

Server-Scripting Oct 2012

Andrew told us, “…Dan Linden noticed that the “number of objects in view” right after the login curtain comes up, in a busy region, is less in my code than server-trunk, which means that my interest list wasn’t doing as good of a job of loading initial content. But I think I’ve got that fixed, and am planning on implementing the “gradually increase camera far clip on login” behavior that some 3rd party viewers have already hacked on their end, which should help the initial login sorting.”

Read more

#SL News 3 Week 42

by

Blake Sea and Le Tigre

You probably remember the region crossing problems sailors and pilots had with the previous Havok Physics Engine update. Putting different versions of Havok on adjacent regions creates problems. Havok was never designed for use across multiple versions of Havok. It’s use by Linden Lab™ is the only known use that encounters that problem. So, we will likely have crossing problems with each update of Havok.

Morris Region, ADITI Grid

With the addition of Pathfinding and possible other gaming features to Second Life™ we are likely going to see more updates of Havok, but fortunately, less crossing problems. ‘More’ is like a couple a year.

Region Organization

Some weeks ago the Lab tried placing adjacent regions in the same or adjacent servers, physically adjacent servers. This made what Oskar Linden described as a ‘MASSIVE improvement’ in performance. Now it is standard operating procedure to keep the regions and servers organized.

Read more