Sorry, not familiar with that the source node of mesh. Could you please explain?

My own solution is really crappy, so I was wondering if there is a better one, but under condition it worcks with older max versions. Like I said my e…

If you read my very first post, you see that bsearch can´t worck for me, as it´s some feature avaible only in newer max versions. Never said your solu…

OK, checked maxscript reference and findItem seems to be avaible for all max versions, but the explanaition there says it just makes a ‘==’ comparison…

Like I said my english is very bad, so I was misunderstood. I said my solution is crappy. I have also apologiezed for that misunderstanding.

Really sorry, never wanted to waste your, or somebody else time, like I said in the very first post need a solution that worcks with older max version…

Really no reason to get agresive, for me the arrays in your solution looked just like normal arrays. Sorted arrays, as far I know are only avaible in …

Nah, can still keep 2 dimensional aray, but just with a diferent structure. I mean something like this: #(#(), #()). Howevwer that ‘FindItem’ could be…

Not a better solution, then what I have at the moment. My curent solution is just a 2 dimensional array, where the first value is the name string and …

OK, looks like I finally know what the problem is, the mesh inside the file is f*cked up. There is a code in my script like this: rot_obj = eulerangl…

Would it be helpfull, if i upload my script with the coresponding file, that produces the problem?

Will try this code. Have to mention that in my code I am using meshop and not polyop, can this be the reason for my problem?

PolyTools3D: That clearly means that a mesh can have more than 256 materials. Have you considered the possibility that there may be something wrong…