Batch Plot extremely slow with Xref

[ManueleDesign]

Hi everyone,

I've got a problem that could compromise months of work.

We have designed 50 apartments for a tower, they are all in a unique file named "abacus" to easily control every single detail especially when client requests to change something. All of them have been made with dynamic blocs, many dynamic blocs repeated in every single apartment.

We have to deliver our work in 5 steps, let's say 10 apartments for each group.

In 5 new dwg files we have imported a cut XREF showing the 10 apartments we need to show for that group. Every apartment has about 4 dedicated layout which is about 40 layouts for every single dwg file.

It takes a while to switch between the layouts and it take ages to batch plot the 40 layouts. I have estimated that it takes nearly 2 minutes for each layout instead of 10 seconds for the same layout with binded XREF.

(Sure, I can go through this problem binding XREF and exploding the block every time I have to print but it’s not a fast option anyway and sometimes some of the dynamic block reset)

It seems that AutoCAD reloads the whole XREF every time I click on a layout, that’s why it’s incredibly slow.

Any suggestion? I have tried to change so many system variables setting but none of them has solved the problem.

Looking forward to getting the right tips and tricks, thanks in advance. Ciao!

[pendean]

Did you turn off background publishing yet? in OPTIONS, it's about all you can do.

After that, explore here (very long lists of items to change)
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Slow-p...
and
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Improv...

HTH

[dany_rochefort]

@ManueleDesign  Check to see if your WHIPTHREAD variable is set to 1.

''Controls whether to use an additional processor to improve the speed of certain operations such as those that regenerate the drawing''

[ManueleDesign]

yes indeed, background publishing is always turned off.

[ManueleDesign]

It is set to 1.

I'm quite sure it's something about some variable, I just need to tell AutoCAD "don't reload that XREF any time you do something".

[Valentin-WSP]

@ManueleDesign ,

Follow the suggestions on this article:

• Plotting takes a long time to complete in AutoCAD

[ManueleDesign]

Thank you so much for this link, it's something I have already checked.

I don't have this "long time problem" in general but just when I try to plot files with xref attached.
The problem is something related to xref for sure.

[Valentin-WSP]

@ManueleDesign ,

Check these links:

• Slow performance when using xrefs in AutoCAD
• Slow performance using clipped reference files (Xref) in AutoCAD

[ManueleDesign]

I've already tried both of them without any significant success. ☹️

[Valentin-WSP]

@ManueleDesign ,

Maybe this one: (Particularly - Enable demand loading of xrefs)

• External reference (xref) file is missing or unresolved in AutoCAD

[ManueleDesign]

tried also this link, no results.

[dany_rochefort]

@ManueleDesign Perhaps XLOADCTL

''When XLOADCTL is set to 2, a copy of each referenced drawing file is stored in the folder specified by the XLOADPATH system variable or the temporary files folder (set in the Options dialog box).

Additionally, xrefs load faster when you work across a network: the performance enhancement is most pronounced when you open drawings with many xrefs.''

Here is the list of all Xref related command & variables: 

https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2022/ENU/AutoC...

[ManueleDesign]

thanks so much for your message Dany,

unfortunately I have already set XLOADCTL to 2, I tried also different settings but nothing changes.

I just discovered that I have the same problem even if I bind the XREF it's not a XREF problem then.

The only way to speed up is to explode the binded XREF.

To print 1 single LAYOUT it takes:

XREF : 1:20 minutes

XREF converted into block reference - Bind Type - Bind : 1:20 minutes

XREF converted into block reference - Bind Type - Insert : 1:37 minutes

Exploded block reference : 6 seconds

It's a huge difference!!!

Now I'm definitely lost, it's not about XREF issue but I guess it's something different.

[dany_rochefort]

@ManueleDesign  You gotta do what you gotta do to get the work out there and get your company paid $$$ If that means exploding blocks, xref's or dimensions... Just send it !    

One of my previous employers did the same thing but it was with Dimensions. Right before the project was delivered, they ran a script that would explode all dimensions across thousands of dwg's +... They were so paranoid that someone would go back into these drawings and stretch or scale something mistakenly that they leveled the playing field with a massive dimension explode 😂 

Cheers    

[ManueleDesign]

I totally agree with what you wrote, we always have to find a way to complete our work which is the most important thing. 💪

It would be very interesting to understand how to use xref without this kind of problems though, I find extremely usefull to draw everything in one file and to lay out the elements in different files.

First reason I find this method intersting is because working on a single file makes it easy to control those similar repeated items, secondly because a dwg file without layouts is ways faster especially when the file size is quite large. 

I really hope someoene can give me some suggestion abou it. 🤞

[RobDraw]

---

@ManueleDesign wrote:
I'm quite sure it's something about some variable,

---

Have you considered that the content of the XREF could be the cause?

[ManueleDesign]

Yes indeed, the XREF seems ok though, I can't see any problem.

I also think it's not about the content because if I bind the XREF and explode the converted block reference everything works as usual.

I now think the main problem is related to blocks hierarchy.

The XREF is a matryoshka, it's made by dynamic blocks with other blocks inside.

I think this is what slow down AutoCAD (and probably drives the CPU crazy), it's enough to delete on level of the hierarchy (binding the XREF and exploding the converted block reference) to go back to standard performance.

It's enough but it's also a quite long process to do, it would be amazing to leave the XREF without loosing performance.