Soviut
08-03-2007, 05:37 PM
Some of the modellers at our studio are wondering if its possible to extend the DeleteHistory command to ignore smooth nodes. Smooth nodes and SmoothProxy nodes are used extensivly for testing how final geometry will look when its tessellated by the renderer.
They'd like to be able to keep those nodes in their scenes while they're modelling so they can turn them on and off rather than having to apply and delete them all the time. Likewise, there have been a few occasions where the modellers have accidentally forgotten to delete the smooth nodes before baking the history, causing the smooth nodes to be baked into the geometry.
From what I've researched, I can cycle through objects and try applying "delete -ch" on them based on their connections. But there are all sorts of special cases where I'll need to replace primitives like PolyCube with a polySurface node and such.
Is there any way I can use the IsHistoricallyInteresting attributes to avoid having the nodes baked by delete history?
They'd like to be able to keep those nodes in their scenes while they're modelling so they can turn them on and off rather than having to apply and delete them all the time. Likewise, there have been a few occasions where the modellers have accidentally forgotten to delete the smooth nodes before baking the history, causing the smooth nodes to be baked into the geometry.
From what I've researched, I can cycle through objects and try applying "delete -ch" on them based on their connections. But there are all sorts of special cases where I'll need to replace primitives like PolyCube with a polySurface node and such.
Is there any way I can use the IsHistoricallyInteresting attributes to avoid having the nodes baked by delete history?