Jump to content

why is one object not one object


RAYMOND
 Share

Recommended Posts

It has do with the way the parametric objects are derived in ADT. Each 'component' frame, sash glass in a window object is a seperate unit/block so to speak with different display capabilties, visibility, line wieght, color......................all of these effect the 3D export/import geometry.

 

It's the complexity of making 2d/3d/Bim simple LOL

 

WDA

Link to comment
Share on other sites

I can do this if I make the dwg a block then I can use mso on the "one object" in viz... but this seems to be a hard workaround for that..

 

it is very nice when a site has multiple buildings etc to have each building one object.

 

just do not like the long list in the object list.. it seems very useless for the most part.

 

my take on it anyway:D :D :D

Link to comment
Share on other sites

haven't tried that for ADT models, but however, if you are constantly updating the model in ADT and reloading it in viz, then do you have to re group everytime... i don't see why they don't give us the "one object" even if it is ADT components.

 

i have used group with Onyx tree's to shorten the list but of course I don't keep editing the tree and reload it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...