This is a repost. It seems to have poofed shortly after I first posted it.
We have some news… March 1 was the Third-Party Dev meeting. It ran 57 minutes… but, there was
Problems continue on the server-front. No updates on the main or RC channels. These problems are holding up viewer releases. EAM, EEP, and BoM are all waiting for server-backend stuff to update.
Any region that has run longer than 10 days will get a restart.
The server update that kills inventory UDP fetching is also held up until the server problems are solved. Actually, lots of stuff is delayed as people are pulled to work on the servers. Continue reading →
There is news. Everyone has been back to work long enough post-holiday
for things to be getting completed. So, changes are in progress. I am behind,
again. So, I’m just getting this converted from my notes to something readable.
We did get a Deploy post, appearing Tuesday afternoon.
The Rainforest Photo Contest, Entry # 2
The main channel
updates to version #19.01.09.523003. This version is listed as having logging
collecting data to build a baseline performance measure. Also, more internal
My empirical take is things have degraded. But, without some
objective measure that is only an opinion. As I started flying a complex Shergood
helicopter in July 2018 my perception of region reliability has likely changed.
But, my observation of what happens when crossing region boundaries is more
Using the Firestorm Viewer, I have the option to cross
regions in two ways. The default is to cross using the basic viewer prediction
of what should happen for a smoother appearing crossing. The other is sort of
stop-action crossing. (Preferences->Move
& View->Movement->Movement at region crossing: Predict or Stop)
Monday was a US holiday, Memorial Day. So, today is the Lab’s first workday this week. As of 10 AM SLT this morning there is no Deploy post. But, there is some HOT new news today. See the Other News section.
From the Server-Scripting meeting, Simon Linden: Let’s see … for server news, we had a rollback last week of the RC channels for a bug. I think there was a post somewhere about that. We’re going to have updates out tomorrow that have that fixed … and possibly another release that has a few other items in it. It’s all internal changes, as far as I know.
Concrete studied under orange light – 3
Second Life Love Me Render Viewer version 188.8.131.525528 – This an update from the previous version184.108.40.2064788 released in week #16.
Second Life Maintenance Viewer version 220.127.116.115527 – Last updated in week #21.
Second Life Project 360 Snapshot Viewer version 18.104.22.1683006 – Last updated in week #10.
Second Life Project Animesh Viewer version 22.214.171.1245420 – Released week #16.
Second Life Project Bakes On Mesh Viewer version 126.96.36.1993936 – Last updated in week #14. Continue reading →
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 →