✨ Feature Requests

The alignment tool is very useful for aligning objects to an axis, but it doesn’t work on linked prims, forcing us to unlink them first. What about enabling alignment for selected linked prims when the ‘Edit linked’ checkbox is checked?

Hi can you please increase ocean depth to 12288 meters for sailing, submarines and aquatic gameplay 256 x 48 = 12288 meters The ocean's average depth is about 3,682 meters (12,080 feet). The deepest point, Challenger Deep in the Mariana Trench, reaches approximately 10,994 meters (36,070 feet). The ocean is divided into several depth zones, including the abyssal and hadalpelagic zones, with the latter being the deepest. Depth zones of the ocean - World Ocean Review World Ocean Review Here's a more detailed breakdown: Average Depth: The average depth of the ocean is around 3,682 meters (12,080 feet). Deepest Point: The Challenger Deep, located in the Mariana Trench, is the deepest known point in the ocean, reaching approximately 10,994 meters (36,070 feet). Depth Zones: The ocean is divided into different zones based on depth: Abyssopelagic Zone: Also known as the abyssal zone, it extends from 4,000 to 6,000 meters (13,100 to 19,700 feet) and is characterized by near-freezing temperatures. Hadalpelagic Zone: This is the deepest zone, extending from 6,000 meters (19,700 feet) to the ocean floor, with constant temperatures just above freezing. https://www.google.com/search?q=ocean+depth&sca_esv=3d1e29cf7e253e0e&source=hp&ei=BvyMaNzFMJDawN4Pm-Gn-AE&iflsig=AOw8s4IAAAAAaI0KFo01jzOl-MnFXk7SYTjNEa_d3fXd&ved=0ahUKEwjc4PqElOqOAxUQLdAFHZvwCR8Q4dUDCA8&uact=5&oq=ocean+depth&gs_lp=Egdnd3Mtd2l6IgtvY2VhbiBkZXB0aDILEAAYgAQYkQIYigUyBRAAGIAEMgUQABiABDIFEAAYgAQyBRAAGIAEMgUQABiABDIFEAAYgAQyBRAAGIAEMgUQABiABDIFEAAYgARItAVQAFgAcAB4AJABAJgBcKABcKoBAzAuMbgBA8gBAPgBAvgBAZgCAaAClwGYAwCSBwMwLjGgB_UEsgcDMC4xuAeXAcIHAzQtMcgHIQ&sclient=gws-wiz

The 'Skin' body part inventory type should support PBR materials. In other words, add PBR to the skin baker. Many of my characters have non-human skins such a fur, scales, metal (robots), stone (statues), wood, or other interesting and fantastical materials. Opening up avatars to PBR materials would allow these to be used directly without relying on appliers. As an initial release, PBR could be added to just the "skin" rather than clothes, tattoos, and the 'universal' clothing type. Any "legacy" clothing worn layers worn over top would be treated as "Base Color" and set the normal, roughness, metalness, occlusion, and emissive maps to "default" values (where not transparent) so the skin material doesn't shine through. Alternately, PBR skins could disable all legacy clothing. Whatever gets us PBR skins fastest. Later on, PBR clothing could be added with different blend modes. A "robotic" or "doll" tattoo, for example, could blend a normal map onto the skin to create different looks for the base skin.

Currently we can't update animesh size and have to upload multiple versions of the mesh in different sizes, and upload all animations for each size. I did some research in the viewer's code, and it appears to me that it's extremely easy to add a feature to adjust the global size of an animesh by modifying the llcontrolavatar.cpp file. Here is the current setGlobalScale() function: void LLControlAvatar::setGlobalScale(F32 scale) { if (scale <= 0.0) { LL_WARNS() << "invalid global scale " << scale << LL_ENDL; return; } if (scale != mGlobalScale) { F32 adjust_scale = scale/mGlobalScale; LL_INFOS() << "scale " << scale << " adjustment " << adjust_scale << LL_ENDL; // should we be scaling from the pelvis or the root? recursiveScaleJoint(mPelvisp,adjust_scale); mGlobalScale = scale; } } And here is a modified version that currently takes into account the X size of the main prim: void LLControlAvatar::setGlobalScale(F32 scale) { if (scale <= 0.0) { LL_WARNS() << "invalid global scale " << scale << LL_ENDL; return; } scale *= mRootVolp->getScale().mV[0]; if (scale != mGlobalScale) { F32 adjust_scale = scale/mGlobalScale; LL_INFOS() << "scale " << scale << " adjustment " << adjust_scale << LL_ENDL; recursiveScaleJoint(mRoot,adjust_scale); mGlobalScale = scale; } } Note that I replaced mPelvisp by mRoot because using mPelvisp does not correctly adjust the animesh's movement during the animation." It works wonderfully. Of course, this modification as it stands could affect many existing animesh objects, so we need to add a parameter to the object, 'ANIMESH_SCALE_FACTOR', which would be set to 1 by default, adjustable via script and by manual editing of the object. We would then have something like this: scale *= mRootVolp->getAnimeshScaleFactor; Here is a gif, you can take a look, the 4 dogs are all the exact same animesh, I only changed there main prim X scale : https://gyazo.com/de2dc2904bcb4e6b8737514aa7db7d2c

