🪰 Viewer Bug Reports

There's a visual glitch when using more than one BOM texture layer on a Universal Aux channel if there's partial transparency in the texture using Blinn-Phong textures. I've made BOM textures with partial transparency for rigged fairy wings, so that customers could layer a stripey texture on top of the main wing texture. However, it's as if there's an outline of 100% transparency around the edges of the upper stripey texture that punches a hole straight through the underlying wing texture as well. It shows up the most when in front of a bright background. I tried making the stripe texture completely black with a 100% transparent background by converting it to a vector and then converting it back into a raster image in Photoshop, and this minimizes the issue so that it's only visible if you're very zoomed in, but this means there can't be layered BOM textures with blended edges at all on the Aux channels. I had envisioned being able to make add-ons like colorful peacock 'eye' spots, faded edges, etc so people could really customize their wings' look, but this doesn't seem to be possible right now.It happens whether the files are PNG or TGA, with or without an alpha channel.Since the main wing textures have partial transparency, changing the blend mode to alpha mask would not solve the issue. Hopefully you can see the problem in the screenshots. You might at first think it's the white outline 'halo' issue but no, it's actually that the edges have an outline that are completely clear so the background shows through.

Rez a prim Set material to PBR Metallic Click Texture Picker and set material to Blank Edit Selected material and Base Color, ORM or anything else Attempt to remove material using Texture Picker and Selecting None Any edits are removed, but the Blank material remains on the object If you select a saved material from Texture Picker, the material can be removed by using Texture Picker and Selecting None. This is the expected behavior.

Clip Demonstrating Behavior: https://youtu.be/LuTbgsij74M Additionally, it appears that the texture alignment overlay is always tied to the transforms of the Blinn-Phong material. To Reproduce: Rez two prims and place them next to each other. Place a glTF material on adjacent faces on prims. Set texture mode to Planar Ensure both texture transforms of both faces do not match. Click Align Planar Faces Checkbox

Description: When importing a Collada (.dae) file from Blender into Second Life, one or more objects within the mesh linkset frequently get renamed incorrectly, even though all object names are clearly and uniquely set in Blender prior to export. This issue occurs systematically: All objects are properly named in Blender. The .dae file is verified to contain the correct object names. However, upon import into Second Life, at least one object's name is arbitrarily replaced by the name of another object in the linkset. This results in duplicate names in the final imported mesh, despite no such duplication existing in the original .blend or .dae. This bug makes it extremely difficult to manage and script mesh components reliably, especially when using scripts that rely on precise object names via llGetLinkName(). Steps to Reproduce: Create a multi-object mesh in Blender with uniquely named objects. Export to Collada (.dae) using SL-compatible settings. Import into Second Life using the Mesh Uploader. Observe that one or more objects are renamed incorrectly during or after import. Expected Behavior: Each object should retain its unique name exactly as defined in Blender. Actual Behavior: At least one object name is replaced by another object's name, leading to incorrect duplication. Notes: This happens regardless of naming conventions (e.g., simple vs. complex names, underscores, numbers, etc.). It's not caused by Blender's export; inspecting the .dae shows correct names. The issue seems to originate during SL’s import processing stage. Please investigate and correct this persistent and highly disruptive behavior. Just a final note: it's been this way for years. It's annoying having to check each object name one by one just to find the one that's not named properly.

