So what should we use instead?

I don't believe that any caches (tesselation, ray, etc) are stored in the detail anymore, so you can just remove the call entirely.

Ondrej's correct. It's not needed.

A possible exception (so far as I know, nobody's checked, so it might not really be an exception) is if you're using the GL1 or GL2 viewports, there's a chance that they may be out of date for some operations like selecting things. I don't think anybody knows for sure.

The big thing is that in the next major version of Houdini, it's certainly unnecessary, and may be eliminated. Of course, there is an obscure case that probably nobody is depending on, but if someone was using notifyCache to increment the meta cache count when switching between two different sets of expression local variables, it'd need to be replaced with gdp->incrementMetaCacheCount().

Hopefully that clears things up! :wink:

Thank you for clarification.

I had forgotten about the old viewport. You'll also need to keep that call if you're using the H11 viewport for whatever reason in 13.0.

Ondrej
I had forgotten about the old viewport. You'll also need to keep that call if you're using the H11 viewport for whatever reason in 13.0.

… but the H11 viewport *isn't* in 13.0. (wink wink, shhhhhh) :shock:

I'm not using any H11 stuff anymore. Thanks to TWOD http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=29374&highlight=GUI [sidefx.com] I moved my four letters to OGL3 (and C++11) for any future expeditions.

As for notifyCache(), I'm cleaning my library of HDK stuff, and with it all the things that become depracated between 12.5<=>13, like not using gdp->primitives().entry(*primIT)->getNum() for retrieving index of prim which still relies on GEO_PrimList. Small changes here and there and right now I don't have any warnings beside some standard stuff that warns about precision loosing between some casts.