Feedback needed on UI designs - USD Selection modes #4112
Replies: 1 comment
-
I like the indentations, I did wonder if this will also display any site kinds added on top of the default USD kinds as well? A studio might have multiple kinds that inherit from component for example. Having an indicator that the Prim is instanced, and not just tagged as instanceable, is nice as well. I think if you set the kind to "group" it should select all derived kinds, that is kind of the point of the inheritance. As above, maybe I have custom component kinds and I want to select all of them, I should be able to use "component" for that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey everyone,
We’re taking a moment to revisit the USD selection mode design to address certain issues and confusions, namely:
ex: Assemblies are also considered Groups
Our Proposal
Watch here!
USD_selection_modes_design.mp4
Questions we have for you
Would you change anything with these designs?
If you set the selection mode to “Component” and you click on unstructured data that doesn’t have “Component” as a kind it will fallback to selecting the leaf prim, which is inconsistent with Maya selection modes. Do artists like this behavior? Would they want fallback selection to be an option?
There’s currently no way to select by a specific kind (bypassing kind inheritance), is this something artists would ever want?
ex: set selection to “Group” and only selecting objects with kind group and not assembly
What do you think about the indentations?
Finally, we’re thinking that the UI should communicate to artists whether something is an instance or not, to help with understanding how editing them differs from non-instance prims. Do you think this would be helpful?
Thanks!
Scott Renaud
scott.renaud@autodesk.com
Beta Was this translation helpful? Give feedback.
All reactions