Viewers

Second Life – Third-Party Dev’s UG Meeting 2017 w27

2017/07/08 by Nalates Urriah

Very short meeting, 20± minutes. Nothing new. Just status updates.

The first subject was the JIRA spamming. For now, the JIRA is locked down, no comments. There is no idea how long it will take to build a spam block.

The Alex Ivy viewer is out as the main viewer. It will update soon as a couple of problems were found. The Lindens are working on the launcher that figures out if it should load the 32 or 64-bit version of the viewer. They are also adding a setting to allow the user to override the automatic detection and force install of one or the other.

Second Life News 2017 w27

2017/07/062017/07/06 by Nalates Urriah

Servers

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.

Second Life News 2017 w26

2017/07/052017/06/27 by Nalates Urriah

Server 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 … Read more

Firestorm 5.07 Released – Should you update? Why?

2017/06/21 by Nalates Urriah

Tuesday the 19^th, 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.

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.

Second Life – News 2017 w25

2017/06/20 by Nalates Urriah

Servers

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.

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.

Second Life News 2017 w24 – New Shiny

2017/06/13 by Nalates Urriah

Servers

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.

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.