Friday, 04 August 2017
  7 Replies
  2.5K Visits
0
Votes
Undo
  Subscribe
I've got a large project that's both being designed, and installed, in phases. My LA client is providing me AutoCad pieces as we progress, that is, the base plan plan xref, utilities, and their planting plan for each discrete area. Naturally, though, because of the nature of the project, my irrigation systems overlap these areas, so I have to pretty much put all the xrefs into the drawing to form the entire site. So I've done this, and have been drawing my irrigation plan over these multiple xrefs.

At plotting time, I ref MY drawing (and all the other xrefs) into separate sheet files, each of which may have several layout tabs (this may be clumsy, but hey, works for me). Unless I'm mistaken, the xrefs in my irrigation drawing need to be ATTACHED to my drawing file, so that they show up in my sheet files (I had them as overlays early on, but they didn't show up, so I attached them, and they showed up).

Anyhow, my big drawing file is getting clunky. Is there a better way I should be handling these xrefs (there's more than a dozen) so my process is smoother?

Thanks!
Define "clunky". That appears to be the issue, correct?
I don't see anything wrong with your process.
Unless, that is, you are attaching these files without any sort of drawing cleanup such as Nuke.

--J
My main drawing is 3450kb, and I notice a bit of lag during piping, for example. The other thing that happens is in my sheet file drawings, if I go to draw a polyline, the crosshairs jump around like some weird snap command is set (there is not). If I unload the xref, that goes away. Not sure what that's about.

I have a nice Dell i7 box with 16gig of memory, with 16 more on order. That might make the lag go away.

And yes, I Nuke everything.
So there is definitely something going on with one of the xrefs.
What I have found the best, is to sort the xref layers by Linetype, and then freeze them by each linetype. Basically try to track down the offending layer.
When I have looked at this, it is almost without fail a custom linetype, or a hatch pattern (or even an exploded hatch pattern).
Alternately, you could try freezing all xref layers, and thaw just those that are absolutely necessary.
When you do track down what the issue is, if it is something we can build into Nuke we would be happy to.

--J
What's interesting is that in the drawing file, there's no jumpy crosshair issue. In the sheet file, there is, but the xrefs should be the same. I'll investigate.
This might be another clue: the crosshairs are only jumpy within the limits of the actual drawing. They are not when I move it around in open space, away from the drawing.
What are you even doing in the sheet file that would make this come up? But also, this is very clearly not a Land F/X issue. You might be better served on an Autocad forum.

--J
I agree with Jeremiah. Sheet sets are for printing only. If you're putting text or match line information into the sheet drawing, you may want to consider using a separate model drawing instead. We have a separate match line drawing that includes all of the common information (street names and the like) and match lines as well as the match line text that are fields tied to the project's Sheet Set so that we don't have to edit it every time we or another consultant adds or subtracts a sheet. This drawing also includes a layer that includes the viewports in the paper sheets so that our labels all stay within their planned sheet viewports. Once we set up our paper sheets, we hardly ever revisit them. Usually it's to reconcile the layers that the other disciplines (or we) have added to their (our) drawings since the last time that the sheets were plotted. - Hopefully this helps.
  • Page :
  • 1
There are no replies made for this post yet.