✨ Feature Requests

At present, lights are clamped to an "imaginary" range of 0 to 1 that have no basis in physical reality. The GLTF spec defines a physically based light falloff and specifies real world radiometric units - which is aligned with most major game engines and 3D modeling applications. This change should apply to all sources of lights - point lights, projectors, and the sun/moon. Sun/moon would be easiest to support first.

As it stands, Second Life (secretly) supports global illumination via reflection probes. This is confusing to users - as we only really specify it as part of the reflection probe. In reality, there's often a need to have more light probes for GI than there is for reflection probes. This change means that: Probes can have three modes. Reflection, light, or both Existing probes would be both for reasons of content compatibility Potentially, changing how we store light probe data (using spherical gaussians or spherical harmonics or some such)

Adding the .gif files to the allowed list to upload, letting us create animated particles, textures without the classic LSL moving into the same framed image

SL has for a very long time supported dynamic shadows for up to two projector lights. This requests asks for: A viewer-controlled count of shadow casting lights Shadows on point lights Note that this has technical implications in the viewer, namely how shadow filtering works. The shadow filtering in the viewer is handled as a post process that can filter up to four shadows in the viewer - ambient occlusion, sun/moon, and up to two projectors. This change requires changing how shadow filtering and sampling works, which in turn changes how shadows will look.

Schedule notice send in advance

Allow users to create and rez objects larger than the current 64-meter limit to support large-scale builds like floating islands or full-size ship models (e.g., a 270-meter Titanic). Rationale The 64m limit creates unnecessary friction for creators in private or controlled environments. Splitting large meshes increases workload during modeling, uploading, and placement—especially when iterating. Supporting larger objects would streamline workflows and enable more ambitious content. Implementation Consideration To manage potential misuse, this capability could be selectively enabled in certain regions or estates at the owner's discretion.

Problem Currently, when users need to reset their avatar's skeleton, the changes only apply locally to their own viewer. For other users to see the reset skeleton, the avatar owner must use a workaround that involves resetting their skeleton locally, teleporting elsewhere, and then teleporting back. This process is cumbersome and interrupts the user experience. Solution Implement a system where when an avatar owner resets their skeleton, it automatically sends a packet to all viewers that can see that avatar, instructing their clients to also reset the skeleton display on their end. The same functionality could be extended to animations, allowing users to clear all animations across all viewers simultaneously. Links BUG-225527 Github: Make it so that reset skeleton is a networked ViewerEffect

Yearly Premium Plus is quite a big investment, but I know that I can't do much of anything within just one month, so I tend to shy away from having more than one Premium Plus avatar. A 3-month long Premium Plus membership would be long enough to, for example, try out a new 2048 LH theme to see if I like it. I just dumped my Mediterranean, tho I wanted to keep it, to try a Tiki. If a 3-month membership had been available, I would have kept the Med and just bought a quarterly PP to try tiki.

I've thought for years that there should be some sort of bonus or perk for someone who has been active in SL for ten years (and more after 20! years). It could be a discount in the membership fee, additional land, a bump in the monthly stipend or just a one-time (or maybe annual) "Happy Rez Day!" deposit of L$. There should be some sort of "minimum activity" requirement in there so the perk doesn't go to dead accounts. Those of us around this long (16 years for me) are not just Residents; in RL we're Ambassadors. We're the folks out there actually trying to explain what this crazy place is and why they should try joining us. The Old Av Bonus would recognize that good work.

I suggest an enhancement to the Bakes on Mesh (BOM) system by introducing an opacity option for BOM layers. As a designer, the current limitations of BOM force us to add additional mesh layers, particularly for makeup applications. This increases mesh complexity and necessitates the use of complex HUDs. Enabling opacity control on BOM layers could eliminate the need for extra mesh layers, thus optimizing mesh complexity and enhancing overall performance. Additionally, this would allow for greater flexibility and creativity, as BOM makeup layers wouldn’t be limited to one or two mesh layers (depending on the number of mesh layers created by a designer). With the recent introduction of 2k BOM textures, the capability to adjust blend modes directly on BOM layers would be highly beneficial for both designers and users. It would offer more customization options and improve the user experience. It would positively impact the creative community and contribute to a more streamlined and efficient design process.