Templates with Relative Path XREF failure and solution

[Anonymous]

I have multiple building specific templates (.dwt) which pull in an xref title block, as well as the multiple floors of the building along with address data and a few other nice to haves.

Recently moved to a new machine, and went to ACAD 2020 while I was at it(I usually wait until SP2). Most of my templates broke. If it had been all of them I might have addressed it sooner. Regardless, I have spent hours here on the forums, as well as between my two machines (ACAD 2019 on the old) trying to find a setting that is different. I found a number of references in the forums to relative paths not working with templates. Surprised me, as it worked great before. 

So, I found a solution, but I don't entirely understand why it works. In searching all XREF related system variables I finally came to XLOADCTL. Stock value is supposed to be 2, but was set to 0 on the new machine with 2020, and was 2 on the old machine. Correcting that fixed my issues. Here is what AutoDesk says about it:

Type:	Integer
Saved in:	Registry
Initial value:	2

ValueDescription

0	Turns off demand-loading; the entire drawing is loaded.
1	Turns on demand-loading. Referenced drawings are kept open and locked.
2	Turns on demand-loading. Copies of referenced drawings are opened and locked; referenced drawings are not locked

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.

So, problem is solved, but I'm curious. Why would saving a copy of the XREF to the temp folder solve this problem? Why can't it load from the network? (I imagine to reduce lag?) Is ACAD modifying the path to the temp folder but not showing it in the dialog box? I am completely dependent on XREF for everything, with all my work on a network, so I'm very keen on understanding what ACAD is doing behind the scenes. Anyone have anything to add?

Thanks 

[natasha.l]

Hello @Anonymous, 

Thank you for posting. 

This is more of a IT or CAD manager specific question because it involves your work environment & network situation.

To better understand pathing, it specifies a unique location in a file system for a given name for a file or directory. So when a xref file path is uploaded AutoCAD will search & point to a file system location, so when over a network the longer the file location/address the longer it will take AutoCAD to locate the file & upload it. 

So it is recommended that you work with a IT professional to specify a direct network path. For example, use something like \\server\share\folder. Network securities can also cause delays & access issues if not set up properly.

I hope this helped answer your question. 

Please "Accept Solution" if a reply or replies have helped resolve the issue or answered your question, to help others in the community.

[Anonymous]

Thanks for the reply Natasha.

I am essentially a CAD manager, I maintain living documents for a whole division. I'm also the draftsman, due to staffing issues.

To make sure I understand. Are you saying that CAD will store a local copy to compensate for a long file path? Or is it saving the copy either way, and with XLOADCTRL set to 0, it doesn't save one, and has to dig through the entire path?

My current setup, for say a background(walls and doors) file, is:

W:\XXXXXX\XXXXXX\XXXXXX\XXXXXX\XXXXXXXX\XXXXXXXXX\Base DWGs\DWG Data Base\BACKGROUND

Where W:\ is the network drive. Sorry I had to X out most of it for IP concerns, but the number of levels is clear. The file that my BACKGROUND is XREF'd into would be at the Base DWGs level(usually)

If I interpret your direction correctly, I would want to simplify that path to as close to the root as possible, so I may just be something I have to live with, as the folder structure isn't something I have a choice in. 

[pendean]

Sounds like you corrected the XLOADCTL variable setting in R2020 to match your R2019: I think you just forget that the XLOADCTL setting you chose allows others in your organization to open and edit that XREF without being locked out by you having it loaded in you open top file.

OPTIONS command's Open/Save Tab > XREFs section > Enable With Copy is what you have chosen with XLOADCTL=2, as most of us prefer to have it. Perhaps that jogs your memory better about it all.

HELP says:"...Enabled with Copy: Turns on demand loading but uses a copy of the referenced drawing. Other users can edit the original drawing...."

[Anonymous]

I hadn't picked up on the others can edit component. Perhaps something I'll need to readdress in the future if I end up with more write users. At the moment everyone using my system is on Read only, using the files as backgrounds but with no edit capability.

I'm really not sure why ACAD2020 installed with the setting incorrect. Odd, but par for the course. It goes on my growing cheat sheet of things to try with my users and in general for troubleshooting.

Any thoughts on why the templates wouldn't work with XLOADCTRL set to 0? Is it as simple as the paths being too long? When I would correct a path(by clicking through the file tree), it would update the "found at path" to an identical path as before (.\DWG Data Base\BACKGROUND\(BUILDING)), I would save the template, but then when relaunched it would lose the path again. I'm still having some occasional failures, and seek to understand.

[pendean]

>>>...not sure why ACAD2020 installed with the setting incorrect...<<<
No idea either, it did not do so here for me.

XREFs problems are all related to pathing (how it is saved in the top file, aka relative vs absolute vs none, as well as physical file location) and rarely much else. Dig a little deeper, not sure we can do much for you over here without screenshots ad no masking of information from you etc.

BTW... Make sure you have the 2020.1 update installed: it fixes many sins.

[Anonymous]

"not sure we can do much for you over here without screenshots ad no masking of information from you etc."

A great frustration for me. I am very active in motorcycle mechanicing and building forums where I can share everything, and love the collaborative nature of the conversation. Trying to get help while working within repressive Intellectual Property guidelines is maddening. Thanks for what you have been able to provide.