Error on first time running script, fine after rerunning.

[chad_voller]

SOLVED on my end.

As the title says, when I run my maxscript for the first time after a max restart, I get an error message. If I rerun the script, it works fine from then on out. The problem is when it errors out the first time, it made it part way through the processing of the object, so it messes up the material IDs on it. The script is supposed to take a selection's multi/sub-object material and combine it with another, and then assign that combined multi/sub-object material to the objects selected, and all of their instances found in the scene.

[denisT.MaxDoctor]

As I see it, the addNewSubMats function is passed the oldMat parameter, which may be undefined at the beginning. But you are trying to get its name, expecting it to be some valid material. You should check this case...

But of course, it could also be something else. So along with the problem always provide all popup messages and the maxscript listener output.

[chad_voller · Accepted solution]

I moved the lines having to do with addInstancesToSel, to be located after it returns from the other functions, instead of being inside of one of those functions, and that seems to have fixed the issue.

[denisT.MaxDoctor]

---

@chad_voller wrote:

I moved the lines having to do with addInstancesToSel, to be located after it returns from the other functions, instead of being inside of one of those functions, and that seems to have fixed the issue.

---

That was most likely the issue, but what I noticed above should also be fixed.

[chad_voller]

I'll look into it, I appreciate the advice!

[hagen.deloss]

Hi @chad_voller @Anonymous ,

Do you think one of these outcomes could be marked as a solution here, or was the issue inconclusive? 

[chad_voller]

I fixed it on my end, I should have tried what I did before posting.