@Emil Assarsson (metabaronen)
I've added this functionality, albeit in my official soc branch for now.
You can test it out by building my branch: soc-2017-normal-tools.
Tue, Jul 25
Wed, Jul 19
Thank you! Let me know If there is anything I can help with :-)
@Bastien Montagne (mont29) Would love to take this on ;)
Thanks for the report, but don’t think this should be changed actually, this is supposed to affect normals as vertices ones, not really split ones…
Tue, Jul 18
Sun, Jul 16
Try enabling the Bevel Checkbox located in the Mesh Display panel the N Toolshelf area on the right of the 3D view like in the image below.
Sat, Jul 15
Tue, Jul 11
The value is used, this is more of a documentation issue, committed edit.
Mon, Jul 10
Sun, Jul 9
Wed, Jun 28
Jun 26 2017
Uuuh… yes indeed… :/
Jun 15 2017
Hello. SmartF with pep8 standart.
Jun 9 2017
Jun 8 2017
Jun 5 2017
Tha sanp in blender still does not support occlusion (ignoring elements that are behind faces).
Blender 2.8 will bring some changes to the mesh mapping that will influence the snapping code. The implementation of occlusion test can be thought of in a more efficient and simple way when this change in the meshes has been implemented.
Jun 2 2017
I can confirm the bug.
I tried on a not-saved file and I see no bug. I don't see any reason in this case how not saving the file could influence snapping.
The problem is more that snapping doesn't respect the 'limit to visible' toggle of selection mode.
I think @Germano Cavalcante (mano-wii) wrote a patch for this, not sure if it's ready for release? Will let you decide on this one.
Jun 1 2017
Can this be reverted to the previous behavior before the release? I depend on this very often in my work.
May 31 2017
Edge group for bevel could be better than vertex group
Someone else requested something similar to what you suggest -- just that when some vertices get blocked, they stay there and the unblocked ones continue to move. Maybe this should be the default, but I'd like to get some kind of consensus from artists before changing. As you say, it could be an option, but there is a lot of pushback on Blender devs from Ton not to add too many options to tools, but rather make them smart enough to "do the right thing" without options.
May 30 2017
I can confirm the bug on 2x RX 480 with latest driver and latest buildbot
I can also confirm that the bug wasn't in 2.78c, so it's a regression. I can't change the titel so I set to high as regression have higher priority.
I also had to zoom a lot more to trigger the bug.
May 29 2017
I think what I'd like to see is a threshold that prevents close vertices from overlapping without blocking the movement of vertices that are far from each other. I suppose something like a weighting that diminishes the bevel effect for close vertices.
Something like in the following which shows how Edge-Slide has less impact on close vertices but a large influence on vertices with larger distances. I think this would have to be an option though since it would best suit organic or choppy shapes like rocks. It would likely be inappropriate for machined surfaces.
Another requested bevel clamping change. See T50994. Requester would like clamp to apply to edges individually rather than globally. Could be consider as breaking backward compatibility for 2.8. Or an option (but we dislike adding too many options).
I can't think of a single use case where handling each vertex is more preferable than island during translate operation. But I can bring a lot use cases for handling whole island in hard surface area, including jewelry modeling.
May 27 2017
More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.
hi, could add this to contrib shortly, would need the pep8 clean up first