🪰 Viewer Bug Reports

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.

Differing shadow issues on every viewer I have tried. Not even sure how to put into words everything going on. Pixelated shadows, shadows only sharp at certain angles, some shadows disappear at other angles. See videos attached for examples. Viewers where you can fine-tune shadows (like firestorm) seem to have the same issue, sometimes more exaggerated by certain settings. There is no constant though, one issue could happen on a lower setting and also a higher setting- or not at all. It is incredibly random. Also possibly related is a texture issue- seeing a seam between heads/bodies. I cannot see the seam on my PC, but I see it on my Mac. Other people on PCs and other versions of Mac chips cannot see it. To recreate: 1.) Be on a Macbook Pro M4, current version Sequoia 15.4.1 2.) Simply cast shadows anywhere and move your camera Album with a few videos showcasing issue on both LL Viewer and Firestorm: https://imgur.com/a/sl-shadow-issues-j0QtjoQ

Run Script default { state_entry() { llSetTextureAnim(ANIM_ON|LOOP|SMOOTH, ALL_SIDES, 0, 0, 0, 0, 1.0); } } Set PBR Material with visible emissive mask. (Preferably <1.0,1.0,1.0> Color) Set Glow to 1.00 Set Alpha mode "blend" Setting Opaque or Mask works as expected, setting Blend causes emissive part of the material to snap to zero and not animate. https://cdn.discordapp.com/attachments/1259105650776997908/1259105650932191312/image.png?ex=668bca84&is=668a7904&hm=6e2d81e302f4d2cad40492db69839ab253528e092862fad88e7c6e4024f42308&

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.

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.

I am having an issue where I see a halo around AVs when the environment lighting is set to Midday (Legacy) while running the Official-SL-viewer-7-1-11-12363455226 Also tested with the Firestorm Extra FPS beta 7.1.12.77211. and see the same issue only when the environment lighting is set to Midday (Legacy) under World > Environment > Midday Legacy When set to Midday from the Environment World > Environment > Midday no halo effect appears This issue isn't present when running the Firestorm public release build 7.1.11.76496 that is pre-PBR https://i.postimg.cc/rc44pDxF/Firestorm-7-1-12-77211-Midday-legacy.png https://i.postimg.cc/xjGq3b3v/Official-SL-viewer-7-1-11-12363455226-Midday-legacy.png Steps to reproduce: Menu: World > Environment > Midday Legacy https://i.postimg.cc/SNn0f7VP/Environment-settings.png * The issue is present with even if Screen Space Reflections is turned disabled My GPU is an AMD RX 6700 XT. That being said this halo issue only manifests in Midday (Legacy) in ExtraFPS enabled viewer so seem unlikely it is the AMD GPU or drivers since this issue is not present if the viewer is PBR viewer such as that viewer prior to ExtraFPS such as FireStorm 7.1.11.76496 My friend doesn't see it the halo issue when he runs the the Official-SL-viewer-7-1-11-12363455226 or Firestorm Extra FPS beta 7.1.12.77211 and set his set his environment to Midday (Legacy) Would be useful to know if others users running ExtraFPS with an AMD GPU see this sam issue to better determine if this is a bug that specifically affects the graphics of AMD GPUs.

Enable full screen mode in preferences. Reboot client. off topic, i can get alchemy, the app data folder from an older version on alchemy, to work fullscreen at 5120x2880. But all the modern clients, i run into this error. I need Fullscreen support to record my machinima work, as the work around tend to steal away FPS or compromise color output.

I would like to apply BOM AUX textures on the lashes of my mesh heads but I noticed annoying differences in their rendering when they are alpha (which is the case for lashes). Here is an example : https://gyazo.com/a46d41f4fbbbb8588a82c71d69892870 Above, the texture applied directly on the prim. Below, the texture applied through the BAKED_AUX2 texture. As you can see the rendering is different. The BAKED_AUX2 is "lighter". Why is it so ? For the moment I can not use the AUX textures for my lashes because of that difference...

After login or teleport, it often happens that some objects (usually large props like parts of buildings, landscaping stuff) are not displayed until I (accidently) rightclick on them. In older viewer-versions you could toggle wireframe off/on to force all objects to be shown and there are other tricks to 'unhide' those objects. That issue is well known for many years, for example, look here: https://community.secondlife.com/forums/topic/459592-problem-larger-mesh-props-remain-invisible/ and its a mystery to me why it gets no attention from the devs. Its extremely annoying, almost a showstopper for me. It just happens a lot to me, no matter what viewer I'm using (FS and LL), what PC I'm using and how fast my connection is. I'm not using any exotic hardware or settings. After almost every teleport I'm standing on invisible floors, bouncing against invisible walls and looking at party rezzed buildings.

The orientation of a prim is affecting its bump-map shadow effect (relief). An upside down prim seemingly inverts the effect, turning an emboss into an engrave. This is showing in Firestorm and LL viewer, which was updated moments ago. The effect is shown in the images below -First is a single prim 1m square -Second section is a 4x4 grid of 0.25m prims, rotated differently but textures aligned -Third and Fourth are the same things using Materials rather than Blinn-Phong, which do not have the issue The bug is the Second section showing differing relief amounts even though they are co-planar and same orientation. The difference here is the orientation of the prims themselves.