so opensubdiv really is just for optimal animation preview?

thought it was a whole new subdiv display algorithm which can completely replace catmul-clark, but after seeing it brings incorrect mesh display in a few cases, i wonder is it the coding thing or due to its nature that it speeds up by only do the approximation thus only useful in very specific occasions (mainly animation preview)?

For now, it’s mainly to be used for animation preview, but the Blender devs. will be working on expanding the implementation over time to include more areas of Blender.

As for the approximate normal interpolation in OpenSubDiv, this will continue to be the case until Blender’s graphics code supports tessellation shading (which is not the case right now).