• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: MISC-527
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Yumi Murakami
Votes: 32
Watchers: 8
Operations

If you were logged in you would be able to see more operations.
4. Second Life Misc Issues - MISC

Expose all "secret" building/designing options

Created: 02/Aug/07 07:20 PM   Updated: 22/Jun/09 10:31 PM
Return to search
Component/s: Miscellaneous
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates


 Description  « Hide
There are a large number of "hidden features" in Second Life's building environment. Information on how to access these is often hard to come by, and even when it's easy, often actually using them is highly awkward because of the hoops that must be jumped through to access them. In order for SL to evolve as a creation platform I would like to suggest that all creation features in SL are fully exposed to the user interface. Steps involved in doing this include (but are not limited to):
  • Placing the "invisiprmi" texture in the Library.
  • Exposing all "prim torture" options (eg advanced cut/dimple of a Box (actually truncation)) on the Build panel.
  • Expose the legacy prims (those accessed via script, using 1 in place of the PRIM_TYPE constant) as options in the "Object type" drop down, and all of their torture options.
  • Allow the creation of megaprims, on private islands only, with appropriate warnings given beforehand.

I am aware that many of these features were only retained in SL for backward compatibility, but since backward compatibility will always be necessary they will likely never be removed, so why not allow the full power that SL has to be accessed without jumping through these extra hoops?

In addition to the above changes, the general position should be that all available building features in Second Life should either be: a) forbidden exploits, resulting in punishment under TOS if they are used; or b) visible through the standard user interface. In the event of a previously unknown feature being discovered, it should be put into one of these categories as soon as possible.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Lex Neva added a comment - 03/Aug/07 09:05 AM
All of these are bugs, I believe. I'm not sure what happens when you put a 1 as a PRIM_TYPE... can you give an example/screenshot? Anyway, the reason that these "features" are hidden is that LL really wishes people wouldn't use them. Eventually, some of these may go away. In short, they're not undocumented features, they're bugs.

Yumi Murakami added a comment - 06/Aug/07 09:53 PM
They might have started as bugs, yes. But the reality is that in the here and now, they are treated as features; they are used productively; and they will realistically never be fixed. Removing prim torture would break every single object that uses cube truncation to adjust the centre of a prim for scripting purposes; removing invisiprims would break just about every single pair of shoes in the world. Megaprims are used in all kinds of structures, even by RL employed SL building consultants.

If LL wanted to fix these things, that would be fine - but they aren't going to, because of their policy of not breaking existing items. So let's make them visible instead of having the current system where the people who managed to work out the right people to talk to, find out the secrets, and anyone who doesn't suddenly finds that they can't do what their competitor does and there's no explanation why not. Yes, I know some of these are taught in classes, but if a professional 3D modeler decides to give SL a try, how can they know that they have to attend an absolute novice's building class to find out about hidden items in the UI? Professional platforms don't ship with significant features supplied as easter eggs, and if SL is going to be developed as a professional platform, it can't, either.


Yumi Murakami added a comment - 06/Aug/07 10:12 PM
As for the legacy prims:

Create a prim and put this script into it.

default
{
state_entry()

{ llSetPrimitiveParams([PRIM_TYPE,PRIM_TYPE_BOX,0,<0,1,0>,0.0,<0,0,0>,<0,2,0>,<1,1,0>]); llSetPrimitiveParams([1,PRIM_TYPE_SPHERE,<0,1,0>,0,<0,1,0>]); }

}

You'll get a neat-looking shape. As far as I know, there is no way of making this shape from the regular editor - even with prim torture - because the final prim type used is the "hidden" type LegacySphere, not Sphere.


Elwe Ewing added a comment - 07/Aug/07 04:07 AM
Also unleash megaprims may be a good thing (providing the hollowing problem is resolved before): all SL world is using them.

Rob Kubrick added a comment - 10/Aug/07 03:18 PM
Creating functionality controls to do "Prim Torture" may be benficial. Though sculpties are probably a better path to the future. Remember it's not 'exposing' they would have create not existing user interface.

