• 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: VWR-2773
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Normal Normal
Assignee: Unassigned
Reporter: Jani Myriam
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Implement a "visual mute" feature allowing residents to prevent specific objects from rendering based on object id, creator, and/or owner.

Created: 17/Oct/07 07:51 AM   Updated: 07/May/09 11:18 AM
Return to search
Component/s: Graphics, User Interface
Affects Version/s: None
Fix Version/s: None

Issue Links:
Duplicate
 
Relates
 


 Description  « Hide
Visual spam in the form of large signage on small (often 16sq/m) parcels is rampant in Second Life. Often these parcels are offered for sale to other residents for highly inflated prices as a form of extortion forcing residents to pay to have such signage removed from view.

To address this problem it would be useful to be able to visually mute such objects by simply right clicking the offensive object and selecting the appropriate option from the radial menu. This action would prevent the visual rendering of the object on the resident's client but would not prevent physical interaction with the object. Alternatively, an almost transparent texture could be applied to visually muted objects to provide a subtle visual queue that a muted object exists within the resident's field of view although the highlight feature could also be used to reveal the location of such muted objects when necessary. In any case, however, it would be ideal if visually muted objects were not rendered when a screenshot is taken.

Extensions to this idea might include preventing objects owned or created by certain "visually muted" residents from rendering on the client or using group ban lists to prevent the client-side rendering of objects trusted members of the group have determined to be offensive or annoying.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.