View Full Version : Deleting modifier does not update dependencies
01-23-2008, 05:27 AM
So try this
1) Create a spline
2) Create a cylinder
3) Apply path deform
4) Choose your original spline as your control spline
You'll see the path deform in the result
6) delete the modifier
The path deform is still there, even though the modifier is now gone. Any way to refresh the dependencies?
01-23-2008, 06:01 AM
Just to add to this thread - although I don't know how to refresh the dependencies list (one possible attempt resulted in a max crash in Max 2008), the basic problem is that the modifier appears to be perfectly valid; which somewhat hinders detection of whether the spline is being used in a path deform modifier.
There is a method to check, by looping over the dependents of the modifier and checking if one of them is a valid node or not (if not, then the modifier is not applied to any node), but if there's a way to refresh dependencies.. that would be much cleaner :)
Looks like there needs to be a way of refreshing the dependancy stack. I'm thinking that it is still a dependent because it is held in the undo stack. Maybe a GC() call but that is rather drastic. It is like there needs to be a way to clear just that node from the memory or undo stack.
01-23-2008, 10:57 PM
gc() doesn't work BTW.
01-24-2008, 12:56 AM
clearUndoBuffer() doesn't remove it, fwiw
followed by a gc() still doesn't remove it
01-24-2008, 03:16 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.