I have not tried this on the SL viewer, and if asked to I will certainly do so, but with the current release of Firestorm I have found that the root object assignment upon uploading a DAE file with multiple objects the resulting linkset inworld will be random, where I would expect it to be either the last or the first object listed in the DAE file, preferably the first one since in Blender that's the "Active" object. My testing as follows: Select to upload a DAE file that contains multiple objects, in my case where the object "Cube.nnnn" is the first listed one. Set LOD settings and pick one of the LODs to serve as Physics too. Complete the upload, and rez the object. Find out the root of the linkset. Repeat the steps a bunch of times with the same DAE file. Whenever the cube is not the root, the object that becomes the root gets the name of the cube, losing its actual object name. The cube itself keeps its name, resulting in two objects in the linkset with the same name. Attached is an image showing three of my attempts (out of maybe ten uploads of the same DAE). So, why is this important? Well, my case is that I am building a full region terrain with my wife, which requires splitting the mesh up into 64x64x64 chunks (or less). It also requires fitting them together exactly inworld. We found that the way to do this properly, we'd enclose the component meshes in 64x64x64 cubes, which can easily be aligned to each other, and in relation to the region of 256x256, a total of 32 cubes for one layer covering the whole region, it's easy to place them on the grid by way of calculated offsets. We can also automate the placement of the cubes using scripts, by having the script look at the name of the root object and then move the cube to a predetermined position based on that name. None of this works however, if the cube isn't the root object. It's easy to change it to be the root object, if one has one or two linksets, but dealing with a multitude of them it's quite a lot of extra work, especially during testing (on the beta grid). If it's needed for testing, I'd gladly send the DAE file, and I can send the already uploaded cubes (displayed in the attached screenshot), they are on the beta grid not on the main grid. Thank you!

Create some PBR content in one viewer (say the Linden viewer) Adjust some Materials properties (scales, offsets, metallic-roughness maps) of that content using another viewer with a different cache (I used Firestorm's PBR beta but could have been a Linden viewer using a different cache location), then go do other stuff at a different location and eventually logout for a few hours Switch back to the creating viewer, fly and teleport around, edit other stuff for hours, then return to the content created in Step 1. Behold that all the changes made in Step 2 have reverted, including in the editor. Logout and switch back to the viewer used to make the Step 2 changes, noting they're restored. Clear cache in the original viewer, login, and find the changes restored in this viewer, too. If this is expected behavior, it surely wasn't expected by me! Knowing nothing about how the viewer cache is actually implemented, I'd naively hypothesize that something about how PBR Material override properties are stored on the region or in cache make them invisible when determining whether cached instances are valid.

When editing texture repeats, etc., pre-PBR, the surface showed each repetition of the texture map outlined (with a crosshair in the middle) rotated and sized according to the current settings for that map. In PBR that outline now seems to be static and correspond to the extent of the entire UV map on the object itself (or something? it's missing altogether when adjusting the Emissive or Normal maps' transforms). Is there some reason we shouldn't have the old, useful behavior?

Issue: An item rezzed by a rezzer, or rezzed by dragging out of a prim, can be grouped and coalesced back into the object, incorrectly updating the last-selected object as a coalesced one. It reasons that each selected which were rezzed separately be placed back in the object separately. Now that we can pick up objects as a group but still separated, the Build > Object > Save Object back to Object Contents should respect the form it was rezzed in and put it back as singles of the same name as well. Why? Right now we can make really simple rezzers that just let us organize stuff willy nilly but to save updates made (like recoloring, relinking, etc) we have to Save Back to Object Contents, one at a time. If we could do it as a group, we could select a whole build and choose the option, any anything which has an object_rezzer key still around can be updated in one stroke. This would be phenomenal for keeping builds organized and updated! Note: This may create issues with mixed coalesced and linked items. In that case, it should be prudent to take the coalesced items first, and then go through the rest of the selected list. If this is unfeasible, a warning is in order if saving a previously coalesced set back. Reproduction: Rez 3 prims, name 2 of them uniquely Pick the named ones up separately Place them in the object inventory Drag them out of the inventory to rez them, one at a time Select both of them and Build > Object > Save back to object contents Attempt to drag each out again. The last selected one before saving is now coalesced as both, and the other is not updated.

Rez a prim, change to sculpted, use the "plate" sculpt map from the library and the prim disappears. Friends on firestorm can see it, I cannot. I can take it to inventory if I"m lucky usually I cannot. I must relog to see the sculpt. I teach building classes so to avoid this downfall, I give them the sculpt. Sometimes it appears, sometimes it does not. Students have to relog to see what they are building. This happens on any sim, any time of day. I have more trouble with the plate sculpt than sculpts I make, but really either way it makes sculpts nearly impossible.

Edit mesh - go to Blinn-Phong texturing and tint the color. The face that is being edited will turn white or nearly white till the mesh gets out of Edit Mode. Precise tinting is difficult as it's impossible to see the changes while working. SL Prims works fine, it's only mesh editing as far as I can see. Tested at Default lighting settings.