So try this
- Create a spline
- Create a cylinder
- Apply path deform
- Choose your original spline as your control spline
- run…
refs.dependents spline
You’ll see the path deform in the result
- delete the modifier
- run…
refs.dependents spline
The path deform is still there, even though the modifier is now gone. Any way to refresh the dependencies?
- Neil
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.
gc() doesn’t work BTW.
- Neil
clearUndoBuffer() doesn’t remove it, fwiw
followed by a gc() still doesn’t remove it
Very odd indeed.