The main channel continues to run #17.06.12.327066. But, they say there was a ‘bi-weekly’ restart. According to my ‘restart monitor’ in-world, the main channel region I live in was restarted 7/4 @ 08:05. So, they did. I think that is unusual for a holiday.
Blue Steel and Le Tigre continue to run #17.06.23.327344. There were no restarts.
Magnum was restarted and now runs #17.06.29.327400. This has the fix for the DJ song boards that stopped working. This is primarily an Operating System update.
There was no roll on the main grid today. Still on version #17.06.12.327066.
There are to be rolls on the RC channels. Blue Steel and Le Tigre will get #17.06.23.327344. This is Internal Fixes and an update from 17.06.19.3272066.
Magnum will get #17.06.23.327348. This is an OS upgrade (Nothing is changing functionality-wise). There have been some problems and the Magnum update last week was rolled back. So, a new try this week.
Reading time
Viewers
The main Viewer updated from 5.0.5.326444 to 5.0.6.326593. – Release Notes:
This viewer moves fetching of several types of assets to HTTP. This means that landmarks, wearables, sounds, and animations will now be fetched the same way as textures, via a direct query to CDN instead of through the simulator. This should generally make loading of such content both faster and more reliable. Twice the fetching and half the crashing with this new build.
Second Life Maintenance Viewer version 5.0.7.327250 – Is updated from last week’s version 5.0.6.327125.
Second Life Voice Viewer version 5.0.7.327253 – Is updated from last week’s version 5.0.6.326589.
Second Life Project 360 Snapshot Viewer version 5.1.0.506488 – This one also updated, from 5.1.0.505089.
Second Life Project Alex Ivy Viewer version 5.1.0.505089 – No change.
Tuesday the 19th, a new Firestorm Viewer version was released, 5.0.7.52912.
You can download and install this new version. There is no need to remove the previous version you are using. Some of us (yes, me) have noticed it crashes shortly after its first launch. On the second and subsequent launches, it seems fine.
The Girl with the Sun in Her Hair VIII
I suggest you restart your computer before installing. Inara in her review of this release (here), recommends backing up your viewer settings before starting the install. I didn’t have to restore any settings. BUT… if you are changing from 32 to 64-bit version, a settings backup is a good idea.
The Firestorm team has a goal to release an update every 3 months. It has been 6 months since the last release. So, there is a lot of work in this new release. Plus, they say it is very well tested.
Tuesday version #17.06.12.327066 of the server software rolled to the main channel. This is primarily a fix to keep regions from losing their connection to the backend servers.
Blue Steel and Le Tigre get the same new package #17.06.19.327206. Changes are listed as ‘Internal Changes’. I suppose that is more changes to data collection. Maybe updates to the server OS.
Bond – Austin Bond
Magnum gets version #17.06.19.327192. There is also an explicitly stated update of the OS for this channel. Plus, a couple of fixes.
BUG-100830 HTTP_CUSTOM_HEADER no longer works on RC 17.06.13.327111
BUG-100831 Lelutka Simone bento head spits a script error when attached on 17.06.13.327111 regions (Magnum & Cake)
Bug-100830 is the Song Board fix. If you didn’t read the previous article, be warned your song boards are not going to start working.
There was no roll to the main grid this week. The channel continues to run #17.05.26.326655.
Blue Steel will get a new package Wednesday, #17.06.01.326763. Includes internal fixes.
Le Tigre will get a new package Wednesday, #17.06.12.327066. Includes internal logging and features and an improvement to region starts.
Magnum also gets a new package, #17.06.12.327060. Shoutcast Player fix included. Other changes are an upgrade of the OS.
Tuesday done less left before WE 😜
Shoutcast is the feature that many use to publish the name of the song playing in a music stream. There was some old time fundamental problem with how those scripts worked. Some fix in the server side created a problem with those scripts, broke them. (BUG-100737) The Lindens were not going to build the bug back in. So, they are providing a fix that works similarly. But, all the Shoutcast scripts will have to change.
The fix is something about the characters in the HTTP request stream.
If you are hoping I am going to tell you we have VR for Second Life™, I’ll disappoint you. However, it apparently is possible. But, it isn’t easy and the whole VR thing is a mess, especially if you want to do it cheaply.
https://www.youtube.com/watch?v=FmC4nDabAkw&
For an instance of a mess, when you place a phone in Gear VR it auto-launches the Oculus app. Doesn’t matter what app you have running, the Oculus app launches and takes over the device. A bunch of people tell you to insert to the headset without connecting the phone to the headset. WAY lame, but doable. However, without the USB connection made the phone can fall out of the unit.
So… you have to get Samsung’s BK Package Disabler (US$1.49) get around this problem. They have a free version if you rooted your phone. If not, you have to hope the retail package will install. If you did root it, no problem just delete all you phones accounts, installed the root-version of BK, and redo all your accounts… lovely.
