🪰 Viewer Bug Reports

When uploading a mesh and moving the mesh uploader preview camera, any HUDs that use llWorldPosToHUD become offset from their correct positions. After closing the mesh uploader, the offset persists. The only way to fully resolve the issue is to relog. Zooming out in the mesh uploader preview can make the HUD appear closer to the correct position, but does not fully fix the problem. This issue has been occurring for approximately a year, I only just identified the mesh uploader as the cause. Expected behavior: HUDs using llWorldPosToHUD should remain correctly aligned regardless of interaction with the mesh upload preview. Actual behavior: HUDs become permanently offset after moving the mesh uploader preview camera until the user relogs. Viewers affected: Second Life Viewer Firestorm Alchemy

I've tried filing this as a 'support case', but Freckle Linden (who?) closed my ticket and told me to bring this issue here. Thank you for submitting your case. After investigation, it appears as though this issue may be a bug or error which would be best handled through our bug report system known as JIRA ( http://jira.secondlife.com ). While our Support team is always happy to help, there are certain technical issues which can only be addressed via a development or engineering investigation. Something strange is happening with the 'account security' emails. I have several alt accounts, and I am seeing a large number of emails saying I've logged in to a new machine. Far more often than I am used to, and far more than seems reasonable. This increase in frequency seems to have started around October 17, 2025. I will focus on just two accounts for the purpose of this report, and I will so you can see the issue clearly. Oct 17 - Of the accounts I logged in on October 17, I received 6 emails (one per user) stating that <account A> or <account B> accessed Second Life from a new machine. <my IP> Oct 19 - Important: <account A> accessed Second Life from a new machine. <my IP> Oct 20 - Important: <account B> accessed Second Life from a new machine. <my IP> Oct 22 - Important: <account B> accessed Second Life from a new machine. <my IP> Nov 4 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 6 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 20 - Important: <account A> accessed Second Life from a new machine. <my IP> Nov 23 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 1 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 1 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 5 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 9 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 16 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 17 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 20 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 20 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 26 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 28 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 28 - Important: <account B> accessed Second Life from a new machine. <my IP> Dec 29 - Important: <account A> accessed Second Life from a new machine. <my IP> Dec 29 - Important: <account B> accessed Second Life from a new machine. <my IP> Now here's the thing. Aside from a couple of attempts to use the mobile viewer, I have been consistently using my desktop computer. This computer hasn't changed. My IP Address (both on our home LAN, and the household IP) hasn't changed! My MAC hasn't changed. My OS hasn't changed. I haven't done any major computer rebuilds or OS reinstalls that would result in notable hardware or software changes. I also haven't logged these accounts in with any other computers. I feel it's important to note that I didn't attempt to log <account B> into SL every single day. <account A> is my 'daily driver' account. These emails are coming in FAR too frequently to be explained by those brief mobile app attempts. The app has not been launched in days, and the device it is installed on, has been powered off and rebooted in the time since. To confuse things more, someone else, in the same household (on the same external IP!) has been logging in from a different computer, and has received NONE of these alert messages.. it's JUST ME and my accounts! I've enabled Multi-factor authentication on both accounts, I've checked my transaction history, both https://accounts.secondlife.com/transaction_history and https://secondlife.com/my/lindex/history.php and I have seen no transactions that would indicate someone is using my accounts without my permission. I only see these notification emails after I log in to my own accounts.. I've never seen them appear any other time.. and no one to my knowledge has access to my email. I do not believe that this is an unauthorized account access issue. These messages are important.. it's important for me to know if my account is logged in without my consent. I value these messages. But at this point, the system is crying wolf.. and it's getting to the point where I've considered making an email filter to automatically delete them before I see them.. because they are only creating false scares and annoying me. Something's wrong with the system here.. whether it's on your end or mine, I can't tell. What I do know is that these emails aren't useful in their current form.. and they should be! They need to be!

upon initial log in after installing the block list is fine block list is empty upon a new log in every log in after that the block list remains empty even after adding avatars to the block list again after clearing cache block list comes back but empties once relogging and letting inventory load completely also happens on the latest firestorm release edit: cannot update to add photo of empty block list