Megaprims I don't see as a good thing, and hopefully we'll see some cure for them. Though I could see a use for increasing the current maximum sizes to say 20m.

If it's crazy 3d things your after make a sculpty.

The invisible texture would be a helpful addition to the library, as well some more everyday needs.


Rosen Janus added a comment - 11/Aug/07 10:36 AM
In my opinion, invisiprims should be removed or highlighted when you select Highlight Transparent. It's annoying to come across a well-cloaked invisiprim and even be caged by one.

Keep invisiprim's ability to cloak avatar skin and such, BUT FOR GOD'S SAKE, MAKE THEN HIGHLIGHTABLE IN HIGHLIGHT TRANSPARENT!


Yumi Murakami added a comment - 14/Aug/07 12:37 PM
Sculpties still have some issues with collisions, and they can't be made without external software. I don't think they're a good substitute for full access to all the controls of ordinary prims.

Wolt Amat added a comment - 22/Aug/07 09:54 AM
I would agree with Rosen. I don't think Ctrl-Alt-t is a workaround, since it destroys the visual imagery.

Yumi Murakami added a comment - 15/Sep/07 05:33 AM
Rob, they wouldn't need to create "non-existant user interface" because the build window already has a standard "template" to it. Certain controls are turned on or off depending on the prim type and that's all they'd need to change. There's no reason why the advanced cut box shouldn't be turned on when Prim Type is box. (This is assuming that the update messages the client sends have this function, but maybe someone who knows more about the client source could help with that?)

I've made an update to the issue to indicate that I'm hoping for a more general policy. All available functionality in SL should either be forbidden or freely accessible. As I said above, professional platforms don't hide useful features away!


Domchi Underwood added a comment - 30/Sep/07 07:49 AM
The problem with megaprims is with the physics engine, as I understand it. Maybe now with the new version of Havok they can become regular shapes (though I hope not the really big ones), and maybe Lindens will fix the off-center or existing megaprims which makes them awkward to use.

Acru Joliat added a comment - 07/Jan/08 10:38 PM
There isn't a way to get/set the advanced cut of a box/cylinder/prism in LSL, so this should be exposed too, for scripts. (An extra attribute for ll{Get|Set}[Linked]PrimitiveParams that passes a single vector would be sufficient.)

McCabe Maxsted added a comment - 25/Jun/08 05:20 AM
VWR-7827 has a patch for allowing advanced cuts for box-based prims. All of these should really be subtasks (i.e. one feature, one JIRA) to keep this from being resolved as "misfiled"

Yumi Murakami added a comment - 05/Nov/08 03:45 AM
I am raising priority given the recent OpenSpace price increase which was based on "unintended" use of the sims. By keeping options secret, LL encourage all kinds of things to be used without knowing about whether or not they are "intended". Whether they like it or not, the existence of so many crucial hidden tricks for so many years has created a culture of "never mind LL's intentions, do what works". If LL are now reneging on that, that's fine, but they need to do so across the board - and exposing these features is a key part of that.

Adeon Writer added a comment - 13/Feb/09 08:07 PM
There is no reason to not be able to dimple cut (truncate) a cube or cylender. Basic prim torture like this should be allowed without menu trickery.

Phantom Ninetails added a comment - 22/Jun/09 02:55 PM
"Exposing all "prim torture" options (eg advanced cut/dimple of a Box (actually truncation)) on the Build panel."

This request has now been fulfilled in viewer 1.23.


BrianA Corleone added a comment - 22/Jun/09 03:19 PM
Now if they'd only release a useable version with that.

Phantom Ninetails added a comment - 22/Jun/09 04:39 PM
BrianA, you can download 1.23 from http://secondlife.com/support/downloads.php, it is the current release version so it's right at the top with the big DOWNLOAD NOW button.

BrianA Corleone added a comment - 22/Jun/09 10:31 PM
Last I checked there was a texture bug in 1.23 that rendered certain HUDs I relie on nonfunctional.