🪰 Viewer Bug Reports

I have a persistent issue where whenever I try to Edit Shape IN ANY ACCOUNT on my main computer, in BOTH SL Viewer and Firestorm (completely separate installations), parts of the head, a part of the torso and the waist down become invisible. They look okay on two other computers! On my main computer the issue persists over several accounts with completely different bodies, including the system body and a default "welcome pack" avatar. One exception is the Catwa head where the face go black instead. The same problem happen in both the official SL Viewer (vanilla settings) and in Firestorm, in completely separate installations. Clearing Cache do not help this problem. The same issue persist in different sims. Updating video and cpu drivers did NOT help. Changing windlight did not help. Refreshing attachments, undeform, rebaking, switching bodies etc did not help. The default "Avatar Welcome Pack" have the same problem. Whitelisting in Defender did not work. Changing quality (performance/quality) did not help. Turning off Anti-Alias, texture filtering, mirrors, PBS, and enabling/disabling the vram tweaks did not make a difference. I do not use any custom settings in the driver ("Manage 3d Settings"). Turning off Nvidia surround did not help. The main use a RTX 5090 with Ryzen 9 950X3D. The secondary use a RTX 2080 Ti with Intel Core i7. The third use a GTX 1080 with Intel Core i7. Video example: https://gyazo.com/6bf02aaeb57265934bf23140aa702de4 System: https://gyazo.com/f9da422d4095f1fa626278762e46ba91 Gianni X + EvoX = https://gyazo.com/eab5c895f037a121a6a4cba1b9312d14 Catwa + Legacy (no BoM) = https://gyazo.com/323c9b5f261225374e6d72d53692e81d Reborn + EvoX = https://gyazo.com/71782f6b0e9d79ed259ea73b3b2d569a Default Avatar Welcome Pack = https://gyazo.com/ba87dc1f6c0d2f5c1ba7234afb8d173c I normally run Second Life in 2384x1010 px in order to be able to take 16:9 screenshots without the need to hide chat/huds. Changing the width of the window, such as 1010x1010 causes the right side of the face to go invisible; https://gyazo.com/94f567ed79433836adb90578d1e171ad

Very niche edge case I spotted at random: a glancing reflection of the sun will result in the reflection getting blown out into wrong colors. This affects only the glossy component of Blinn-Phong materials: PBR and environment BP are unaffected. It also requires a fairly specific kind of sky and a shallow angle so it's not easy to spot in everyday use. Repro: 1) Create a cube, set it to blank texture, black tint so the diffuse doesn't interfere with any colors you see. Set specular to blank texture, set glossiness to 255, environment 0. 2) Set environment to sunset (control-shift-N). Open personal lighting settings, set glow focus to 1.0 to increase the sun intensity. 3) View the top of the cube towards the sun at a shallow angle. You should see something like the attached image, with a distorted cyan-blue-magenta highlight in the middle of the sun. Rotating the cube might help seeing the effect from a less shallow angle as well. The effect depends strongly on the chosen sky and angle of viewing, e.g. I can't reproduce it using the default midday, but can see it on a custom sunset as well (PBR-tuned HDR enabled, so HDR or lack thereof doesn't matter). It can be seen on a sphere prim, but only when the specular angle is sufficiently shallow and glancing. Also lowering the glossiness spreads out the intensity of the highlight, eventually making the colors normal.

FIX EEP, Mainland environment cycle are way too dark, see my forum post https://community.secondlife.com/forums/topic/428374-environmental-enhancement-project-aka-eep-feedback-thread/page/41/#findComment-2861867

Requires AMD GPU, Adrenalin 25.10.2 or later. See attachment for a visual of the issue. Toggling AO makes no difference. Please note that there is a risk of this issue being prevalent for many months to come if Linden does not exert pressure on AMD to work together on a solution to this rendering issue. I'm speaking from experience with other software. The workaround is to revert back to 25.9.1 driver. Others complained here: https://reddit.com/r/secondlife/comments/1olf72w/skinclothes_glitching/

A script that reapplies an environment to an avatar at set intervals using a timer event, causes the transition to restart every time it is re-applied, even when it's the same environment, creating a "bouncing" effect where the sun/moon keep moving back and forth in the sky, as well as causing probe reflections to constantly turn on and off as the environment keeps constantly changing. The only way to fix this at the moment is to simply set the transition time to zero, but on some viewers like black dragon the reflection flickering persists despite of this, creating an inconsistent experience between viewers.

When using llSetAgentEnvironment to slowly change environment values in an experience, all parameters change gradually over the transition period except Cloud Coverage: this value changes suddenly at the end of the transition, giving an unwanted sudden change in lighting.

I've become aware of a texture rendering issue that impacts textures when on a face. It's not so much an issue that only impacts PBR textures, but it is exponentially worse and makes certain designs as mastered in Substance unusable as PBR. I'm not enough of a rendering brain to understand what is going on here, but it's my belief this is not correct and is a bug. I hope that this will get in front of the right people to be evaluated and hopefully fixed. This is being demonstrated with a 0-25% gray bi-linear gradient, however anything that uses color and gradients near this will exhibit the same obvious defects. A single example using real-world art is included for reference. Texture UUIDs Dark gradient lossy: cac83520-08b2-500f-b683-1ede13d4e052 Dark gradient lossless: bd66f42c-6b56-780e-c183-3307151f8292 Raw files, non-anotated screenshots, and sample items shown are available upon request but I don't think they will be necessary. As I was sharing this around with creator friends moments before submitting this I was made aware this may be or have been a known bug, and can be alleviated entirely on the material side by setting the alpha mode selector to blended. Masked and opaque do still exhibit the shown issues. This made me frown. There is no alpha channel on the textures shown.

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.

• Cam/zoom onto an object with an animated texture, for example, a fire, running water, etc. • Press Ctrl+9 to reset any current camera magnifications. • Press Ctrl+0 MORE THAN ONCE to magnify the camera view multiple times. All animated textures on the object will freeze. • Press Ctrl+9 to reset any camera magnifications. • Press Ctrl+0 ONLY ONE to magnify the camera view a single time. This does not freeze the animated textures on the object. SUMMARY: Anything beyond a single Ctrl+0 camera view magnification will result in freezing animated textures. This was tested by other users who verified the problem. Attached sample shows pressing Ctrl+0 three times and texture freezing.

Use any legacy hair Observe that it looks normal Zoom out so that it becomes a imposter Observe that it becomes black First image is normal rendering, second image is a imposter rendering.