Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-216140] Ability to Create "Wearables" by Script/Text Interface #3595

Open
sl-service-account opened this issue Apr 20, 2018 · 1 comment

Comments

@sl-service-account
Copy link

How would you like the feature to work?

With the way avatar customization has evolved, skins and clothing layers are almost entirely used simply as texture-delivery systems, with the various slider settings seldom if ever used. However, when creating a new wearable the process still requires going through an interface that has many unnecessary steps (such as needing to wear it to add the textures) and doesn't have a way to quickly enter texture UUID's. It would be very useful to be able to have an interface that would allow a wearable to be created and have the ability to set the textures and possibly tint at the moment of creation instead of needing to wear it. The slider settings could stay at a default - if there's ever a need to edit them it can be done while worn the way it's traditionally done.

Why is this feature important to you? How would it benefit the community?

With the introduction of bakes-on-mesh the wearable system that many people no longer use will get new life, but content creators are now used to the workflow of creating scripted appliers, which is a faster and more direct process. A stripped-down, faster interface will make it easier for content creators to create the necessary wearable items. Ideally, there could even be a scriptable/bulk creation process for them.

Original Jira Fields
Field Value
Issue BUG-216140
Summary Ability to Create "Wearables" by Script/Text Interface
Type New Feature Request
Priority Unset
Status Accepted
Resolution Accepted
Labels bakesonmesh
Reporter Theresa Tennyson (theresa.tennyson)
Created at 2018-04-20T10:30:57Z
Updated at 2018-05-16T18:25:29Z
{
  'Business Unit': ['Platform'],
  'How would you like the feature to work?': "With the way avatar customization has evolved, skins and clothing layers are almost entirely used simply as texture-delivery systems, with the various slider settings seldom if ever used. However, when creating a new wearable the process still requires going through an interface that has many unnecessary steps (such as needing to wear it to add the textures) and doesn't have a way to quickly enter texture UUID's. It would be very useful to be able to have an interface that would allow a wearable to be created and have the ability to set the textures and possibly tint at the moment of creation instead of needing to wear it. The slider settings could stay at a default - if there's ever a need to edit them it can be done while worn the way it's traditionally done.",
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'Target Viewer Version': 'viewer-development',
  'Why is this feature important to you? How would it benefit the community?': 'With the introduction of bakes-on-mesh the wearable system that many people no longer use will get new life, but content creators are now used to the workflow of creating scripted appliers, which is a faster and more direct process. A stripped-down, faster interface will make it easier for content creators to create the necessary wearable items. Ideally, there could even be a scriptable/bulk creation process for them.',
}
@sl-service-account
Copy link
Author

Theresa Tennyson commented at 2018-04-22T11:48:45Z

After looking at the default states of new clothing assets, I'd want the items made this way to default to maximum body coverage/minimum thickness values. Some items now default to settings less than full possible coverage.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant