I need some advice/ opinions on working with blocks. Organizing.

[cvriv.charles]

Well,... I finished all the parts for my model and I am ready to assemble. The model only has two parts. Three actually. One part is used twice. Anyways,... both parts are in seperate files. When I inserted one file into the other, I noticed that all the layers from the one file got added to the other. The first thing that came to mind when I saw that was, "clutter".

 

So my question is,... how do you pro's organize your models? What are some good habits and bad habits?

 

I first deleted all the unecessary layers in each file. But I still thought that there would still be a lot of layers in the assembly file. So then I though that I would only have one layer left in each file with the name of the part. This way when I add that file to the other file, only that one layer will be added. I could assign colors to the solids individually instead of by layer. But i wasn't sure if this was good practice? Because if the model has several little parts here and there I would have to click em all to change to colors etc.

 

If I was to do that,... I think I would want to create a copy of the model before I do that so just incase I had to make changes I wouldnt have to add the layers again before I edited. But then I would have like 2 files for each model laying around.

 

Any advice/ opinions?

 

Thanks.

[L_Ruts]

You could always put your part on layer "0", and then insert it on whatever layer you like and it will take the properties of that layer (unless you explode it). Or you could xref the parts, then the layers are easier to control in the layer manager, being able to select all layers in a specific xref. I prefer to xref every thing into my drawings rather than inserting blocks.

[Patrick Hughes]

My method for "parts" that will be brought into a model is to create them with objects always on layer 0.

 

When I insert into the assembly I use a named layer for the part.

 

If the inserted part is used multiple time (such as a fastener) it is inserted into the individual part layers that will "own" it. This way the inserted part has an association with the object it interacts with.

 

I like to keep things as simple as possible.

[cvriv.charles]

Thanks guys. I will take all that into consideration.

 

Is it true that inserting other files will save on file size as oppose to recreating the part several times in one drawing?

[cvriv.charles]

XR's work great! I like the idea of XR's instead of blocks. Thanks guys.

[Patrick Hughes]

Bear in mind that if you share drawings with others outside of your organization the will need access to the X-Refs.

 

And yes it is true that blocks (and x-refs) will save on file size.

[cvriv.charles]

Bear in mind that if you share drawings with others outside of your organization the will need access to the X-Refs.

 

And yes it is true that blocks (and x-refs) will save on file size.

 

Understood. I understand how XR's save on file size. I dont understand how blocks do though.

[Patrick Hughes]

Understood. I understand how XR's save on file size. I dont understand how blocks do though.

 

Well I should have qualified my statement. Blocks can save file size when you have a multitude of copies of a given block in a drawing. So if you have geometry that is repeated it can be beneficial to create a block of the geometry and make multiple insertions of that block.

 

There are tricks and some "Gotchas" that go along with blocks, such as layers and insertion points, etc.

 

If you are not familiar with them it is best to experiment with them for a while to observe how the different methods and techniques behave.

 

You can think of a block as a mini drawing that is contained in the working drawing.

 

Another benefit of using blocks is when you have text included in the blocks known as attributes. But that is another subject altogether.

[cvriv.charles]

Well I should have qualified my statement. Blocks can save file size when you have a multitude of copies of a given block in a drawing. So if you have geometry that is repeated it can be beneficial to create a block of the geometry and make multiple insertions of that block.

 

There are tricks and some "Gotchas" that go along with blocks, such as layers and insertion points, etc.

 

If you are not familiar with them it is best to experiment with them for a while to observe how the different methods and techniques behave.

 

You can think of a block as a mini drawing that is contained in the working drawing.

 

Another benefit of using blocks is when you have text included in the blocks known as attributes. But that is another subject altogether.

 

Ok well I understand in a way. I know it saves on file size if you use a block geometry multiple times as opposed to using the geometry several times. Thanks.

[Jack_O'neill]

 

There are tricks and some "Gotchas" that go along with blocks, such as layers and insertion points, etc.

 

If you are not familiar with them it is best to experiment with them for a while to observe how the different methods and techniques behave.

 

 

Be sure you keep track of block names too. If you have a block in your drawing that's named "abc" (lets say its a half inch socket head cap screw) and somewhere down the road you try to insert a different block with the same name, only this time its a quarter inch screw, you'll get the one that was there first. That gets really confusing if you have nested blocks (a block inside another block) for a common assembly that you reuse in several drawings. Just make sure they all have unique names and you'll avoid any conflicts.

[cvriv.charles]

Be sure you keep track of block names too. If you have a block in your drawing that's named "abc" (lets say its a half inch socket head cap screw) and somewhere down the road you try to insert a different block with the same name' date=' only this time its a quarter inch screw, you'll get the one that was there first. That gets really confusing if you have nested blocks (a block inside another block) for a common assembly that you reuse in several drawings. Just make sure they all have unique names and you'll avoid any conflicts.[/quote']

 

Well which do you guys think is better to use? Blocks or XR's? Or os it one of those thing where it's merely down to preference?

[L_Ruts]

I prefer XREF's. If you're worried about sending drawings to outside companies or the client, the ETRANSMIT command will take care of everything for you. It creates a folder that includes all XREFS, Plot Styles, Text Styles etc. It will even create a .zip file if you choose. Autocad looks for XREF's in the root folder if the folder structure is not the same, like when you send it outside the company.

[Cad64]

Well which do you guys think is better to use? Blocks or XR's? Or os it one of those thing where it's merely down to preference?

 

You should use both.

Blocks and Xrefs serve different purposes and both are very useful.

 

An xref is generally something unique that is inserted once in your drawing, like a site plan or a floor plan. An Xref can also be inserted into multiple drawings, and if modified, will automatically update all drawings that contain it.

 

A block is generally something common that is inserted, over and over again.

[Jack_O'neill]

Well which do you guys think is better to use? Blocks or XR's? Or os it one of those thing where it's merely down to preference?

 

As time goes by, you'll find reasons to do it both ways. Inserting a drawing as a block isolates it from any changes you make in the future to the inserted drawing. In other words, if you insert "b" into "a" as a block, you can go back later and change the original "b" and nothing will happen to the block you inserted in "a".

 

If you xref "b" in "a" and then later go change "b" in someway, the next time you open "a" you'll get a notification that "b" has been changed and needs to be reloaded.

 

This can work to your advantage if you want more or less automatic updates, but can be a pain in the backside if you don't.

 

Xref is also a great way to bring information in that you need to see, but may not want to leave in a drawing. If you want to design a custom awning over a window for example, you can xref the elevation you want, draw your awning, then detach the xref and its gone.

 

Just look down the road and decide which would be better for what you're doing at the time.

[cvriv.charles]

Thanks guys:) Lots of info right here:) Well I like the idea that if I change the something in the individual xref file that it will change in the drawing the xref is attached.

 

Blocks get added to the drawing so the overall drawing is just one file. Thats nice too.

 

I'll have to play around with them both and see what is needed for whatever im doing at the moment.

 

Thanks guys:)