✨ Feature Requests

Some kind of cloth simulation would be great, I think everyone agrees on that. Except that it's computationally very expensive, and while it's practical in a game where you've only got one main character and care can be taken to avoid much simulation happening at any one time, SL needs to render up to a hundred (sometimes more) "main characters" at a time. There's already a feature request in for some kind of cloth simulation tracked here: https://feedback.secondlife.com/feature-requests/p/weighted-clothing-material-with-collision -- in the thread people have discussed some things like collision volumes to stop the mesh intersecting, which was always a problem with the old flexi solutions too. All these things would be great, but maybe there's a computationally cheap way we can at least get part of the way? People have tried things using spare bento bones and animating, but that doesn't coincide with actual avatar movements, so it's really no more than a gimmick. I admit this is a bit beyond my wheelhouse, but I had a crazy idea, spoke to a few people about it, and they seem to find it intriguing, so I'm bringing it here. I call it "Velocity Bones". Imagine we have an extra (or maybe a few) bone in the skeleton, which mirrors existing bones, but all motion is delayed . When you move your avatar, the velocity bone starts moving a second behind the rest of your avatar, and stops moving a second after it. When you play an animation, the velocity bones will animate as per their mirror bones, but start a second later. This gives a bone that rigged mesh can be weighed to, which will be where you just were a second ago, and catch up with you when you come to rest. For example, imagine a ponytail with the end of the tail weighted to this velocity bone. You move left, the ponytail will trail to the right. You stop, the end of the tail catches up with you. You jump down from something, it bounces upwards. You dance, the end of the tail takes a little time to catch up with the top of the tail, giving a basic simulation of inertia. This doesn't solve collision problems, doesn't allow for things being moved by wind, but otherwise could provide us with something akin to what people used to use flexi for with attachments. We could have a cape flowing behind us, that moves dynamically as we fly. We could have moving hair. Clever people might even be able to put a bit of reasonably convincing movement into a dress with it. Best of all, it should be pretty computationally cheap. As I say it's beyond my technical wheelhouse -- I'm not sure how practical it would be to split-animate a skeleton in this way. However people have been crying out for flexi mesh or something for years, and since the idea occurred to me I thought I'd throw it out there and see if it gets any traction.

Feature Request: View Previously Used LOD Triangle Settings for Uploaded Meshes As a mesh creator, I frequently adjust the triangle limits/settings for each LOD level during upload in order to achieve the best balance between visual quality and reasonable land impact. The challenge comes when a mesh later needs to be corrected or updated and reuploaded. Currently, there does not appear to be any way to review the LOD triangle settings that were successfully used in the original upload. Unless creators manually document every upload externally, the original working values are effectively lost. This results in unnecessary trial-and-error reuploads, inconsistent optimization, and difficulty maintaining the same visual/LI balance across updated versions of a product. Suggested enhancement: Provide a way to inspect the previously used LOD settings for an uploaded mesh object. One possible implementation: * Right-click mesh object * Advanced / Developer submenu * “View Uploaded LOD Settings” or similar The displayed information could include: * High LOD triangle limit * Medium LOD triangle limit * Low LOD triangle limit * Lowest LOD triangle limit * Physics settings (if available) * Upload optimization method used This would greatly improve creator workflow efficiency, consistency, and asset maintenance, especially for creators managing large product catalogs.

Hello, I have been making Windlights/EEPs for photography and other purposes for some years now and have recently been looking into creating Day Cycles but one thing that is lacking in EEPs makes creating brighter, more colorful nights in day cycles difficult is the lack of the Glow Focus and Glow Size for the moon. In an EEP this is less of a problem as it is a single time of day where the sun and/or moon are in static positions and you can just position the sun where you want the moon to shine from and add a moon texture to the sun, but with day cycles the sun/moon move around the sky as the time of day changes and if you want them to move about organically you can not use the sun as a substitute or aid to the moon. Having these two sliders for both celestial bodies instead of only one would unlock far more potential for photographers, home owners, vendors and others to experiment with and create more and even better environmental settings.

