Gdp->clearanddestroy() - What's It Doing ?

[eloop]

Hi,

I'm trying to write a creation sop that add's a bunch of points to the gdp, then makes some prims with them, always keeping the same gdp->points() modulo moving their positions around.

So each cook instead of gdp->clearAndDestroy() I simply delete all the primitives (btw is there a fast single call to do this ?). This works, but I have a display anomaly where it looks like the normals that have been calculated to display the first geometry have been cached and aren't being re-calculated as the prims are changed. I've tried gdp->destroyCache() to no avail (actually not sure what it's doing ?). Doing something as simple as placing a Facet sop down (with no options checked) after the node fixes the problem.

-Drew

[sibarrick]

Maybe it's quicker to copy all the points from your input gdp into a scratch one, then destroy the original, do all your munging around then merge the scratch one back into the original.... if you see what I mean. Just a suggestion, don't actually know if this is quicker.