Server
The main channel is getting a restart but, no new package.
Wednesday the RC channels will get a new package and be restarted.
The server changes are stated as:
Second Life News 2017 w05
Viewers
General Viewer Information
Second Life Third-Party Dev News 2017 w04
The Third-Party Developers meeting was last Friday. The video is here: Second Life: Third Party Viewer meeting (27January 2017). 54 minutes.
Following is my summary of the video.
There are 2 project viewers in Lab’s pipeline. They are not yet published as RC viewers. Soon.
Second Life News 2017 w/04
I haven’t updated the server/viewer information since week #1. Blame bacteria, I do.
Server
This week the main channel got a server update. The RC channels run the same package, no new package.
Second Life at 64-bits
I’ve been out of it with pneumonia, 103+ fevers, and some really messed up dreams. Just as the Lab was releasing Alex Ivy, the project name for the 64-bit version of the Linden viewer, I was getting sick. So, I’m just getting around to trying the new project viewer.
Download
The download package is about 80MB. Firestorm releases are about 20MB larger.
You can download a copy here: Alternate Viewers.
Second Life: How to FIX SLURL’s
How do we tell our computer which viewer to use when we click a SLURL in a web browser? I’ll explain what happens and show you how to make the change (at least for Windows – Sorry, I’m not an Apple person). Plus, I’ll give you the link to the way easy tool for this task that the Firestorm peeps made.
Firestorm Default Viewer Selection Tool
The Firestorm people are aware of the problem and made a tool similar to Firefox’s process for handling protocol settings. You can find it here: SLURL Proxy.
Install this program. Drag and drop your viewer icons in it. Select one for your default choice. Once setup, when you click an SLURL the program will use the default you have selected.
Run the program again to make changes. Easy.
Second Life News 2016 w51
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.
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?