🪰 Viewer Bug Reports

Slink feet used to be a perfect replacement for the "clumps" that go for feet in the system body. But after years I can't wear them anymore with some outfits I really want to keep. I have system avatars with Aeros skins for which I have Slink feet appliers too. System used to be a perfect match with good Slink feet (and hands).

1: Stand in front of a wall or object. 2: Move your camera around to look at the front of your avatar. 3: Press the 'walk forward' key. (up arrow or w.) In previous versions of the viewer, the avatar would turn around and walk in the direction the camera was facing. In the current version, the camera moves and you walk the direction the avatar was facing. Use Case: I use this when performing in plays, when my character has to deliver a line, and then turn around and walk to a new position. It takes too long to manually (via keyboard or mouse) to turn the avatar all the way around. Extra Note: Firestorm 7.1.13 (78266) Jun 14 2025 21:43:13 (64bit / AVX2) still exhibits the old behavior (the avatar turns around). except when using a camera control hud. (it used to work with or without a camera control on.)

within logging in crashing on my viewer. can see others typing in local but what i type does not go through

This weekend (particularly Sunday 6/22), I experienced disconnects every handful of teleports using SL Viewer, Firestorm, and Alchemy viewers alternately. While that's an immediate inconvenience and concern, it's not the root of the problem: The problem is that I don't even know there's a problem. As is always the case with networking issues, "everything else" was working fine; video streaming in web browsers, connections to SL and other websites, Discord servers etc so I was not having an overall internet outage... but then, I can't really do anything here. If there's a problem on my end, I can't tell; if the grid is struggling, I can't send you anything to determine what might have been bottle-necking. When I have a viewer crash, at least I get a bugsplat thing, right? But what happens when I go to teleport to a new region, and 20% of the time, I get a progress bar just sitting still at "Requesting region capabilities" or region handshake? What's really happening under there? I know that after 60 seconds, it'll time out and "Quit" the viewer, but that leaves me with nothing to tell you about what has happened. Nothing crashed and yet, something's wrong~ I've heard many (including Lindens) refer to region changing as an indecipherable and scary mess of spaghetti code, but this is the lifeblood of the platform, and it seems to have phases where error rates go through the roof (anecdotally, during the half-day I had these issues, various group chats indicated I was not alone). A thousand little cuts in silence, and it's hard to know what to report and how. The request here is a bit nebulous, I apologize, but that's because I don't even know what LL needs, but please add something to the viewer to log region changes in some way that is meaningful to you, and that presents itself when the viewer times out and disconnects. You know that screen where I can choose to view IMs offline or Quit, when I have a timeout? Add something there, please, to open the region change log folder. (And pls make a region change log, even just to track the most recent change; it sounds as though this one area of SL activity could use better investigation). That way, when things are acting up, there's something to send to support that hyper-focuses on the specific region-change that caused the problem. I could attach that here, or send it to customer support etc.

http://maps.secondlife.com/secondlife/Pattaya/229/218/21

The current midday eep is GRAY.

I have many products that spin, and they are randomly stop spinning unless right clicking them. This is a very old issue, but i would like this to be solved. To say things clearly, they are set to spin by script, (using lltargetomega, but it's like the information that they are spinning doesn't reach the viewer .. randomly.. (as some of them will be spinning and some others not, and if i tp back that would be some other stoping spinning). And it would be spinning for some people, and not spinning for other present at the same moment.

I have tipjars that combine a non pbr material link and a pbr material link. Sometimes some of them will randomly show the pbr part as a blank material (no texture, no material parameters). In the included captures you can see the 3 hearts on the left are fully blank, and on the right the 1 on the top is rendered normally while the 2 others see their pbr part being blank. (the rainbow part is non pbr). This happens more or less depending on the days .. and one viewer can see them alright while an other viewer will see some of them rendered with a blank material. This issue has been present for months, so it's not just the latest updates. Also it happens on PC or Mac.

Ever since the update a few days ago, loading in has been agonizingly slow. It takes upwards of 15 minutes sometimes to rez my avatar, and even then not all the textures on him load. Meanwhile, it's been half an hour and my surroundings STILL haven't finished loading. This is ridiculous, it's disrupting my enjoyment of the game and my interactions with others. Most of my surroundings are either grey blobs or completely invisible. Some have blurry textures, my head is floating away from my body, my AO isn't working, some of the people are still glowing clouds... This is insane! I've reduced all my settings, I've cleared the cache, I have my graphics set to low, sky to the lowest it'll go. All the usual stuff. Thinking about switching to a third-party viewer because of this. Edit: I entered this room at 10:42 am SLT. At 11:27 am SLT, the room finally loaded. This screenshot was taken at 11:12 am SLT.

this is a sometimes bug, no idea how to reproduce. what we experienced is, that the LL viewer (not yet seen in Firestorm) sometimes shows PBR opaque which was set to BLEND and 0.0 alpha with overrides by script. I report that on behalf of my business partner who said he has no hope for this being solved by LL. so the computer details may vary..