Hi everyone, I know this report is quite old, but I think this is fixed in master by a change I made recently (see rB288d7794d4c6836e1322d5ed943c4fbd4b0b0e54)?

I can reproduce this on the old version you are using, however this is not the case with a build from today. So I'm marking this as resolved

I should note that I didn't need to move the subsurf modifier to get this result. It's enough add it first and add a skin mod on top.

Hi Sergey,
thank you so much for your clear answer.

A bit more general task is T58833, this has the same root, so will merge that in...

Seems to be tied to

Confirmed in that particular file, working fine if Load UI is disabled when opening, checking...

Awesome!

Thank you for the follow up, but after I installed the latest build the issue seemed to get resolved.

OpenSubdiv expects topology to be ordered in an uniform manner. This is exactly what's happening when you invoke "Make normals consistent".

This is similar to, probably the same as, the issue discussed in T47129.
Looks like the template has to change to create & copy the CD_BWEIGHT custom data layer. I will look into this.

Normally that should not affect the subdivision result, so still seems like a bug.

Hi guys,
as reported by a my friend the recalc of the outside normals solve the problem.
So at this point I am not sure if it's a bug or something else.

Hi Bretch,
sorry, I forget to add it.
Now I added it.

Thanks for the report, but we need a .blend file to reproduce the problems.

Cannot reproduce (as of rB5c8f1053b5f0, also tried latest buildbot)

This has been fixed already: https://developer.blender.org/rBe666ee965c63322531fba5203905e7d9ca567ed3
Please download a new Blender build.

Any news on this one? I am sort of hoping this will work soon, everything else seem to work fine for me at the moment.

The subdivision modifier for beveled curves also does not work.

Yeah, binding is totally broken actually…

In fact, we need special handling for both limit cases (180° == no split by angle, and 0° == split on all edges).

I had some info from an other user...
From the (wip) release notes : Note however there are still some missing features in the new implementation, particularly: ... Vertex creases support (to mark vertices as sharp or semi-sharp) ... We plan to added these improvements in the 2.8 series.