Demand load Layers from Xrefs

[clarkrj]

I XREF several active drawings (with many layers in each) into a model to be able to have several designers work on a given project.

The problem I have is layer control. I often have several files loaded into a single model which is then loaded into an overall site file. This resulte in a few hundred layers in the final drawing. I rarely need geometry from more than two or three layers from each of the original files.

Is there an option upon XREF that would allow me to demand load only those few layers I need?

[Mike.Perry]

<SNIP>

Is there an option upon XREF that would allow me to demand load only those few layers I need?

Hi

Not that I am aware of in AutoCAD.

Have you looked into the use of Layer Filters ?

Plus have you looked into things like...

IndexCtl
TreeDepth
TreeMax
XLoadCtl
XClip

When set-up correctly, the above can greatly help when working with Xrefs.

Have a good one, Mike

[rkmcswain]

Is there an option upon XREF that would allow me to demand load only those few layers I need?

Have you read about "Demand Loading" in HELP?
Are you saving your files that are being X-ref'ed in with layer indexes?

[Comach]

Hi

Not that I am aware of in AutoCAD.

I concur.

Are you saving your files that are being X-ref'ed in with layer indexes?

Layer index is a useful capability for improving performance issues with xrefs.

If I may suggest - you might wish to consider re-organizing your drawings and your xref hierarchy by utilizing the overlay structuring. This will give you manageability at the main model level and provide options at the overall site file level. May require a complete thinking out of the box approach but is worthwhile for processing only essential data and minimizing layers.

[greg.mcdowell]

two variables control demand loading... indexctl and xloadctl

i can't remember which option does what but, in verbal form, i set indexctl to save both layer and spatial indices and set xloadctl to enable with copy (i think they're option 3 and 2 respectively)

your file size will increase (slightly) but if you've got a lot of geometry not showing or a lot of layers frozen (if they're off they still load) you should see the drawing load substantially faster

oh yeah... indexctl needs to be set in the base file and xloadctl is a system variable.

[Mike.Perry]

Plus have you looked into things like...

IndexCtl
TreeDepth
TreeMax
XLoadCtl
XClip

When set-up correctly, the above can greatly help when working with Xrefs.

Hi "cjohnson.100237" ( Sorry, I do not know your real name )

It would appear the consensus somewhat agrees with the rubbish I wrote above...

rkmcswain ( above post ).

hughrjt ( above post ).

greg.mcdowell ( above post ).

Have a good one, Mike

[clarkrj]

Thank you all for your help. These were the answers I expected, but didn't want.
My solution is to create a vessel model (geometry only) XREF it into the layout model and the vessel detail drawing. I have the ability to modify the vssel geometry through REFEDIT from either place and both are notified of the revision. My boss doesn't like this idea, but I don't have a cleaner solution.

Thanks again

Clark

[sifuentes]

The problem I have is layer control.

What kind of layer control problem do you have? If it is visibility, and since you only need 2 or 3 layers from each reference drawing, it seems to me that you could use a script to control layer visibility. You could write a script that freezes everything, and then thaws the layers you need.

For what I understand, demand load helps with performance of drawings using xrefs, so it doesn't read all the information from the source files.

[clarkrj]

300-400 layers from XREFs that have nothing to do with the physical model because I will often insert 8-10 vessels into a package drawing and each of those have 20-30 layers each. This is just a pain, but I would love a simple work arround

[rkmcswain]

300-400 layers from XREFs that have nothing to do with the physical model because I will often insert 8-10 vessels into a package drawing and each of those have 20-30 layers each. This is just a pain, but I would love a simple work arround

Is the problem the fact that it loads all the geometry in -or- the fact that 1000's of layers are hard to work with in the Layer Manager?

BTW: Small world, I live around the corner from your work location. (West/6)