The main channel updated to version #18.04.30.515008, this is the version that hopefully improves… not fixes, region crossings. Specifically, “Updates to simulator communication protocols aimed at improving region crossings and teleports.”
Blue Steel, Le Tigre, and Magnum all get the #18.05.07.515224 version. This is the version preparing for the name change feature by adding scripting functions to LSL.
Seems some regions are getting two restarts today. I suspect that is somewhat common.
It’s your move, pawn.
Simon Linden tells us, “…the servers are now doing a better job tracking all the attachments and objects you may be sitting on [when crossing a region]. The goal is to know when the region thinks that’s all done, and the viewer acknowledges it. If that doesn’t happen, it can do better fixing it. Continue reading →
Le Tigre and Magnum update to #18.03.14.513292. Internal fixes, logging to help diagnose an issue with in-world HTTP servers returning HTTP 503 (BUG-214702), adds a new capability to request IMs that were delivered to the requesting agent while the agent was offline, and adds a new capability to request the most up to date list of abuse report categories.
These ‘adds’ will require a viewer that can use them. Which I assume is somewhere in the QA pipeline. Continue reading →
The main channel was updated with version #17.07.27.327933 this morning, Tuesday. Last week the main channel was running version #17.07.11.327548. Both of these are listed as having “internal changes”. Geek-speak for changing data reporting, debugging, and performance information… usually.
Street at sunset
Blue Steel, Le Tigre, and Magnum were supposed to update to #17.07.27.327933 tomorrow, Wednesday. But, Simon tells us that isn’t going to happen. There probably won’t be a restart as they restarted with last week’s update. The Lindens try to restart regions once every two-weeks even if there is no planned update.
No big problem, but enough of one the Lindens decided to hold the RC update back. It had to do with regions names not being applied correctly in the restart, so they never appeared to come online.
The Deploys thread is dying. There is very little discussion or information to be gleaned from reading the posts. They are basically a day, time, and link to release notes. So, I suspect fewer people are reading the posts. I expect the posts to go away at some point. Continue reading →
I thought we would be in the no change window all this week. But, the Lindens have decided to roll last week’s RC update to the main channel… or they automated the forum posting like they did the status reports… naw.
♥ Believe in the Magic of Christmas ♥
The package rolling to the main channel is listed as having ‘improved internal server logging’. So, it makes sense to me that there is little likelihood of new bugs being introduced by adding and changing logging features. The week in testing probably revealed no performance change problems for this package. So, why not roll it out? Continue reading →
I don’t cover the Third-Party Viewers as much as I used to. I think Project Bento is a change that will make any viewer without Bento capability obsolete. Some Third Party Viewers are already Bento capable. Here is what I have found.
…and I may have made mistakes about which viewer does and doesn’t have Bento capability. If you see one please correct me. Continue reading →
I’m not a Singularity user. I have been. I know many people on older hardware use Singularity. It seems if Firestorm doesn’t work well for you then Singularity is the other white meat. So, I am always curious what is happening with the Singularity Viewer.
This is a brief round up of the Third Party Viewers for Second Life that I find interesting. Not in any particular order. The popular feature to be adding is: Restore to Last Position. I explain that in the section on RLV.
RLV 2.9.15 Update
Marine has updated the RLViewer she maintains. She is adding in the feature from Firestorm and Kokua: Restore to Last Position. This is a controversial feature the Lindens have omitted from the Linden made viewer. It apparently generates too many support calls.
What’s that sound? [Good facial expression]
The controversy centers around a problem the feature creates. Imagine you have a parcel in, say, Fishergate and it is in the northwest corner of the region. You build and rez stuff into that parcel. You then take them into inventory. You go to a different region, say Furball, and get a parcel in its south central area. When you use Restore to Last Position to rez those items they will poof away. You will most likely find them rezzed at the 0,0,0 point in the region. Continue reading →