sl-service-account
commented
3 years ago Vir Linden commented at 2021-08-18T13:51:26Z
Thanks! Bringing this in for possible future avatar work. Note that we have a lot of proposals in this bucket - putting something there is basically a reminder to think about it at the appropriate time, not a guarantee that we are going to go that way.
How would you like the feature to work?
In BUG-231017 – Shape Override / New Asset Type / Avatar Enhancement, I described a potential mechanism for implementing partial shape overrides.
https://jira.secondlife.com/browse/BUG-231017
In the description I described the use of a Null Radio Button to have the slider values be ignored as the default condition, and only if a value is specified would it then override. Presented in a UI mechanism that is consistent with what users are used to using.
Afterwards this occurred to me…
Using this Null Button Mechanism could allow the Hair Base - Eyebrow values to be now implemented in the System Shape, and potentially carry the Eyebrow Values into a Shape Override Asset as well.
So that the System Shape, if it’s eyebrow values were engaged, it would override the System Hair values.
This would make it so that all sliders that relate to a bento head is in the same ‘thing’ so as to simplify matters.
Avatars would still wear a system hair, even if only as a ‘conceptual’ placeholder, as one of the four body type parts.
However, using the null button type function in the system shape would allow backward compatibility with older no-mod shapes, and if the user chooses, an ability to use older system System Hair with their older own shape.
Why is this feature important to you? How would it benefit the community?
Since prim hair became a thing, and now mesh heads, System Hair base is only really used for eyebrow shape. (And I assume is probably lost in the shuffle as an option to customize ones face. I forgot all about it! Finally remembered. Fixed the Unibrow.)
But… When creating a shape and focusing on the face, current workflow is split between adjusting system shape, saving…. adjusting system hair, saving… back and forth… and so on.
This would put it all in one place for the end user. Both for working the sliders, but more useful to just remember the right eyebrows with their face.
If implemented with an additional Shape Override on top of the shape, then is one asset to configure to make the face independent of the shape.
Links
Related
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-231096 | | Summary | Eyebrow Slider Values / Mechanism to Consolidate with System Shape / Avatar Enhancement | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | KathrynLisbeth (kathrynlisbeth) | | Created at | 2021-08-11T19:53:20Z | | Updated at | 2021-08-18T13:51:32Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2021-08-18T08:51:26.285-0500', 'How would you like the feature to work?': 'In BUG-231017 – Shape Override / New Asset Type / Avatar Enhancement, I described a potential mechanism for implementing partial shape overrides.\r\n\r\nhttps://jira.secondlife.com/browse/BUG-231017\r\n\r\nIn the description I described the use of a Null Radio Button to have the slider values be ignored as the default condition, and only if a value is specified would it then override. Presented in a UI mechanism that is consistent with what users are used to using. \r\n\r\nAfterwards this occurred to me…\r\n\r\nUsing this Null Button Mechanism could allow the Hair Base - Eyebrow values to be now implemented in the System Shape, and potentially carry the Eyebrow Values into a Shape Override Asset as well. \r\n\r\nSo that the System Shape, if it’s eyebrow values were engaged, it would override the System Hair values.\r\n\r\nThis would make it so that all sliders that relate to a bento head is in the same ‘thing’ so as to simplify matters.\r\n\r\nAvatars would still wear a system hair, even if only as a ‘conceptual’ placeholder, as one of the four body type parts. \r\n\r\nHowever, using the null button type function in the system shape would allow backward compatibility with older no-mod shapes, and if the user chooses, an ability to use older system System Hair with their older own shape. ', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': 'Since prim hair became a thing, and now mesh heads, System Hair base is only really used for eyebrow shape. (And I assume is probably lost in the shuffle as an option to customize ones face. I forgot all about it! Finally remembered. Fixed the Unibrow.)\r\n\r\nBut… When creating a shape and focusing on the face, current workflow is split between adjusting system shape, saving…. adjusting system hair, saving… back and forth… and so on. \r\n\r\nThis would put it all in one place for the end user. Both for working the sliders, but more useful to just remember the right eyebrows with their face.\r\n\r\nIf implemented with an additional Shape Override on top of the shape, then is one asset to configure to make the face independent of the shape. ', } ```