Snap doesn't work properly every time #54741

New Issue

william willybid · 2018-04-20T14:11:00+02:00

william willybid commented

2018-04-20 14:11:00 +02:00

System Information
Win7

Blender Version
Broken: (example: 2.79 (all versions as far as I know have the same issue)

Short description of error
The snap tool doesn't work as expected every time

Exact steps for others to reproduce the error

Blender is a great piece of software but unfortunately sometimes it is lost in a glass of water for nothing ;'-)

Some times when using the snap function in blender (the red magnet to be more precise) the snap doesn't work as expected. For example if it is set snap to closest and there is a complex mesh frequently it snaps to the other side and not to the nearest.
It would be great to solve little issues like this in next updates or releases.
I don't attach any file because I'm pretty sure this is a well known little issue that every artist has to solve with some work around (3D cursor, object origin... etc). But, if I am allowed to, I would like to suggest to see the following video https://youtu.be/6gUWN19kdbQ?t=150 that starts explicating some of the problems everyone knows well.

Also it would be great to have the possibility to activate multiple snap target simultaneously as for example allows to do autocad or other CAD software around.
I would suggest a little different approach for the Snap target menu selector, replacing the drop down menu with a selector similar to the manipulator widget that allows to select more option at once.

EDIT 23.04.2018 :
Another thing that work bad is when you need to snap a vertex to an edge and the targeted edge is inclined and not orthogonal to the grab direction of the vertex: the snap point scrolls along the edge making difficult to snap in the correct spot
IMHO there is the need to create some more constraints to limit on demand the snap point sliding along the edge when it is unwanted. The way it is now it doesn't work well if what you need is a precise job.

Thanks so much.

**System Information** Win7 **Blender Version** Broken: (example: 2.79 (all versions as far as I know have the same issue) **Short description of error** The snap tool doesn't work as expected every time **Exact steps for others to reproduce the error** Blender is a great piece of software but unfortunately sometimes it is lost in a glass of water for nothing ;'-) Some times when using the snap function in blender (the red magnet to be more precise) the snap doesn't work as expected. For example if it is set snap to closest and there is a complex mesh frequently it snaps to the other side and not to the nearest. It would be great to solve little issues like this in next updates or releases. I don't attach any file because I'm pretty sure this is a well known little issue that every artist has to solve with some work around (3D cursor, object origin... etc). But, if I am allowed to, I would like to suggest to see the following video https://youtu.be/6gUWN19kdbQ?t=150 that starts explicating some of the problems everyone knows well. Also it would be great to have the possibility to activate multiple snap target simultaneously as for example allows to do autocad or other CAD software around. I would suggest a little different approach for the Snap target menu selector, replacing the drop down menu with a selector similar to the manipulator widget that allows to select more option at once. **EDIT 23.04.2018 :** Another thing that work bad is when you need to snap a vertex to an edge and the targeted edge is inclined and not orthogonal to the grab direction of the vertex: the snap point scrolls along the edge making difficult to snap in the correct spot IMHO there is the need to create some more constraints to limit on demand the snap point sliding along the edge when it is unwanted. The way it is now it doesn't work well if what you need is a precise job. Thanks so much.

william willybid commented

2018-04-20 14:11:00 +02:00

Added subscriber: @willybid-4

Ray molenkamp commented

2018-04-20 14:34:58 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2018-04-20 14:34:58 +02:00

"I'm not going to attach a .blend cause i think it's common, also here's a 30+ minute video for you to watch" is not a great way to report a bug.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

Marking as "Incomplete" until the requested information/data is provided.

"I'm not going to attach a .blend cause i think it's common, also here's a 30+ minute video for you to watch" is not a great way to report a bug. Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc. A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports Marking as "Incomplete" until the requested information/data is provided.

william willybid commented

2018-04-20 15:20:27 +02:00

In #54741#495806, @LazyDodo wrote:
"I'm not going to attach a .blend cause i think it's common, also here's a 30+ minute video for you to watch" is not a great way to report a bug.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

Marking as "Incomplete" until the requested information/data is provided.

Thanks for the fast answer.
Sorry, I understand your point of view so I'm going to be more precise: the important part of the video for the issue in object I'm referring to in the main post is just the part from 2.30 to 3.05 minutes more or less. Following the video is very clear what is the problem I think every artist faces with blender snap weird behavior.
For the blender attached file: after watching the video I'm pretty sure that there is no need of it because the video in object per se is far more clear than a generic blend file with some entities in it.
I have edited the main post link to the video to point directly to the right point.
Thanks again for comprehension and I apologies for my previous imprecision.

> In #54741#495806, @LazyDodo wrote: > "I'm not going to attach a .blend cause i think it's common, also here's a 30+ minute video for you to watch" is not a great way to report a bug. > > Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc. > > A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports > > Marking as "Incomplete" until the requested information/data is provided. Thanks for the fast answer. Sorry, I understand your point of view so I'm going to be more precise: **the important part of the video for the issue in object I'm referring to in the main post is just the part from 2.30 to 3.05 minutes more or less**. Following the video is very clear what is the problem I think every artist faces with blender snap weird behavior. For the blender attached file: after watching the video I'm pretty sure that there is no need of it because the video in object per se is far more clear than a generic blend file with some entities in it. I have edited the main post link to the video to point directly to the right point. Thanks again for comprehension and I apologies for my previous imprecision.

william willybid commented

2018-04-24 02:08:56 +02:00

This comment was removed by @willybid-4

*This comment was removed by @willybid-4*

Germano Cavalcante self-assigned this 2018-04-24 02:10:29 +02:00

Germano Cavalcante was unassigned by william willybid

2018-04-24 02:10:34 +02:00

william willybid commented

2018-04-24 02:10:34 +02:00

Added subscriber: @mano-wii