🪰 Viewer Bug Reports

The attached images demonstrate some rendering artifacts I have just encountered. One was taken with viewer version 7.1.10.10800445603 and one with ExtraFPS RC (7.1.11.11565212741). Both exhibit the same faults. The bells in the images are made of prims. The hollowed-out and profile-cut torus that forms the side wall is now divided into four circular bands with shading discontinuous between them. Viewing in wireframe confirms that these divisions correspond to the actual division into bands of triangles. I experimented with a few more types of prims (the white ones in the images), and several show the same thing. Notice that the surface forming the inside of the torus hole is smooth shaded, only the outside (the "hollow" face) has discontinuous shading. Cylinders also have this, but spheres do not. No earlier version of the viewer is available to compare, but I have never seen this before. I note that an older version of the Firestorm viewer (7.1.9.74745) is still able to login and does not have these faults, but the current one does (7.1.11.76496), suggesting that this is a recently introduced problem originating with the official viewer. There is also a shading anomaly that is common to all the viewers mentioned, and is shown by the Tube prim at the top left of the images. Here too there is a perceptible division into circular bands of the inner face of the outer cylindrical skin of the tube. Yet these bands meet with zero exterior angle. None of the other faces of the tube show this anomaly. As this is present in the older version of Firestorm, this looks like a different problem of older origin. No graphics settings or tweaks to texturing properties (shininess, normal map, switching to PBR, etc.) affected any of these observations. The images are screen shots. Viewer snapshots are the same.

This has been an issue that comes up for since at least version 7.1.9 where sometimes reflection probes will only render when the camera is inside of them then derender when the camera leave like it's getting culled. Most of the time I've run into it is from attaching probes to other items, take them then rerez then out but it wasnt always consist repro. Testing out the latest version 7.2.1 I've seen this is still an issue and now I've found a location where a probe doesnt appear to be attached to anything else and its just a normal inworld object and so far is consistent in repro this problem. Video showing issue. https://drive.google.com/file/d/1GE3ZVVpG86qGXx01u0gW0LnEg_wtMt7Y/view?usp=sharing The location is not my house but another users house so out of respect the location is in the Viewer Info section only. UPDATE: Did more testing and wiped out cache and settings. On High preset for graphics I am able to reliably repro this even in the LL roads at the new Ridgewood exclave sims at the car rez parcels. http://maps.secondlife.com/secondlife/Tequila%20Rosa/103/154/26 Rez a prim Set to reflection probe Notice will derender when camera leave probe. A few times I noticed setting max reflection probes to Ultra would cause probes to render as expected how ever as soon as I change the draw distance from 128 to 192 the same problem started happening again even when I reduced the draw distance back to the original value. In this area there is only about 2-3 reflection probes in a 1-2 region distance. Note that this issue has seen since before Max Reflection probe was implemented just not consistently repro.

Textures are extremely slow to render. This is happening to about myself and a dozen friends of mine. For some reason over the last two weeks textures in SL irregardless of if they are 1k or 2k are taking forever to render a great amount of the time. It also seems to be affecting performance of each viewer as well. I can provide images and video recordings if requested. Clean installing, clearing cache, increasing cache size limits, etc. all do not change the issue.

Description: After attempting to upload a mesh and selecting Cancel, the client crashes. Following the crash, it becomes impossible to relog. Expected Behavior: Previously, after a crash it was possible to relog immediately. Actual Behavior: With the latest changes in the code, the crash is followed by an inability to relog, and this issue occurs consistently. Steps to Reproduce: Start uploading a mesh. Select Cancel. Client crashes. Attempt to relog → fails every time. Impact: This prevents users from resuming their session after a crash, which significantly disrupts workflow. My internet work aweomse, I have fast Fiber.

Create/Apply a glTF Material with a bake layer as the BaseColor to an object. Add/Wear object Create/Apply any editable clothing/skin layer. Attempt to edit the applied layer. Note: BOM bakes and displays properly outside of Edit Layer.

Reflection probes trigger an update every time you cross a parcel connected even when both parcels are using the same EEP setting and same large probe, that is disrupting, it should not trigger an update if both parcels are using the same EEP within the same region, same owner. It's very common in regions like Bay City, Nautilus (not limited to it... ), where we cannot merge parcels, that was not problem before PBR, and reflection probes are quite slow to update ( 1 to 3 seconds ) noticeably "brightening" the scene while its updating. In my case I have several in Bay City, and 3 scenes share two or more parcels connected. Left an example here: http://maps.secondlife.com/secondlife/Bay%20City%20-%20Moloch/162/227/26 2 parcels, same owner, same region, same EEP... 1 probe, 1 scene... can be observed by walking the concrete walkway. That only happens with "Use Shared Environment", does not happen if you select Midday (the new one) on the viewer as a fixed environment.

on viewer 7.2.1.17108480561 - Default sculpted prims do not upload correctly. the image shows the exact same texture represented 3 ways. On the left, the model was uploaded prior to the version release. In the center, uploaded after the update. On the right, used as a local texture from my HDD.

Been testing this and its a SEVERE bug you need to handle. To reproduce 1 - Create a material. Put a ANY BAKED BOM TEXTURE (i.e. UPPER) on the BASE color slot. 2 - Create a box. Apply material to it. 3 - Pick up the box. Give it to other avatars. 4 - Avatars wear it. Result The attachment on AGENT A shows baked texture on AGENT B and vice versa. Keeps changing when zooming in and out, or if any of the agents rebakes his maps or reattaches anything. Found this happening on my avatars after updating them to BoM. But after a simple test the bug is super easy to reproduce.

Group ejection does not update group list until relog (especially with a bot)

Tested at beta grid Voice 1. In open voice, the audio seemed "muffled", not strong, crisp, clear as Vivox open voice. My partner, whom I was testing with, saw that my voice was blasting red in Nearby Voice, even though my green lines showed normal. My partner even turned the slider to the far left and that didn't make a difference and sounded shrilling. Note that later, when we tp'd back to a normal Vivox sim, everything was fine. I did not experience any of the clipping and saturation. My partner also noticed a whistling sound in open voice. While on the premises, we tried private voice and we did not notice any differences between it and normal Vivox voice, which was a little surprising, as WebRTC was touted to bring better audio quality and clarity.