A few of my favorite features of Components that groups can't do: * Be saved and reused outside of that model, either by saving it to your files or by saving it to the 3DWH. * Have all instances be easily instantly swapped with another component. * Be a face-me * Have metadata added to it such as cost, manufacturer, or anything else, prepping a model for an exported purchasing report * Be dynamic!
In the real world we’re often dealing with groups of groups or components built from components - in other words, nested entities. So it would also be useful to understand the editing semantics of these nested entities, for instance whether “exploding” a group also explodes its constituent entities (and what happens to all that geometry if grouped again en masse), whether editing of a nested group or component by say, scaling, automatically scales the constituent entities, etc.
hello there, how did you walk or zoom in slowly form the ref to the hanging cabinet? there was no indication that the walk tool was on nor there is a scene already present
Mistah Ar. Aaron uses a optional 3D Connexion Space Mouse I believe; I just purchased one and you use it to zoom, pan, and so on, and still you also use your mouse to select tools to draw and edit. They cost a little over $100.
Good video but some details were lacking. Maybe it was intentional to drive home the primary difference between components and groups. But here's what I mean: As stated, you double-clicked into the component, that opens it up for editing. But there must have been another click done as well. I'm referring to a click *after* the double-click. That additional click was necessary to actually *selecting* the geometry inside the component. And in this particular case, it seems that if there was only one additional click necessary for selecting all the geometry in a bowl. I guess each bowl was a single surface? But in most real world examples, not all components are like this; there are multiple surfaces, edges, and faces a lot of times. So, in that case you'd have to select *all* that geometry and apply the material to *all of it* to fully cover the component and to get the material to propagate and fully cover the rest of the components.
What happens if I make a component with groups in it. Than I make interactive settings for this components (e.g. a list to open or close the door). When I have multiple of this same component in there and open the door on one, will it open the doors in all of them?
If you are making a Dynamic Components, all nested containers should be components (you should not use groups in Dynamic Components). Each instance of a DC has its own options, so modifying the state of a DC (open dor vs closed, for example) will affect a single instance.
Thanks for sharing. That was a good comparison. I would just like to add my two cents and say that complex components can cause big problems when editing. Furthermore, I have found that creating components too often can lead to an overcrowded component list.
A few of my favorite features of Components that groups can't do:
* Be saved and reused outside of that model, either by saving it to your files or by saving it to the 3DWH.
* Have all instances be easily instantly swapped with another component.
* Be a face-me
* Have metadata added to it such as cost, manufacturer, or anything else, prepping a model for an exported purchasing report
* Be dynamic!
That was awesome, thank-you! :)
In the real world we’re often dealing with groups of groups or components built from components - in other words, nested entities. So it would also be useful to understand the editing semantics of these nested entities, for instance whether “exploding” a group also explodes its constituent entities (and what happens to all that geometry if grouped again en masse), whether editing of a nested group or component by say, scaling, automatically scales the constituent entities, etc.
Great thought, Steve! We'll throw the idea on the list and you may see a Skill Builder about nested groups/components in the future!
This is when Outliner really shines to show the nesting hierarchy! It also shows why it's so important to name components.
Very well thought out and well presented video.
hello there, how did you walk or zoom in slowly form the ref to the hanging cabinet? there was no indication that the walk tool was on nor there is a scene already present
Mistah Ar. Aaron uses a optional 3D Connexion Space Mouse I believe; I just purchased one and you use it to zoom, pan, and so on, and still you also use your mouse to select tools to draw and edit. They cost a little over $100.
Good video but some details were lacking. Maybe it was intentional to drive home the primary difference between components and groups. But here's what I mean: As stated, you double-clicked into the component, that opens it up for editing. But there must have been another click done as well. I'm referring to a click *after* the double-click. That additional click was necessary to actually *selecting* the geometry inside the component. And in this particular case, it seems that if there was only one additional click necessary for selecting all the geometry in a bowl. I guess each bowl was a single surface? But in most real world examples, not all components are like this; there are multiple surfaces, edges, and faces a lot of times. So, in that case you'd have to select *all* that geometry and apply the material to *all of it* to fully cover the component and to get the material to propagate and fully cover the rest of the components.
can the section plane be cut through specific groups or components ?
Great explanation.
What happens if I make a component with groups in it. Than I make interactive settings for this components (e.g. a list to open or close the door).
When I have multiple of this same component in there and open the door on one, will it open the doors in all of them?
If you are making a Dynamic Components, all nested containers should be components (you should not use groups in Dynamic Components). Each instance of a DC has its own options, so modifying the state of a DC (open dor vs closed, for example) will affect a single instance.
Aaron Dietzen Thank you very much
Thanks for sharing. That was a good comparison.
I would just like to add my two cents and say that complex components can cause big problems when editing. Furthermore, I have found that creating components too often can lead to an overcrowded component list.
How to download from Wearhouse