Page MenuHome

Snapping vertices with subserf modifier is harder in 2.71 RC2
Closed, ResolvedPublic

Description

System Information
Archlinux
GTX 460

Blender Version
Broken: 2.71 RC2
Worked: 2.68a

Short description of error
Snapping vertices with a subserf modifier doesn't work very well in RC2.

Exact steps for others to reproduce the error

  1. Open
  2. Press G and hold Ctrl while moving the cursor over one of the vertices on the cube. In 2.68a it's super easy to get it to work, but in RC2 it almost never snaps.

Revisions and Commits

rB Blender

Event Timeline

Kitt Zwovic (gandalf3) raised the priority of this task from to 90.
Kitt Zwovic (gandalf3) updated the task description. (Show Details)
Kitt Zwovic (gandalf3) edited a custom field.
Campbell Barton (campbellbarton) changed the task status from Unknown Status to Archived.EditedJun 18 2014, 8:44 AM
  • comment removed (replied to wrong report) --

@Campbell Barton (campbellbarton) I see now. I didn't realize the snapping behavior has been improved between 2.62 and 2.71 to use the deformed edit cage. Very nice addition, thanks to whoever added that :)

However, I'm still not quite sure this is the most useful behavior..
Maybe when snapping with modified edit cage enabled, perhaps there should be an option to snap to the true position of the geometry instead?

So in the case of the vertex snapping to the modified edit cage, with the cursor on the apparent, modified location of the target vertex, the vertex being transformed would go to the true (unmodified) location of the target vertex.

Wait, I'm confused..
Where you perhaps thinking of T40680? I was thinking I was writing about that bug when I wrote the above comment..

If not, then I fail to see what auto merge has to do with this.. (I mis-named the .blend because I got slightly mixed up on which file was which when writing T40680 and this report)

Campbell Barton (campbellbarton) changed the task status from Archived to Unknown Status.Jun 18 2014, 10:48 AM

Mistakenly confused this report with the T40680, re-opening.

Looks like this is a regression caused by rB7b5fe4f316234022a0ab761b694cd459ce98db2d

Bastien Montagne (mont29) lowered the priority of this task from 90 to Normal.Jun 18 2014, 11:06 AM
Antonis Ryakiotakis (psy-fi) changed the task status from Unknown Status to Resolved.Jun 18 2014, 5:40 PM

Closed by commit rB47ec0394ca3d.