Title: Editor Improvement: Add a "Selection Lock" toggle and position safety boundaries to prevent lost objects. Description: > Editing objects in Second Life can currently be unforgiving, often resulting in lost inventory. I would like to propose two major quality-of-life improvements to the build/edit menu: Selection Lock Toggle: Instead of requiring the user to continuously hold down the left mouse button while manipulating or holding an object, add a "Lock Selection" button. This prevents accidental de-selection if a mouse click slips. Basically you cant click off the object by accident when edit lock is on. Also have a rerun edit object button encase it shoots off in the distance you can return the locked object. Some times return to last known position does not work on edit linked a glitch perhaps and it shoot some place ware you cant find it. Velocity/Distance Safety Cap: Implement a safeguard that prevents objects from accelerating into outer space or off the region bounds during edit slip-ups. This is a critical issue when handling rare, no-copy/mod objects that become permanently lost when they shoot past draw distance or off-region. The reason I need this is because I build huge towns and cities. When I am editing a massive house made of many different parts and I use edit linked, it is incredibly easy to accidentally click off an object while moving it. When that happens, trying to find and re-select that one tiny detail piece or invisible prim again can be almost impossible without tearing the whole build apart. Other times I am editing invisible prim in a wall or door and if they lose selection its a real game to re select them again. Us who spend long hours editing in game who have 1000s of hours working on a project will thank you if this is implemented.

Please allow us to use the voice moderation functions in LSL/Lua. Similar to https://releasenotes.secondlife.com/viewer/26.1.0.20139269477.html but able to be automated.

Currently it is not possible to animate the scale of a bone in either avatars or animesh objects. This seems to be the case mostly to avoid compatibility with avatar shapes as they use bone scale but it causes several annoyances, especially with animesh objects. Since animesh objects aren't influenced by their object size it seems to be entirely impossible to scale them inworld and scaling the root bone in the rig is not possible either. This means to create an animesh object with multiple different sizes we need to upload separate mesh objects. (And each with their own set of animations provided they aren't affecting purely bone rotation, but also location.) Which creates a lot of extra work and cost. Perhaps more subjective: Animating scale is incredibly important for convincing animation that doesn't feel stiff. Especially for more action loaded stylized animations. Squash and Stretch is the first principle of animation for a reason. As things are now, unfortunately it is not applicable for SL.

gravity based physics on clothing with shape collision for skirts and dresses or any clothes that hang and would flow naturally. this would be much easier to create clothing and give it a more natural look as opposed to being bone weighted and rigged which gives cloth an over-starched look.

When will it be possible to make a minimum of 2 shops on the market, at least for premium plus?

It would be great if we could export just a single file from the mesh editor and have the uploader recognize the various _PHYS and _LODn models in there. This simplifies the export process. In a first parse of the file, ignore all objects having the postfix _PHYS and _LODn except for what corresponds to the "High" LOD. In following parses of the file, look for objects in the first parse that has matching names with the relevant postfixes (_PHYS, _LODn) Search for the still missing corresponding models for _PHYS and _LODn in other files in the same folder, like is already done today.

I'm proposing that the 15 impact is replaced by a system that is actually, fully receptive to the content by a user to encourage performant creations rather than expecting an arbitrary number to the Land Impact, smiling and shrugging. At the very least have the LI cost of Animesh lowered significantly to dampen the hesitation by SL users to purchase the content involving it and enable creators who want to implement it. I don't know what goes on 'under the hood' with Animesh other than it's some branch of the SL avatar skeleton, but there's a lot of uses where it could be given non-character, environmental roles to animate content with .ANIM rather than using keyframing with scripting (for example) that are currently not viable due to the insane upfront LI cost. It's hardly viable for a flying flag to be 20 Land Impact, especially when a user would scoff at the idea of such a cost and go find their ugly 1 prim flexi flag, waving at us from 2007. :)