Second Life

Things about SL

Sudden Lag on the Radar

by

Toysoldier Thor has been relentlessly tracking down the causes of his in-world event crashes and sudden massive lag. Region owners and event managers have been collecting and providing data on the problem in the forum. See my previous article: New Lag Problem. See the forum thread here: Major Increase in Instant SIM LAG & Crash … Read more

Treet TV’s Pathfinding Episode

by

Treet TV is an ongoing broadcast team presenting in Second Life™ and streamed on the web. Their studio is at Garden of Dreams. They present their shows there via Media on a Prim (MOAP) and on Parcel Stream. Each Monday at 2PM (SLT/PT) they have a new Designing Worlds show. At other times you can find other shows being presented. Happy Hunting has a regular show for hunters. Plus, there are drama shows and series with weekly episodes. Check out the full range at Treet.tv.

Cute Horatio Pathfinding Character

Pathfinding

Monday October 8th Designing Worlds presented their interview with the Lindens on Pathfinding, the new feature in SL that I’ve been covering for months. Sandry Logan was interviewed on Isle of Dogs, which is the home of the Virtual Kennel Club of Second Life. They have a new line of trainable companion dogs. Check out the web site for more information.

Read more

Pages: 1 2

Metareality Index Week 40

by

I’ve been gone all weekend, a wedding to attend. So, writing up the latest Metareality podcast has had to wait. The podcast is: Not Cool… well the podcast is. They are referring to Second Life™ not being cool.

As always this outline is my take on what I hear and may or may not relate to what you hear when listening to the podcast.

Metareality Podcasts

00:50 – Is Drax a real name? Karl is messing with Drax. But, then Drax gets to take some funny takes on the German thing about Stiefvater.

03:30 – Exodus Viewer slider scandal Drax is involved in… this too is funny and you have to listen to appreciate it.

Read more

Pages: 1 2

#SL Large Group Edit Update Wk40

by

Wednesday we got three packages rolled to the Release Candidate (RC) channels. The changes for Large Group Editing were in the package that rolled to the Le Tigre channel. While the packages rolled to Blue Steel and Magnum worked well, something went wrong in the Le Tigre roll out.

Large Groups – Image by: KittyKat3756 – Flickr

Something in the code is miscalculating the prim cost/count and forcing the return of large numbers of prims. You can imagine the screams. Very quickly the Lindens realized they had a problem. While they didn’t know the cause as of Thursday, they do know a massive number of prims were being returned.

The Le Tigre regions were rolled back and the package running on Blue Steel, a maintenance package, was rolled over Le Tigre. Unfortunately that roll could not undo the damage of returned prims. So, the damaged regions had to be restored to the region state previous to the damaging roll out.

Read more

#SL News 1 Week 40

by

Not much news this week. Plus I have been trying to resuscitate dying laptops. Seems to be a rash of those this week.

UPDATE: 1:54 PM PT – Le Tigre had serious problems and is being rolled back to the previous version. The regions have to be rolled back to get an earlier version of the server software. That is an automated process. Next all the regions in Le Tigre have to be manually updated to a previous SIM state prior to the problems. There are a over 1,000 regions to do. It is going to take some time.

Main Channel

There was no roll of a new server package to the main channel. Last week no Release Candidates made it to the RC channels, so there was nothing to roll.

There is a the New Lag Problem. This problem is pretty much invisible to the Lindens, meaning it is not showing up in their stats. Nor is it an easily reproducible problem. Both of those things make it invisible to the Lindens for all practical purposes. However, those running events are pulling their hair out dealing with the problem.

So, if you are an event manager or promoter, you will want to record the date and time, nearest minute, the lag hit, get as close as you can. Attend the Server Beta and Server & Scripting user group meetings (Time & Location) and provide at least the server version, region name, and date time of the problem.

Read more