Malkalypse
12-07-2009, 07:38 PM
I've noticed that when I have sub-object selection, and then add a new modifiier to the top of the stack using MaxScript, the sub-object selection is disregarded.
Case 1:
I apply a mesh select to an object, and select some particular vertices that I want to effect with my next modifier. Leaving the mesh select on the sub-object mode, I manually select the next modifier from the list, and only the selected vertices are affected.
Case 2:
I apply a mesh select to an object and select vertices as before. While still in sub-object mode I add a modifier via MaxScript. The new modifier is added, but the selection is ignored. If I drop back down to the mesh select modifier, it has been reset to sub-object level 0.
(From here I can manually switch to the sub object level I was using, and the correct vertices are selected. Then I can jump back up to the top modifier on the stack and only the selected vertices are affected.)
I'd like to know why this happens, and if there is a way around it?
Case 1:
I apply a mesh select to an object, and select some particular vertices that I want to effect with my next modifier. Leaving the mesh select on the sub-object mode, I manually select the next modifier from the list, and only the selected vertices are affected.
Case 2:
I apply a mesh select to an object and select vertices as before. While still in sub-object mode I add a modifier via MaxScript. The new modifier is added, but the selection is ignored. If I drop back down to the mesh select modifier, it has been reset to sub-object level 0.
(From here I can manually switch to the sub object level I was using, and the correct vertices are selected. Then I can jump back up to the top modifier on the stack and only the selected vertices are affected.)
I'd like to know why this happens, and if there is a way around it?
