I've also noticed that the thing that seriously slows down my code is the OSD mesh creation. On the squirrel (17 106 quads) OSD creation takes 4.346086 sec while the rest of my modifier code takes 3.414331. I'll try to multi thread a part of my code. If that goes well then I might push the time down to around 1 sec for the non OSD creation stuff.

A quick update. I've worked with the GSoC student YimingWu so see if my work would be useful with his LANPR solution (and it seems to be!).

@Brecht Van Lommel (brecht) Yes that was it! Thank you.

I've tried to compile the "2.79" tag and it still is broken for me. However if I download the official 2.79 build, it works like expected :S

Hmm, If you guys can reproduce then I don't know what I should do to figure out what is wrong.
I'm using gentoo portage to build blender from git. So the build directory is clean. I haven't made any changes to the blender code either. So I don't know what it could be.

I have uploaded the ported code to: https://github.com/DarkDefender/blender-npr-tess2

Just a quick heads up. I've managed to get the code to run in blender master and with opensubdiv 3.0.x

Campbell requested some examples with characters so I took some from BBB:

Yes, thank you for making blender FFmpeg 3.0 ready!

I guess the solution to this problem will be the new bmesh boolean stuff? I mean there is no point in trying to fix the problem with carve if it's going the get phased out soon anyways, right?

I can attach a screenshot and try earlier versions, but I thought because the new error doesn't seem to be because of doubles, I'll just upload a blend file again to see if you can reproduce it...

Ah, I had multiple problems with the boolean operator it seems... The one I attached were because of doubles. Or at least it seems to be the case as I didn't manage to get it to bug out anymore.

I didn't personally talk to him about this on IRC, no. Someone else might have though.

In D785#18, @Folkert de Vries (flokkievids) wrote:

Basically, if artists want the feature I'll have a look at it.

Great! :) They (the svg2 board) is looking for feedback. So if you have any requests I'm sure they would love to hear them.

Just a question to flokkievids:
Is there any plans to support SVG2 when it comes out? It seems like a lot of the new features could be useful when exporting from freestyle to SVG.

If the change is indeed deliberate, I would like it to be more obvious that changing the start/end values does nothing with a cyclic path.
While the old behaviour wasn't that great, you could quite easily figure out that you had to have a non cyclic path for best results.

Just to be clear: The blender version that I listed as broken is not the commit that broke it. It's the version of blender that I currently use.