🪰 Viewer Bug Reports

Create a simple cube (mesh or prim) and scale it to 0.3, 4.0, 4.0. Create another cube, scale it to 4.0, 4.0, 0.3 and place it on top of the first one. Set the sun azimuth so that it shines onto the wide side of the first cube. Move away from the objects and observe that the shadow changes; there is now a fully lit band of light directly underneath the second object. This seems NOT to be not related to: • Materials/PBR -- adding a PBR material does not change this behavior. • Geometry -- the objects are watertight. • LOD -- a mesh cube with all LODs using the full geometry behaves the same. • Physics Shape Type -- Convex Hull and Prim behave the same. I have found only two factors that affect this: Top object thickness -- the effect kicks in farther away with thicker objects. The Draw Distance -- the effect kicks in farther away with lower distances. Interestingly, moving the top object up so that there is a gap between the two object changes the behavior and reduces the effect; see the attached image. PS: I realize that this may not technically be a "light leak" -- but I couldn't think of a better term. PS 2: I have tried to think of ways of designing around the issue, but I don't think there are any realistic options. Most non-trivial structures will encounter this issue in some form or other.

Not necessarily a bug as it's likely working as "intended", but I suspect this feature might do more harm than is ideal currently. The original request for this feature was meant for those who essentially wish to opt-out of the client driving the LookAt animations for their avatar, but in its current state, residents may consider using this feature for one of the following reasons that it is not intended for. DisableLookAtAnimation: Turns off all LookAt animations locally, including those of other avatars who may actually want to use LookAt for its intended use (looking at things) DisableLookAtAnimation does NOT: Hide LookAt animations when viewed by others Prevent LookAt from being broadcast This is fine for debugging purposes, but for those meaning to use it to disable LookAt animations for their avatar permanently (including when perceived by others) it's not ideal. It also "breaks" the LookAt feature for others entirely who do intend to use it for its intended use.

Logging in knowing that offlines have happened (seeing them via email) to find nothing on log in. Relogging and all offlines appear, notices, drop downs, and IMs. Has been happening for at least a week now.

I recently upgraded Firestorm from v6, noticed certain unicode characters in chat and hover text exhibit the bug, installed LL's viewer, saw the same issue. I was told by Monty Linden in the last server meeting to file a bug report for the viewer to get a font pack update. Here are a few out of many problem characters: [2025/04/29 05:36:35] llOrd(textbox): llOrd('🗕',0) = 128469 (0x1f5d5) [2025/04/29 05:36:46] llOrd(textbox): llOrd('🗙',0) = 128473 (0x1f5d9) [2025/04/29 05:36:51] llOrd(textbox): llOrd('🞁',0) = 128897 (0x1f781)

Log in, many of not most of the objects on my mainland estate fail to rez, requiring me to continually clear cache and relog to have an acceptable virtual experience

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.

The new PBR Nacon environment settings that were recently added to the inventory library are set to no transfer, this prevents them from even being moved out of the inventory to edit them I assume this isn't intentional, and if not I think they should be changed to be full perms like all of the other environment settings

When taking a snapshot with Screen Space Reflections (SSR) enabled in the viewer, reflections visible on reflective surfaces in the viewer window are not captured in the resulting snapshot. This results in a discrepancy between what the user sees in the viewer and the final saved image. Steps to Reproduce: Enable Screen Space Reflections in the viewer settings (Graphics -> Advanced Lighting Model -> Reflections -> Screen Space Reflections). Position your avatar in a location with reflective surfaces (e.g., near water, mirrors, or shiny objects). Ensure that reflections are clearly visible in the viewer window on those surfaces. Take a snapshot using the in-viewer snapshot functionality. Observe that the saved snapshot does not include the reflections that were visible in the viewer. Expected Result: The saved snapshot should accurately capture all visual elements present in the viewer window, including screen space reflections. Actual Result: The saved snapshot is missing the screen space reflections, resulting in a visually inconsistent image. Workaround: None known. Affected Versions: [Specify affected viewer versions] Attachments: Snapshot_001.png - Result of the snapshot showing the missing reflections. Viewer_Screen_Snip_Capture.JPG - Screenshot of the scene as seen from the viewer in-world, with reflections clearly visible.

Please, make the viewer icon follow the standard size for MacOS icons.

When a probe larger than 64x64x64 is created, all other reflection probes stop baking normally. They will still update on forced changes but will not update over time. Fixing this behavior or disabling probes above 64m are both acceptable fixes.