• 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-4459
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Vex Streeter
Votes: 20
Watchers: 2
Operations

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

Composite/Bake together function for skin/clothing layers to reduce need for additional permanent layers

Created: 01/Feb/08 07:29 AM   Updated: 23/Sep/08 01:12 PM
Return to search
Component/s: Avatar/Character
Affects Version/s: None
Fix Version/s: None

Issue Links:
Relates
 


 Description  « Hide
Feature request: add facility to new limited-permission layers as a result of compositing existing clothing/skin layers.

Proposal:
UI edit-appearance -> composite layers -> check boxes to select active copy-perm layers to composite
After compositing, the result is a new layer asset of either the uppermost or lowermost of the selected layers with permissions of the component either ANDed component perms, or nomod/copy/notrans.
Texture upload charge would apply.

There might be some impact to skin designers, though I suspect much less than, say, a facial tattoo layer.

This largely eliminates the need for additional layers ( VWR-1449 ), and addresses one of the major reasons that relatively casual users start ripping skin textures (related to SVC-676 )



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Vex Streeter added a comment - 29/Jul/08 05:30 AM
make descriptions a little more explicit.

Lear Cale added a comment - 22/Sep/08 10:41 AM - edited
Provide a "bake" dialog box to allow the user to create a new skin or clothing item from the avatar's current appearance. The title could be "Merge".

Using a radio button widget, user would select a destination layer, such as skin, undershirt, shirt, jacket, underpants, pants, gloves, shoes, etc. Skirt layer would not be applicable since it currently does not have more than one contributing layer. Only one choice would be allowed.

Using checkboxes, the user then selects the source layers to include when merging. Only those layers applicable to the destination layer would be selectable.

All selected source items would need to have copy permission (and the dialog screen should make this clear). Until this requirement is met, the "Merge and Save" button would be inactive (gray).

The dialog would also have a space for the user to enter the new item's name, similar to when saving a new clothing item or skin modification.

On commiting the "Merge and Save", the client would bake the relavant worn textures into a single layer (with transparency preserved) and upload the resulting texture or textures, with upload charge for each texture uploaded. These would be saved by the client as an item of the destination layer.

The results would of course be clipped to the boundaries of the destination layer. For example, when selecting the jacket layer, possible source layers would include undershirt, shirt, gloves, jacket, and pants, but much of gloves and pants would be clipped off in the resulting jacket.

The resulting item would have copy permission, and would have transfer permission if and only if all source layers had transfer permission.


meade paravane added a comment - 22/Sep/08 11:00 AM

Ghosty Kips added a comment - 23/Sep/08 01:12 PM
The resulting item should not have both copy and transfer permissions unless the creator of the new merged item is also the creator of the layers being merged. This would prevent residents from combining products from other content creators and reselling them as new items.