Autocad2016 XRef Issue printing

[Anonymous]

When I have a drawing that contains a clipped XRef, although I don't see the portion that is clipped, if I zoom extents ot print extents it includes the portion that is clipped so I don't get the sheet but the offset to include the portion that has been clipped. I can't see the clipped portion but the view recognizes it

[Anonymous]

Unfortunately I don't have a solution for you.  I wanted to expand upon the problem, because I am having it as well.

It seems that the zoom extents will try to include the basepoint of the xreference even if it is clipped.

This was an issue in 2015 and before, but the print function "Print Extents" ignored the error, but zoom extents would sometimes malfunction.

In 2016 it makes printing almost unusable for my company because we have thousands of sheets that are set up to print extents with clipped xrefs.

[leothebuilder]

I would recommend placing the title border in layout (paperspace) with a scaled viewport.

In layout/paperspace you  plot 1:1 and you will not have the problem with the clipped xref.

Layout/paperspace in autocad has been around for about 25 years.

[Anonymous]

In 2015, everytime it had an issue while zooming I found turning the xclip
off and then back on usually fixed it. Doesn't work in 2016 though









Colin Pye IT

HVAC Designer




Avalon Mechanical Consultants Ltd.

300 - 1245 Esquimalt Rd.

Victoria, B.C. V9A 3P2

Ph. 250-384-4128 ex.107 email:
colin@avalonmechanical.com

Fax. 250-384-4134

[Anonymous]

---

@leothebuilder wrote:

I would recommend placing the title border in layout (paperspace) with a scaled viewport.

In layout/paperspace you  plot 1:1 and you will not have the problem with the clipped xref.

Layout/paperspace in autocad has been around for about 25 years.

---

Yes, that's a decent solution, but my company has chosen to separate our sheet files from our working documents on purpose. We have 15+ years of sheets with clipped xrefs on there all set up to batch plot to extents. It's unreasonable to change all those documents going forward. We have upgraded through every release of autocad and have not had an issue until 2016.

Even when zoom extents was an issue, plot extents never had a problem.

[bcf]

I have had the same problem with clipped xref's and zoom extents (plot extents) even using model/paper space. I have clipped xref's in paperspace. My solution was to create a pagesetup with plot area set to window using coordinates for the outside of our title blocks. Always plots correctly even with a bad extents.

[Anonymous]

I am having this issue as well after going to 2016.

Yes. When I plot, I am using my paper space "layout" (I.e the "Plottable area") and it seems to plot correctly. But, If someone else in the office chooses to use their own page set-up override , or make their own set-up, and plot "to extents", it gets all screwy. I agree that we "should" be using proper layouts, but most of the time, PM's are just trying to get something on paper and they just cheat it because "extents and center the plot" just always work.

Now, even though I can plot right now that I have set it to layouts, I would still like to know if there is a way to set the "limits" of paper space? So that when I zoom "extents" in paper space, it ignores the clipped xref and zooms just to the "layout"?

I did not have this problem in 2015.

[bcf]

The only other thing I have tried with limited success is to

• open the xref'd file and set its indexctl to "2" or "3"
• Open drawing file and reload the xref and xclip it to within the tblock boundary

Setting the indexes to on seems to allow Autocad to calculate the extents properly and ignores the unclipped size of the xref.

The problem is any time the xref is edited/saved it seems to nullify this solution until I go into the drawing file, delete the existing xclip boundary and "re-xclip" the xref.

The xref we were using was a "live" file rather than a background so it was updated constantly and I soon ran out of patience "re-xclipping". If you have an xref that is not changing this might work for you.

Good Luck!