🪰 Viewer Bug Reports

I've noticed that textures which contain an alpha layer, which use an applier to apply them to meshed body parts (either head or body) lose approximately half of their normal opacity when viewed in PBR viewers. However, when using the exact same avatar in earlier non-PBR viewers, such as Firestorm v6.6.17, the applier texturing appears perfectly normal, with seamless blending of applied textured avatar parts with BOM surfaced avatar parts. Attached below are three photos, showing a large black tattoo which is intended to cover the neck and upper chest. The tattoo is applied to the mesh head (with a HUD based tattoo applier function), and a matching BOM body tattoo is worn over the mesh BOM body. As you'll see, the overall tattoo looks completely dark and normal in the earlier non PBR version of Firestorm (v6.6.17). But, the exact same tattoo loses approximately half of it's opacity in the head section (with applier function) when used in two different PBR viewers, Firestorm v7.2.4 and Second Life Viewer v26.2. Therefore, this is a bug that has been caused by PBR viewers and requires a viewer bug update fix to allow Residents to use their favoured BOM and applier avatar parts together without losing their intended full functionality. A PBR viewer update would also enable the continuation of legacy avatar parts that may no longer be supported for BOM updates, or no longer available and have become irreplaceable. PBR has technically "broken" these body parts.

Second Life keeps crashing on both the regular viewer and Firestorm viewer whenever I am on a busy sim. It will happen even when there's only about 10 other avatars around me/ I tried clearing my cache, lowering graphics, filimg an AMD report and turning off play media and it still is not helping. My laptop is only three years old so that's not the issue either.

I log in Seconod life viewer or Firerstorm the button is greyed in and I have a white dot. I can hear everyone on voice, no one can hear me. My headset is selected in Windows 11 says default in both viewers no one can hear me speak. The white box is checked. I rarely can get it to work if I change from default to my headset before I start speaking or take a call. If I do not the microphone button will go grey. The same rules apply for local chat. I have two samsung odyesy g8 monitors with no microphones on them. and a samsung soundbar for when I am not on headset.

i have tried multiple times on multiple versions of firestorm as well as the main SL viewer to upload mesh with the textures and all i get is a blank model that wont upload, i am using GLB as my file type, but no matter what i do it wont attach the textures like it used to and i already put a jira in... ive tried an older version of firestorm, the newest beta, the newest live version and nothing works... Can anyone help me? The meshes are from Tripo; I have zero Blender knowledge... It was working less than a month ago, and now it is not.

The animation uploader currently allows animations to include additional Bento body bones that are not part of the supported body animation skeleton for standard human avatars, such as Spine1–Spine4. Because these bones are not reset by Second Life's default animation system, they remain in their last animated state after the animation ends. As a result, subsequent, perfectly valid animations can appear broken, even though the problem actually originates from a previous animation. This makes the issue extremely difficult to diagnose and causes creators of correct animations to receive support requests for problems they did not create. Because the animation uploader accepts these unsupported body animation bones without any warning, creators may not even realize they are exporting animation data that can affect subsequent animations. This is not just an issue for individual animations. Full-perm animation packs are widely reused by furniture creators throughout Second Life. A single incompatible animation pack can therefore affect a large number of products created by different people, while the resulting support requests are often directed at the wrong creator. Possible solutions Reject unsupported body animation bones during upload. Warn creators when unsupported body animation bones are detected during upload. Automatically reset unsupported body animation bones when an animation ends. Addressing this would significantly improve compatibility between animations from different creators.

When I zoom out far from my own avatar at a club or other texture-heavy areas, say to simply look around, when I return the camera to my own avatar a lot of the textures on my avatar - including materials - are lowered drastically in resolution and it takes the viewer upwards of 20-30 seconds before they go back to full. A resident's own avatar should never have the textures lowered in resolution unless it's specifically set in graphics > advanced, and should always take priority in staying at max quality according to graphics settings. Go to a club that is avatar heavy, so lots of textures are around - shopping events will probably work here too Wait for the viewer to load everything it can do - draw distance was 128 with textures at 2k maximum for this When your own avatar has loaded fully, alt+cam onto yourself and zoom out about half way to the clip plane - just looking around the area for a few seconds will work here too Return the camera to your avatar Lots of your avatar's textures, excluding BoM, are now super blurry, and will take ages to load back again Image 1 shows how my avatar is supposed to look > image 2 is how far I zoomed out (just across the room at this club) > image 3 shows how blurry my avatar's textures become after zooming back in, which stay like this for 20-30 seconds.

Testing PR for align planar faces for PBR materials https://github.com/secondlife/viewer/pull/5347 in viewer 26.2 it appears to only align the base color textures and not the other textures normal/ORM. Also side note reviewing the github notes it looks like it was only ever tested with a base color texture so it might be needed to add a full material (Basecolor/ORM/Emissive/Normal) to QA testing.

Using the Firestorm viewer 7.2.4 (80712) I created a New Skirt from the dropdown menu New Clothes. I wear the skirt, then when I go to edit the skirt, I immediately crash. I've tried the FS viewer and the SL viewer, and other people have not had an issue. What is causing my viewer to crash when I try to edit the skirt? I tried to upload the logs, but it says its too big.

Created a folder in outfits Accidentally moved it to another location Not allowed to move it back

Two new notifications have invaded the SL viewer for reasons that baffle me as they are distracting, unnecessary, disruptive of work flow, and potentially privacy-busting. The notification that you have typed an invalid character now pops up in the precious upper-right hand corner of the screen usually reserved for far more important notifications such as payments and announcements from the region owners or Lindens. It does not appear as a hover or toast or message at the workspace itself while editing. You can already tell you have an invalid character as you look at the object window or other type of editing window you are working with because your work STOPS. You already know it is invalid because your prompt STOPPED. You don't need your eye dragged up to the upper right-hand space for an invasive, duplicatory message. The notification that you have taken a screenshot that saved to your computer's inventory folders now also invades the upper right-hand corner. You already know that you took a screenshot because...you set up the location of where screenshots go when you selected the settings in Preferences. You do not need a distracting constantly repeating notice of this event happening each time when...you selected this option permanently -- and could change that location at will. The notice displays to the owner of the browser only, but if you copy room chat to make transcripts of office meetings, other various community and public resident meetings, you will see the notice then included -- outing the name you have used to label your system folders on your own computer, which might even be your full real name -- that you have to painstakingly edit out. These are features no one among the general user base asked for to my knowledge. They have the feel of technologists' perfectionism in systems like CAPSLOCK notices which you already can see because you already have capital letters. The "invalid notifications" proposal was suggested here and simply immediately passed through without debate -- but does not have some mass community demand: https://github.com/secondlife/viewer/issues/961 (I will provide a screenshot of "invalid characters" when I can catch the next one) If these intrusive notifications cannot simply be removed, then provide the user with the option to mute them in Preferences. Currently they DO NOT APPEAR in Preferences as an option to mute.