I'm having an issue with a user in a remote office where her xrefs will not stay loaded. These drawing were created in 2017 without issue.
I tried to detach them and attach them using relative paths, which is default for 2019, and they come in fine but once you close and reopen them, they are unresolved.
After creating this video I went into the xrefs and detached any nexted xrefs, then reinserted them into this drawing and they seemed to work. I went on to check another drawing to see if that fix worked for others and it did not. I went back to this file that seemed to be working only to find it not working again.
Does anyone have any ideas on this? Ever since moving to 2019 my company as a whole has experienced odd XREF behavior. I personally had an issue where nested xrefs would not display if the main xref was clipped.
Solved! Go to Solution.
I'm having an issue with a user in a remote office where her xrefs will not stay loaded. These drawing were created in 2017 without issue.
I tried to detach them and attach them using relative paths, which is default for 2019, and they come in fine but once you close and reopen them, they are unresolved.
After creating this video I went into the xrefs and detached any nexted xrefs, then reinserted them into this drawing and they seemed to work. I went on to check another drawing to see if that fix worked for others and it did not. I went back to this file that seemed to be working only to find it not working again.
Does anyone have any ideas on this? Ever since moving to 2019 my company as a whole has experienced odd XREF behavior. I personally had an issue where nested xrefs would not display if the main xref was clipped.
Solved! Go to Solution.
I'm going to have her run with XLOADCTL set to 0 for the time being. If this proves to cause other issues, I will create a new user account and retry. Honestly, I think that may be the only option left for me on this one if this XLOADCTL set to 0 doesn't hold up.
I'm going to have her run with XLOADCTL set to 0 for the time being. If this proves to cause other issues, I will create a new user account and retry. Honestly, I think that may be the only option left for me on this one if this XLOADCTL set to 0 doesn't hold up.
I think this might be a conversion issue from 2013 dwg formats to 2018 dwg formats. I found two other posts dealing with XLOADCTL not working only when it is set to 2, but 0 and 1 work fine. Both posts mention this issue happening right after switching to 2018.
I'm not sure what causes XLOADCTL set to 2 to stop working but it seems to be more than just me experiencing the issue.
https://forums.autodesk.com/t5/autocad-forum/xref-won-t-load/td-p/7568102
Hopefully it's something the Devs can pint point and offer a fix in a future fix.
I think this might be a conversion issue from 2013 dwg formats to 2018 dwg formats. I found two other posts dealing with XLOADCTL not working only when it is set to 2, but 0 and 1 work fine. Both posts mention this issue happening right after switching to 2018.
I'm not sure what causes XLOADCTL set to 2 to stop working but it seems to be more than just me experiencing the issue.
https://forums.autodesk.com/t5/autocad-forum/xref-won-t-load/td-p/7568102
Hopefully it's something the Devs can pint point and offer a fix in a future fix.
On the User or computer where this issues is happening,
open OPTIONS
Open and Save Tab
(on right under External References (Xrefs))
Switch Demand load Xrefs to Disabled
On the User or computer where this issues is happening,
open OPTIONS
Open and Save Tab
(on right under External References (Xrefs))
Switch Demand load Xrefs to Disabled
I have the same problem in autocad 2019 with the xref manager, and I found the command: CLASSICXREF
view next image:
In "Xref found at" Include the PATH as usual procedure
I have the same problem in autocad 2019 with the xref manager, and I found the command: CLASSICXREF
view next image:
In "Xref found at" Include the PATH as usual procedure
Can't find what you're looking for? Ask the community or share your knowledge.