Okay, here’s one that’s got me kind of freaked out…
We’re getting “Unresolved XRef” errors on some of our scenes, despite the file actually existing.
In fact, if I do a doesfileexist ((xrefs.getXRef 1).filename) (assuming the first xref is the culprit), it returns true!?
In general this is only a minor issue, but we send these files to the render farm as scripted jobs and this dialog is killing us…
Any ideas !?
Running Max 9 x64
Shane
hey shane,
try creating a dummy scene by deleting all the objects in the xref giving you errors, and xref scene it into a brand new max and try the BB render again. It could be a bad object or something existing in the xref scene.
-Colin
I fixed the last file enabling the xref in question (it was disabled at the time) and for some reason we are no longer getting the error on that file, but I am told there are others. As soon as I can get my hands on one, I’ll give it a try…
Shane