Copying Assets option in SMTD - Maxscript errors

Hi,

Under the Assets tab in SMTD I leave it to ‘Do NOT copy external files to the repo’ for all my submission scripts, and this works fine.

I’m trying to sort some AWS files without the need for merging everything before sending, but choosing either of the other Asset options (Copy LOCAL External File References to Repository/Copy ALL External File References to Repository) just throws up a massive error in the Maxscript listener (attached)

I’ve tried making sure everything is on our file server and accessible, but it is only the Do NOT copy… option that manages to submit a job properly.

The scene only contains a teapot, with another teapot xref’d in.

Any ideas?

Thanks

maxscripterror.zip (6.7 KB)

The ‘No ““get”” function for undefined’ is going to be a tough one to make a guess on. We’re trying to pull some information from a variable that isn’t set to anything.

Mind sending over that teapot and I’ll make a dev issue for it? I don’t think this is affecting others. I’ll ask another client who I know is using Max with AWS Portal.

Update: I dug into the code at that point, and it seems like a problem specifically with XRefs (line 2943 of SubmitMaxToDeadline_Functions.ms):

--Restore Scene XRefs
for i = 1 to (xrefs.getXRefFileCount()) do
(
    local o = (xrefs.getXRefFile i)
    o.filename = SMTDExternalRefsArray.StoreSceneXRefs[i][2]
)	

Hi Edwin,

On checking, it does actually copy the xrefs to the repo and the job starts, it’s just that the maxscript error is killing the submission script from finishing cleanly.

1 Like

Thanks for thee research there! I’ve opened the dev issue on our side.

So, if the job starts, does it render? I’m just trying to gauge how much pain this is causing.

Everything looks like it renders fine, but the problem is that it breaks the submission script that we use (that does a precalc/render/tile assembly sub).