Strip XREFs form scene?

[Morne]

Hi all

Asset tracker lists 2 xrefs in my scene (even after refresh). When I open the file, it says it can't find objects in that xrefs.

However if I check in "Xref Scene" or "Xref Object", it's blank?!?

Where's the xrefs coming from and how can I strip it from the scene?

[YoyoBoy]

I had this problem recently, and I'm not sure I figured out what caused it. But I got around it by merging things into a new blank scene.

[YoyoBoy]

Oh, I think the origin of the problem might have been that I was XReffing objects that had identical names.

[steveblake]

...how about creating another xref with the same name, resetting the reference to that new object / path, and then merging and deleting?

[Morne]

I created 2 blank max files just so the xrefs are found, but then it is trying to find a gazzillion objects in those files.

It's not that big a deal, because my main file still renders fine, just a little annoying having these "errors" in the file in the 1st place and the fact that I can't remove the xrefs from asset tracker.

(OH and by the way, even though I created blank max files to "replace" the missing xrefs, in my main scene I CANT change the paths to the xrefs! Very weird)
The file is from a 3rd party, maybe they have some strange plugins or something on their side

[YoyoBoy]

Check if your xrefs have xrefs.

[Morne]

Check if your xrefs have xrefs.

Seems you missed the main point of the thread.

I have 1 max file and NO xrefs. In this max file, no xrefs are linked or loaded. No xref objects are linked or loaded either. However Asset Tracker disagrees and it "sees" 2 xref files. I can't change the path to those xrefs, even if I cheat and create 2 blank files.

[YoyoBoy]

But what happens if you simply start Max, merge all (and only) your scene's objects in, save, and reopen?

[Morne]

If I merge everything into a new file, the xrefs are gone. But then when I save the new file and re-open, max crashes
some weird stuff there. Anyways, can't spend more time on it now. It works as is with the "broken" file. Will revisit later