Dont overthink realistic. Chances are, the client is not paying for realism. Image is better than good for the common man.
1 Like
Visuals are the only thing that I supply so it is the most important thing for meš
Why is that? Can someone back this up and explain why?
If I recall correctly, @gkernan said he thought it was overhead from creating the thumbnail image of every component and perhaps from registering the components in the Outliner. Groups donāt have thumbnails and arenāt presented in the Outliner.
Sure they are.
Oops I meant the Components window 
1 Like
Well, the Outliner sure. The component library palette has the thumbnails.
Iām finding that once you get a lot of components in a model, the In Model collection becomes very hard to use, i.e. find anything.
Are you giving the components useful names?
I do name everything, but you quickly have to think hard about naming conventions. For example, think about:
- 30" Sinkbase Cabinet
vs. - Cabinet, Sinkbase, 30"
which impacts sort order for when you hunt down a list.
2 Likes
Developing consistency in naming right from the start is a good idea.
2 Likes
I also donāt quite get the rules behind the palette not showing all of the components that are in model (is it context level sensitive or something?) until you check āexpand,ā and then thereās just too much information. Itās not just my components, but all the third party components and their subcomponents which are especially explosive in number with dynamic components. I have to wade through all these bits to find my stuff.
Because of this, Iām trying to move toward saving my project components in a local collection for the project and keep that collection open instead of the In Model collection.
Yeah. With nested components like youāre using, it take expanding to get them all to show.
I donāt know what components youāre using but it might be that they could stand some simplification.
Depending on the situation, maybe it would be easier to access the components from a local collection instead of the In Model.
Hi, hope you had a good Christmas. Just a quick question for you, when I have a selection of cabinets and a selection of doors to use for a kitchen, with a workflow, would you add the door to a cabinet and bring that whole item into the kitchen room or would you put the cabinets into the room and then add the door, also with any handles and seen hinges, like butt hinges?
It was good. I hope yours was, too.
As to the exact work flow, it depends on what I would need to do to the model later. If I am just showing a single door and pull style, I would be tend to make nested components that contain a simple case component, the door(s), and pull(s) and insert them. Or create the first one and make copies to modify for the other ones in the kitchen.
If I anticipate needed to be able to show different door and pull styles, I would probably not create nested components. This would make it easier to either swap those components with Replace Selected or assign different layer tags to different door styles so I can choose which ones to show in each scene. No point in having to duplicate the cabinet boxes in the process.
With all that, though, you might find it just as easy to create nested components with maybe Shaker style doors and others with raised panel doors, and so on. Then just insert the appropriate ones.
1 Like