Can we possibly get the ability to use Linden water, or its unique visuals, on surfaces such as a prim in the future? Existing attempts at prim water are decent, but all lack the distortion element provided by the Linden water which adds immersion and realism.

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.

Hi there, sorry if this is a noob suggestion. And has been discussed and thought about a lot already. Question: In both pbr and old-method textures could we please have a colour tint option in the normal panel. Laying over a "normal-ish-blue"** tint of our own could be a way we can adjust normals strength in world. I have no idea if this will work from a programming/viewer/world point of view. But sometimes instead of adjusting the normal itself I just open it in krita and make a layer over it and set some opacity on that layer and fill it with a "normal-ish-blue" colour, this lowers the normal effect without having to rebake it. So if we have a tint option in the normals like we do for spec... it might work? and be very helpful? IF this does workout, perhaps limit it to only a "normal-ish-blue" range for choice so people don't go putting red over it for instance. I think it could really help folks who are using different windlights with products from different creators to balance out the depth of items in the scenes they create. How that needs to work from a dev point I obviously have no idea, but it could be helpful if possible? **range of the blues that a normal map uses

SL is getting very old now, that old system template for creating BOM is sooo outdated. The issue I face constantly is making an alpha for a body for a dress or top that has only 1 arm, the old template makes it impossible to do this. You might argue and say well the mesh bodies have their own systems, but take the reborn body for instance, it has section to hide down to the elbow but then it uses 1 long section for the rest of the arm. While recreating this template to fix this issue, why couldn't you make the system allow us to use Udims. Would make our life so much easier, especially for those who make tattoos.

Note: I know this was suggested before and it's tracked. I know this will be merged. That's okay, I wanted to give more suggestions on implementation and answer "why" beyond that it would just be a nice feature. Problem: You don't want to see stuff made by a certain creator on the marketplace. There may be a variety of reasons for this. Here are a few examples. You have the shop owner in game block due to harassment, drama, or other personal reasons and don't want to accidentally give this person money. The vendor is selling rips. The seller has a business model you don't want to support. Maybe you don't want to buy clothes that are no mod, maybe they have shady business practices that involve over-editing their ads, or using AI on their ads resulting in false advertising. Maybe the seller's content makes you deeply uncomfortable such as selling adult products but the models scream childlike and you don't want to see that. The seller is flooding the marketplace with thousands of generative AI textures to make a quick buck, making it impossible to find high quality textures. This is a growing problem that needs urgent addressing. Solution: Allow us to block the shop and/or the owner of the shop. Owner might be better in case the marketplace someday expands to let a single user have more than one storefront. Or both. Blocking a particular product may also have its place. Implementation: Beneath the flag listing link there would be additional links: Block this shop Behavior: Browsing and searching omits all products from the store. Adds shop to a block list. They can be removed from block list if needed. Block this seller (<--- Alternative, or TBI if multiple storefronts ever becomes a thing.) Behavior: Browsing and searching omit all products from any and all products from the store. A popup that asks, "Do you want to block this person from your shop as well?" may be a good move in some circumstances. They can be removed from block list if needed. Hide Product Behavior: Omits an individual product from search and browsing. Unhide Product Behavior: Removes product from hide. How would you find a listing if it was hidden? Give people a checkbook to show hidden products in search and browse. By giving us the tools to better curate our experience with the marketplace you will empower users to find what they want without having to wade through things they don't want to see, increasing the likelihood of them spending money instead of getting frustrated and giving up on the search.

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.