[Closed] ProCutter madness
Hi Everyone,
I’m currently working on a MAXscript that uses Procutter to cut an object up into fragments. Based on user settings the script creates the cutter object(s) then performs the cutting operation. Once the object has been cut up, I delete the cutter object to remove it from the scene. After I do that is where MAX becomes unstable. After running the script, if I randomly select the fragments created by the Procutter operation MAX will crash. This happens every single time. I’ve replicated the problem on a coworker’s computer as well.
Through trial and error I found that if I selected and deleted the cutter object manually as opposed to in the script, MAX will not crash. I’ve tried every alternate method to delete the object in the script that I can think of (deleting it in a separate function, converting the cutter to an editable poly then deleting it, etc.) and all have the same result, MAX crashes. If I delete it by hand, MAX is completely stable.
I’m curious if anyone on this forum has had similar problems using Procutter with MAXscript or knows what’s happening or if I’m doing something wrong.
Thanks,
-Brian
I’m not in front of 3ds Max right now so I can’t check this myself… What if you were to put the procutter object into a group, then delete the group? Another thing you could try doing is a garbage collection gc() before/after deleting the procutter object…
Thanks for the quick reply Christopher. Doing a garbage collection before deleting the cutter object did the trick.
I’m a new member of this forum and recently starting doing MAXscript. It’s great to have a resource like this. Thanks a ton for your help.
-Brian Feldges