Page MenuHome

Snap does not work properly with "Surface" object
Closed, DuplicatePublicTO DO

Description

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 760/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.02

Blender Version
Broken: version: 2.81 (sub 3), branch: master, commit date: 2019-08-26 20:39, hash: rBce2368cf69f5
Worked: (optional)

As the title suggests, the snap functions do not work correctly in "edit mode" of a "Surface" object.

  1. Create a surface object such as a "Nurbs Curve".
  2. Change the snap from the grid to the vertices.
  3. Duplicate a curve and move it with respect to the first
  4. Move a CP by pressing CTRL and point the mouse to another CP
  5. Snap fails

Event Timeline

Looks like, Grid Snapping is executing even changed to others e.g. vertex

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 30.Aug 28 2019, 11:55 AM

Working fine here (rBf88022b96f3a, linux, 970m, 430.26 drivers), see

  • is this failing in above file for you, too?
  • have you recently upgraded your driver? (I need to upgrade mine as well), just asking because I had another report with the newest driver failing, whereas an older driver worked fine...

@Philipp Oeser (lichtwerk) Same problem in your provided test file...
However, I think... you were checking in Curves Type Objects...
The proposed problem is more with Surface Type Objects


System Information
Operating system: Windows-10-10.0.16299 64 Bits
Graphics card: AMD Radeon HD 8400 / R3 Series ATI Technologies Inc. 4.5.13399 Core Profile Context 15.200.1065.0

Philipp Oeser (lichtwerk) raised the priority of this task from 30 to 50.

@Abid Maqbool (cto.abid) : Ah, thanx for pointing this out [my bad, sorry].
Can confirm for Surface Types.
However 2.79 did the same thing here, will need some digging why this is...

So might be falling back to Increment on purpose, will check code on it...
(will confirm/claim for the time being though...)

This is a feature that has been requested for a long time (T51249).
I will use this report to keep a track.

Yes, I hope this can be fixed as well. I just came across this behavior myself trying to snap a nurbs surface to other vertices. It definitely would be beneficial to have vertex snapping for nurbs surfaces for greater precision. Thanks!