Second Life and Virtual Worlds
The planned roll out to the main channel (leaving us running #19.01.25.523656) was canceled due to a bug in the logging. So, no restart to the main channel. Main channel regions got a restart last week.
The Deploy notice was posted Monday and revised Tuesday. So, if you are confused, it is because of late breaking changes.
Blue Steel and Le Tigre will update to #19.02.08.524296. This includes the EEP feature, which is to being installed in more regions fo broader testing.
The third-party Dev UG meeting was short and griefed. The video is here. Pantera Północy, the videographer, edited most of the griefing out. Annoying.
The main channel got an update, #19.01.25.523656. Has logging to gather baseline information on simulator performance in various areas of interest and additional internal logging. So, they are now getting data from the majority of the grid.
If you drive, fly, or sail now would be a good week to be active. Of course, Tuesday afternoon is a good day to drive, fly, or sail as the most regions have just been restarted.
There is no Deploys thread this week. From the Server-Scripting UG we hear,
[12:05] Simon Linden: For server news, there wasn’t an update to the main channel today but tomorrow will see 3 different RCs
Server-Scripting Meeting
[12:06] Simon Linden: We’ll have a new maintenance update in one channel
[12:06] Simon Linden: Another that only has internal changes
[12:07] Simon Linden: and _maybe_ an update for the EEP servers, but Rider is going after a bug that’s blocking that from moving forward
[12:07] Joe Magarac (animats): The “time is stuck” bug?
[12:07] Simon Linden: exactly Joe
[12:07] Simon Linden: yeah that one is a show-stopper …. and he’s working on it right now
So, no roll to the main channels and 3 updates likely coming to the RC channels Wednesday.
Also, notice:
Scheduled – We will be conducting scheduled maintenance on our inventory system on Wednesday, January 30 from 6:00 AM until 7:00 AM PST. During this time, some residents may experience difficulty rezzing items.
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 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 logging.
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 factual.
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)
Some see Firestorm 6 as slower then v5, others do not. But there is a design feature in FS that may bite you and have you thinking it is the viewer. It isn’t necessarily just your imagination. Seems if you alternate between 5.1.7 and 6.0.1 Beta and have them sharing cache, which seems like a smart idea, you may well see a slowdown.
The viewers apparently look for a cache they made and if they do not find it, they delete the contents of the cache folders and build a new cache. So, when you first run 6 and attempt to share 5’s cache it deletes the cache and begins reloading. If you switch back to 5 the process repeats and each time to switch between versions, at least according to one of the FS peeps I trust.
Looks like we need to use one or the other. I’ve been using 6 and I like it. I don’t see a reason to switch back and forth. But… if you feel the need to switch back and forth, I suggest you assign a separate cache to 6.
We also know the Lindens are looking at and possibly already working on revamping the viewer cache. I am expecting significant changes in 2019. I also suspect the FS Devs have their own ideas about improving the viewer cache. So hopefully, we will see a mix of cache improvements in this coming year.
The main grid was to get version #18.12.05.522294 on Tuesday 12/18. My region did not get a restart. The last restart was 12/4 and my home region is running this version. So… wasup?
The three RC channels updated to version #18.12.03.522210 Wednesday.
The RC Snack channel is said to be running an EEP version 18.12.14.522551.
At the Server-Scripting UG meeting, there was some discussion of how the coming ability to change avatar names might work. It quickly becomes obvious that third-party service providers need someway to ID avatars with changing names. Think ‘redelivery terminals’.
It was noted that the new LSL functions for Animesh are not included in the Wiki LSL documentation. Oops. The Lindens are looking to get that fixed.
One of the server updates seems to be causing people to disconnect. This is more of a problem in ADITI. If you are seeing the problem let the Lindens know which region and what date and time.
No UG meetings until January 8th…