🪰 Viewer Bug Reports

• Use concise, precise descriptions• Do not include sensitive information. • Create a support ticket at https://support.secondlife.com for individual account issues or sensitive information.
Deed to Land Objects Prevents Modifying Notecards or Changes to Contents in a deeded object.
Make a notecard and set all permissions in Properties to Next Owner can Modify, Copy, and Transfer. Also check all boxes user Permissions, including Group Share. Write any text in the notecard. Create a simple prim on your Deeded Land. Check that the object is also in the land group. Copy above notecard to Content tab of prim object. Before deeding the prim to the land, you can read and edit the notecard, as the owner of the land and the owner of the prim object. Click Share and Deed buttons to deed object to land group. Go back to notecard in contents, and you will not have permission to read or modigy the notecard. Note the notecard had full perms before transfering to the object. You, as the owner of the group cannot delete the notecard. If you then check the perms of the notecard in Content, the Share box was unchecked. Trying to change perms with Permissions button gives an error message, cannot add perms. If you try to add any object, script,or notecard to Contents, one deeded, you will be blocked with red block icon when trying to drag from inventory to Contents. This makes group members with perms to edit a deeded object impossible to change anything. A deeded radio for instance cannot change or update station urls in the notecard. Note I am the owner and creator of the object, the notecard, and the land group and the land. Other group members with edit permissions are also restricted from modify of deeded objects. This BUG was first noticed in the Second Life Release 7.2.2.17774206511 (64bit) viewer, and also the Firestorm Firestorm 7.2.2 (79281) Sep 9 2025 18:02:30 (64bit / SSE2) (Firestorm-Beta). In all versions before this, one could both read and modify notecards that had full perms in Contents, and well as being able to add more scripts, notecards, and objects to Contents with only Edit permissions for group objects.
3
·

tracked

Problem with Vsync and close all game
Hello. I am reporting a persistent and critical instability issue with the Second Life Viewer (this occurs on both the Official Linden Lab Viewer and Firestorm Viewer). The application experiences an immediate crash upon the very first launch after a system boot. The Viewer then runs completely stable on the second attempt without any system changes. This bug is consistently reproducible across different Viewer versions. This issue occurs on the following system configuration: Operating System : Windows 11 Pro 64-bit Processor AMD Ryzen 5 7600 Graphics Card : NVIDIA GeForce RTX 4060 NVIDIA Driver Version: 555.99 System RAM: 32 GB DDR5 Windows Power Plan: AMD Ryzen Balanced. To achieve any kind of stability upon initial launch, two specific workarounds must be applied simultaneously: VSync Must Be Disabled: Vertical Sync (VSync) must be explicitly DISABLED within the NVIDIA Control Panel for the Viewer application. Run as Administrator: The Viewer client must always be launched with Administrator privileges. All standard and advanced troubleshooting methods have been exhausted. The following critical tests confirm the issue is software-based: Hardware Stability Confirmed: Power Supply Unit (PSU) and GPU stability have been verified. The computer successfully passed a full 15-minute GPU stress test using FurMark (running at 100% usage, even with VSync on) without any system shutdown or crash. This rules out hardware failure (PSU/Overheating). Software Scope: The problem is confirmed to occur on the Official SL Viewer, Firestorm Viewer, and older Firestorm versions. Other Steps: All drivers/OS are updated, cache has been cleared multiple times, and various graphics debug settings (VRAM detection overrides) have been attempted without success.The issue appears to be rooted in the Viewer's core initialization process (likely VRAM allocation or system file access) during its initial cold start on this specific hardware configuration.I have included the Crash Logs from a failed first launch attempt. Please use this information, particularly the log files, to diagnose why the core Viewer code is unstable upon initial launch on a system running the NVIDIA RTX 4060. I didnt do picture. because dont show me only just close me all game and computer. i have that from one week, before did work normal and without problems. A rigorous, clean reinstallation of the NVIDIA drivers (using DDU) has been performed. Following this process, the complete computer shutdown issue has been resolved, but the game still crashes on the first launch attempt. I must use the workaround (Run as Administrator + VSync OFF) for stable operation. This definitively confirms that the bug lies deep within the Viewer's core code and requires your intervention. With close Vsync and I'm starting as an administrator game close too. close me again but after 3 h. i did try too take off my all avatar and wear old from firestorm but is same. i send one picture what show me after close game.
1
Load More