AutoCAD Land Desktop

AutoCAD Land Desktop

Reply
Contributor
11 Posts
0 Kudos
Registered: ‎09-25-2003
Post 1 of 5

Phantom XREF problems (not visretain)

952 Views, 4 Replies
10-11-2005 02:10 PM
I have several drawings within a very large project that have become corrupted. It seems as if some sort of XREF error is being passed around like a virus within the project.

I'm using LDD3 and Civil Design 3.

When I overlay XREF multiple drawings into a drawing, additional XREF layers are appearing in layer manager for other drawings that are not attached to the overlain XREFs. The XREF layers that show up in layer manager belong to XREFs that do not exist within XREF manager. I've tried auditing, purging, and CDGpurging all of the main XREF drawings, but I'm still having these issues, even if I start a new drawing from scratch and overlay the XREFs, the phantom XREF layers appear. Drawings are crashing daily, and recovering isn't working on some of them because it fails when it's loading xrefs. If I can get the drawings open, dettaching all the XREFs helps, but it comes back as soon as a few of them are overlaid again. I'm really at a loss of what else i can do here.

Has anyone had anything similar like this happen?
*Don Reichle
Post 2 of 5

Re: Phantom XREF problems (not visretain)

10-11-2005 03:10 PM in reply to: cowles
Hey J Cowles;

Have you attempted an Audit and Purge on all of the XREF DWGs that are
associated with your common errors? It may even be necessary to WBLOCK
certain of these DWGs, if the Audit & Purge aren't complete for "fixing"
them.

When employing this version of WBLOCK, it would be best to run through a
Layer State to save it's current Layers the way they are now, and then
Export them, before you Thaw and On all of them prior to the Wblock next.
When you Wblock don't be tempted to Select the entities with an All, instead
use a Window to select all the uncorrupted entities in the DWG. Once you've
created the New DWG, you can then Import and Restore the previous Layer
State I had you create above, so that everything is back the way it should
have been before you started this endeavor.

HTH

--
Don Reichle
"King Of Work-Arounds"
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
--------------------------------------
LDT-2K4
AMD64 3200+
XPPro 32bit SP2
1GB RAM
Nvidia GeForce FX 5200 128MB
Western Digital Raptor 10K-rpm HD


wrote in message news:4981542@discussion.autodesk.com...
I have several drawings within a very large project that have become
corrupted. It seems as if some sort of XREF error is being passed around
like a virus within the project.

I'm using LDD3 and Civil Design 3.

When I overlay XREF multiple drawings into a drawing, additional XREF layers
are appearing in layer manager for other drawings that are not attached to
the overlain XREFs. The XREF layers that show up in layer manager belong to
XREFs that do not exist within XREF manager. I've tried auditing, purging,
and CDGpurging all of the main XREF drawings, but I'm still having these
issues, even if I start a new drawing from scratch and overlay the XREFs,
the phantom XREF layers appear. Drawings are crashing daily, and recovering
isn't working on some of them because it fails when it's loading xrefs. If I
can get the drawings open, dettaching all the XREFs helps, but it comes back
as soon as a few of them are overlaid again. I'm really at a loss of what
else i can do here.

Has anyone had anything similar like this happen?
Contributor
11 Posts
0 Kudos
Registered: ‎09-25-2003
Post 3 of 5

Re: Phantom XREF problems (not visretain)

10-11-2005 03:26 PM in reply to: cowles
Thanks Don,

I had just run through that on one of the main XREF's and it seems to have cleared the problem up. There was a locked _kti layer that had made it's way into the drawing from an architect's block that seems to have been creating the problem.

I had to do a solution set on that layer, erase it, purge it, then block the entire drawing out to a new one. CDGpurging and auditing alone were not removing the _kti registered application that was causing the errors in the XREF.
*Don Reichle
Post 4 of 5

Re: Phantom XREF problems (not visretain)

10-11-2005 03:57 PM in reply to: cowles
I hear you, and I wish CDG were still around to augment their fine toolset.
I used to use it a lot more often than I do now.

--
Don Reichle
"King Of Work-Arounds"
"The only thing worse
than training your staff,
and having them leave is -
not training your staff,
and having them stay."
Courtesy Graphics Solution Providers
--------------------------------------
LDT-2K4
AMD64 3200+
XPPro 32bit SP2
1GB RAM
Nvidia GeForce FX 5200 128MB
Western Digital Raptor 10K-rpm HD


wrote in message news:4981615@discussion.autodesk.com...
Thanks Don,

I had just run through that on one of the main XREF's and it seems to have
cleared the problem up. There was a locked _kti layer that had made it's way
into the drawing from an architect's block that seems to have been creating
the problem.

I had to do a solution set on that layer, erase it, purge it, then block the
entire drawing out to a new one. CDGpurging and auditing alone were not
removing the _kti registered application that was causing the errors in the
XREF.
New Member
1 Posts
0 Kudos
Registered: ‎01-10-2013
Post 5 of 5

Re: Phantom XREF problems (not visretain)

01-10-2013 05:57 AM in reply to: *Don Reichle
If you cut a section through anyone else's work it will bring those layers into the drawings also. Example: If I am working in my base electrical file but I am using mechanical plumbing and architectural as a background so I can route my work properly. If I were to cut a section through their overlaid xrefs so I can see where my work lines up with theirs, the layers associated with the xrefs being cut through will show up in the current drawing regardless of it being from an overlaid xref or not. I am personally not a big fan of this myself. You would think Autodesk would have come up with a better way of handling this since the layer management won't effect the section anyways. This makes pulling in these layers pointless.
Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Announcements
Are you interested in helping shape the future of the Autodesk Community? To participate in this brief usability study, please click here. Your time and input is greatly appreciated!