[#VWR-185] Requesting Non-interactable setting for objects.

1. Second Life Viewer - VWR

Requesting Non-interactable setting for objects.

Created: 05/Mar/07 03:40 AM Updated: 09/Aug/07 01:27 PM

Return to search

Component/s:

Graphics

Affects Version/s:

None

Fix Version/s:

None

Issue Links:

Relates

This issue Relates to:

VWR-173 Don't render invisible prims

Description

« Hide

This is a simple request. Have an option in the objects creation menu to make an object non-interactable. Meaning, cameras don't snap to it, and clicks go right through it. This would be very useful for many visual effects that use prims, but when you don't want to mess up the ability to click and focus on things behind or inside it.(prim lighting for instance). To combat abuse with these settings, a retroactive option would have to be added to cease this function if you wanted to (much like highlight transparency) simply to edit these objects, and to inspect objects if they are used for griefing. Otherwise these prims will visually be there, and may be scripted to move or whatnot, but interactive wise, be virtually transparent.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Argent Stonecutter added a comment - 08/Mar/07 06:13 AM

This would be another way to implement VWR-173: if this flag was set on the object and it was completely transparent then it could be left completely unrendered unless "show transparent" was set.

[ Permlink | « Hide ]

Haravikk Mistral added a comment - 04/Apr/07 04:32 PM

As per my addition to VWR-173, an option such as this isn't needed per my original aim (simply to stop rendering prims that aren't seen for performance reasons):

"I still think that 100% alpha, or objects/faces/polygons with 100% alpha textures, should not be rendered, however they should always be downloaded so that touches can still be calculated. Thus, when you click the object is still 'there', but the renderer, LOD algorithm and so-on never receive it.

This way touches still work with existing content AND the renderer doesn't get bogged down processing things that can't be seen anyway. An additional flag therefore would only be required to facilitate the creation of non-clickable items, which would be a new, separate feature."

[ Permlink | « Hide ]

Delerium Hannibal added a comment - 10/May/07 02:53 AM

I commented in your post in VWR-173 discussing the lack of real performance increase you would gain by that feature considering the extra checks you would have to make. I never suggested that these two features should be related, although Argent suggested that yours could be piggybacked on top of mine. I don't think he said that they were the same feature request. Either way, this request is still badly needed for a large amount of phantom objects out there that interfere with the camera. (any sort of "virtual eye candy" like lighting which could envelope a room becomes a nightmare to navigate since when you click on the screen, your camera gets focused on that eye candy prim)

[ Permlink | « Hide ]

WarKirby Watanabe added a comment - 30/May/07 01:03 AM

Agreed. Prim lights in clubs can be a pain and really mess up your camera. But they look so pretty...

[ Permlink | « Hide ]

Argent Stonecutter added a comment - 09/Aug/07 01:27 PM

It would also be useful for overlay HUDs.