– Some triangle strips (resulting from the stroke tesselation) are incorrect and show a flip at one or more points

– Crashes. Potentially multiple origins, including, if I remember correctly, a problem with the acceleration grid (some points are found outside the grid although they should be inside). Also, it appears that sometimes a TVertex links to NULL ViewEdges, which shouldn’t happen.

– Visibility problems. Some of these problems are due to the fact that Y-junctions are missing in the current ViewMap (at some point, I refactored the ViewMap and I left the Y-junctions on the side and never got to add them back), for instance that would cause wrong visibility on the silhouette of cylinder’s caps. Some other visibility problems can appear if the mesh is too coarse or has a weird mix of “smooth” and “non-smooth” vertices (vertices that share or don’t share their normals across adjacent faces). In that case, the incompatibility between the model and the smooth silhouettes can make it harder to compute a robust visibility.

Like this:

I did not want to “clog up” the BlenderArtists.org site with this error message. It looks like it compiles all the way until the install sequence related to the TIFF definitions, which I have included below. This is on a Linux64, UbuntuStudio computer. I will try it next on the Win32 side. The SVN is 28968. Again, thank you for you continued efforts. It has come along way. The hope that the challenges with SWIG are solved without too much wasted energy.

Backbone-stretch doesn’t seem to have any effect on the drawn lines. I have followed the suggested procedure in the post of december 19th (where it says “…how splitting and geometry modifiers can be combined…” and I get the expected results up to (b), but when I apply backbone stretch nothing happens, even when I set the value to +/- 5000. The model I use is suzanne with one level of subdivision applied, so I think it’s not that. The guiding lines appear just fine.

Thank you for reporting the issue. I just noticed that there was a hard-coded limit that the backbone stretching effect was only applied to those strokes with 2D length longer than 50. In revision 43568 this limitation was removed. I hope this solves the reported problem on your side.

Thanks a lot ! Man, you’re fast….
But: I have found another issue. Now my stroke-style looks as I wanted it, I tried to render an animation. However, blender always quits at “Freestyle: viewmap creation” of frame two. Frame one renders and saves correctly, but then blender crashes. I can provide a .blend-file if required.

I have a problem rendering subdivisions properly. Even a simple subdivided cube renders all sorts of line artifacts where they’re not supposed to be. Here is a sample blend file, created with r43. The Cube on the left has been subdivided with Subdivide. The cube in the middle is subdivided with subdivide and has some triangles. The cube on the right has been subdivided using ctrl-R, and the one above that is not subdivided at all. Notice the artifacts on the cube faces. Not sure where to submit this other than here.

This only happens when Select By Edge Types is un-checked. If I check it, but leave everything at their default settings, the problem vanishes. Suggestive contours, ridges, and valleys seem to re-introduce the problem.

Thanks for your interest on the Blender Freestyle branch. I looked into the .blend file you kindly provided. My conclusion is that the reported issue is not a bug and won’t be fixed (at least in short term), although I see the point that you think this is a problem.

Just for clarification, when the selection by edge types is unused, all possible feature edges are detected. They include suggestive contours, ridges and valleys. In fact, the line artifacts you observed are of these edge types.

As a general note, real numbers in computers are approximated values and cannot be exact in many cases. For example, 0.1 and 0.01 cannot be exact real numbers in comptuers (more precisely, in the case of single precision floating-point numbers such as cooridnates of mesh vertices in Blender). When you subdivide flat meshes into several quads and tris, individual coordinates of mesh vertices can be non-exact real numbers with some differences from the exact numbers.

As far as I can see, suggestive contours, ridges and valleys are very sensitive to this kind of minor differences in real numbers, resulting in line artifacts even on supposedly flat faces. This may be contra-intuitive as you have found, but for now addressing this issue is out of scope in the present Freestyle integration project.

Hi,
I’m having some random crashes which I can’t understand or explain – sometimes a scene will render, and if I close Blender, and start up again with the same scene, it will crash. Using Windows 7 Pro and I think I’m using r43863 (x86/32 bit) with Intel cpu and ATI Firepro v4800 gpu.
When it does render, there are inexplainable lines/edges missing. I’m at a different computer right now, so can’t fully explain. But just wondering if these are known bugs, or just my settings which are bad (crash either way is still a bug).

Thank you for the problem report. I am not aware of issues that may lead to the reported random instability. If you can provide me with a specific .blend file that exhibit the documented problem, I will look into it. If you prefer email, my email address is rd6t-kjym at asahi-net.or.jp.

I get this error upon launch of r47919. I found this when I noted that the same file will open in the Official 4.69a version, but immediately crashes the Freestyle compiled version. Not sure if this is related. I left a note with the developer for object_edit_linked.py.
Thank you for your continued work.
________________________________
location::-1
Cursor monitor: launched
Traceback (most recent call last):
File “C:\Program Files\Blender Foundation\Blender_2.63.11F\2.63\scripts\addons_contrib\object_edit_linked.py”, line 136, in draw
if settings[“original_file”] == “” and ((context.active_object.dupli_group and context.active_object.dupli_group.library is not None) or context.active_object.library is not None):AttributeError: ‘NoneType’ object has no attribute ‘dupli_group’

Thank you for the problem report. As far as I tested, the trunk also has the same issue. I believe the problem is specific to the addon and not related to Freestyle. I saw you have filed a bug report into the addon bug tracker. I hope the addon author can look into the issue.

Ooops. Sorry, I’ve managed to figure out that the problem comes from incompatibility with different versions of OpenEXR libs. Solved now.
(I’ve used to build in chroot with old OpenEXR lib and running on normal system with newer lib causes such error).

First off, thanks for all the great work on Freestyle. I love this (after understanding it from tutorials at BlenderNPR).

I use a lot of “Mean Crease” values on Edges for my Subsurfed Models (especially those with angular, anime looks). For some reason, when also employing “Mark Freestyle Edge”, very often the Mean Crease values on Edges just disappear! This can be EXTREMELY problematic because those Mean Creases are absolutely crucial to my model designs. Crucial. I’ve tried to discover the precise steps which lead to these Mean Crease values just vanishing, but I cannot quite pinpoint them. I will continue to try and find out when and exactly when and why this is occurring. But I wanted to make you (the Freestyle experts) aware of this, and hope that maybe you experts can investigate and solve this.