This was not only happening on Firestorm viewer 6.6.17, BUT also isues on SL viewer. Touching any group to change, or trying to use landmarks on notecards: All December, both myself and my wife (on separate pc's) were having the same issues. Any time we would go to use a landmark on a notecard, (whether I made the notecard, or it was also happening with the Hop Around Event notecard) or touch a group to change during advent, we would both bugsplat. Once a bugsplat occurred, we could not log back in for hours and sometimes not until the next day. We would both try the sl viewer, and could not log in there, same goes with the mobile viewer, so it was obviously an sl side issue otherwise why could we not log in on any viewer? When I could not login because of the bugsplat, my wife tried to log me in on her pc and she could not accomplish it there. I also tried her account on my pc when she was unable to login, same result on my pc. It was NOT an internet issue as she was still online when I was unable to login, and vice versa. Rocky Linden in support tried to help. Neither he nor Freckle Linden could find anything wrong with my account or my inventory. Rocky closed my support ticket and suggested I write everything here. The support Ticket was #2446401, you can find all the times I was bugsplatting listed there and the attempts to rectify the issues. During all this, I tried changing to a system avatar, no fix. I uninstalled viewers, reinstalled them, no fix. I cleared all caches, no fix. I have had many more problems than these ever since I started this account. I really think part of it may be the server my account is in as my wife has not had many troubles at all in comparison. The last bugsplat I had was on New years eve. I have been afraid to change groups or use landmarks since. I found an interesting notice on the sl viewer. It states that login and intermediate inventory issues were resolved on Dec 6th. That is right around the same time we both began having this recurring problem with group activations and landmark bugsplatting issues. Below are 2 gyazo pictures of the error messages I was receiving on sl viewer when I could not log back in as well as the dec 6th message for reference. https://gyazo.com/fd511f69a65616ec5b870c9c15fd4dea https://gyazo.com/54593a5c2c12de8cfe5ada832a5da48d https://gyazo.com/dd67a7f07afb1fad77b1586feb776c23

before the 31st of Oct this bug did not appear i use an AMD Graphics card and going 1000m in all sims causes the avatar face/LelutkaHead or clothes to visually bug out with shadows

When you set a face when PBR material to rotated 90 degrees, the actual texure image moves at 90 degrees to the texture repeat overlay. This is clearly wrong behaviour, the repeat overlay should show where each copy of the texture is on the object face, but the texture image moves independent of repeat overlay. To recreate simply rez a cube, add a PBR texture with easily identifiable pots in it, set the face to planar and rotate the texture 90 degrees. Now use either offset to move the texture along either axis and the grid will move along the other axis. The expected behaviour would be that the texture and the grid move together in one direction, as it does with a Blinn Phong texture. Also, when setting a texture scale to 1:1 on a face that is 1 x 1m, the texture repeats twice in both directions on the latest official viewer, this does not happen in firestorm where you get the single stamp of the texture filling the face as is expected.

For the past couple of weeks, I've noticed multiple viewers (Firestorm, Alchemy, Kokua and legacy SL) have been very slow to respond to keyboard inputs. Sometimes I'll have to press the same key up to 3 or 4 times before the input shows up in the chat. At first I thought it was a hardware issue, but I noticed this happens exclusively in SL viewers, not in any other other app on my PC. Here's what I've tried doing, all to no avail: Cleaned the keyboard Restarted the viewer and the computer System diagnostic test Firmware and driver updates Stopping as many other apps and background processes as possible Checked internet connection (excellent speed/ping, minimal packet loss). I can't reproduce because it seemingly happens at random, but for some reason it happens most often between 7-10 PM SLT. This is true no matter how long my PC has been in use that day, and no matter what I've been doing on it. My computer is less than a year old and should be more than capable of handling SL: CPU: Intel(R) Core(TM) i7-14650HX (2419.2 MHz) Memory: 32371 MB OS Version: Microsoft Windows 11 64-bit (Build 26200.7462) Graphics Card Vendor: NVIDIA Corporation Graphics Card: NVIDIA GeForce RTX 5060 Laptop GPU/PCIe/SSE2

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.

Tested on Official Viewer 2025.08 – 7.2.3.19375695301 and on Firestorm 7.2.2 (79439). To reproduce; go to any area that would max out your VRAM. As it currently stands, Windows is not stopping the viewer from using up ALL VRAM, including VRAM that's already in use by the OS or other applications. This causes the computer to slow down entirely, to a point of crashing to desktop, or sometimes even reaching BSOD. I can't imagine it's good for the hardware itself either. In Firestorm, we can limit the VRAM the viewer can access, and this entirely removes the problem (when set to a reasonable amount so the system has some space, in my case from 24gb of VRAM to 16gb of VRAM, while the OS sucked up anywhere between 4 and 8. I don't think this is a viewer issue, but a change in how Windows 11 deals with VRAM, however, the results are detrimental to the user experience.

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