This is an informal test and I use the word ‘test’ very loosely. I just wanted to see what the commotion about crossing in the new AWS servers was about. There is no hard data in this experiment. My computer and connection are irrelevant IMO. The Viewer is Firestorm 6.4.5 Beta, which I used because I have it setup to work with OBS.
There is a long 1 sim wide run from Blake Sea – Azimuth to Blake Sea – Bering of 17 regions. That is a 4.352 kilometer run or about 2.7 miles for the metric challenged. Plenty of room to max out my Bandit 380R (The Mesh Shop – Map URL).
I want to mention The Rubber Bunny. That HUD on the left is made by Kaliska Dismantled of Rubber Bunny. Kaliska makes easy to modify HUDs for various boats and vehicles. I’ve bought a couple (L$49). Plus making some fun vehicles. Among them hovercraft which are a novel SL driving experience.
In 2013 Strawberry Singh posted a couple of articles (here & here) about positioning and moving avatars when setting up snapshots. This was needed for those areas where you do NOT have rez rights. Over time viewer upgrades broke those processes.
Every so often I would check to see if the problems with those processes had been fixed. With Firestorm 6.3.9 (May 2020 release date) I can move the avatar again sort of with her process.
Strawberry explained the process for moving your avatar. (Ref)
Open the Develop menu. Top menu, press Ctrl-Alt-Q to reveal it.
Then enable Develop->Avatar->Character Tests->Allow select avatar.
Press Ctrl-3 to open the Build Panel.
Right-click the avatar. Move arrows appear. Move.
Here is a video showing how it used to work. If you have a mesh avatar, right-clicking the avatar likely is not going to work. Instead, you have to right-click on your name tag. Then it works.
Clubs and various places in Second Life™ use scripts to pull the name of the song playing on their media channel. Recently, the LL function call to request HTTP GET/PUT process changed. In doing so it broke most of the scripts used to get song names.
I must warn you …My Thoughts are dangerous and impure
The thread about the problem, DJ Board Display Not Working Properly, started in late May. BUG-100737 – Shoutcast receivers unable to relay on RC Magnum 17.05.23.326524 was filed soon after. By the end of the month, the Lindens had figured out the problem and were looking at a fix. BUT… the fix will require the scripts change.
If you can’t hear the screams of agony and frustration… get your hearing checked. Continue reading →
Have you heard about people losing inventory? Probably. Seems there is a bug on the loose that can clean you out.
I answer lots of questions on the SL Forum. I hear a constant stream of “I lost…” Mine and several other people’s best answer has been the Firestorm Wiki page: Missing Inventory. But, those steps do not work for this problem.
Today I see there is currently a more serious problem. And even worse, my best-informed authority on such matters, Whirly Fizzle, says there is no fix, for now. Ouch!
So, what is the bug and how are people losing inventory?
Here is what people describe happening. They get a popup saying Trash is full or overflowing. It has a button to empty Trash now. I suggest always selecting LATER. Avoid emptying trash from the popup.
They click EMPTY NOW and poof stuff they are certain was not in trash poofs away. Continue reading →
I do bits when either there isn’t much to report or for whatever reasons I’ve missed UG meetings. This week RL work had me busy. So… its bits today.
Empirically, we seem to be seeing more inventory loss. Apparently Grumpity Linden was at the Thursday Beta Server UG meeting talking about the Lab responding to complaints. Inara made the meeting and covers the discussion (here).
I’ve seen more posts in the SL Forum about people losing inventory. The cause is generally thought to be a poor connection or a flat inventory – having everything in the root or first set of subdirectory folders.
The Lab is apparently thinking either users are accidentally self-deleting things or there is bug eating inventory. While they look for a bug they are changing the viewer’s user interface (UI) to reduce the possibility of accidental deletion.
So, at some point we will see the Empty Trash process changes and another ‘Are you sure…’ prompt when deleting things.
It seems people updating to the current NVIDIA driver are having problems logging in. They crash on viewer launch.
As of April 6, there is an NVIDIA driver version 381.65. This is the one people have a problem with. The previous version 378.92, the one I am running, does not have the problem. So, some people are rolling back to 378.92.
Whirly Fizzle has posted in the SL Forum that the problem has been tracked to NVIDIA’s Shadowplay/Share feature. Turn it off and things work.
We are early in this problem fix cycle. So, we may learn more soon.
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.
SLURL Proxy – Control your SLURL’s
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.
Well, for about a minute… when all the guns in Second Life broke… Now, there are work around steps and viewer fixes and… Whatever, you can again shoot those deserving of annihilation.
So, what happened? Why can’t I shoot that scumbag werewolf and save the hot mini-skirted damsel? Seems the Lindens fixed a problem in the process of building Horizons, that’s my thinking. As they expanded controls for use with Advanced Experience Tools (AET), Horizons is an advanced experience, the scripting functions needed a bit more control. So, as reported some time ago we got new SIT commands. See: Second Life News 2016 w45 and for more details Scripting.
Fallout Wasteland – liqueur.felix
I suspect somewhere in that process the Lindens noticed some REALLY OLD bugs, think beginning of SL time, which are now just oddities for most scripters and fixed them to make it easier (and likely make it more logically correct) to do Horizons. The result is all the weapons designed to deal with those bugs/oddities broke.