Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor #69392

New Issue

Kurt Kellner · 2019-09-01T22:19:52+02:00

Kurt Kellner commented

2019-09-01 22:19:52 +02:00

System Information
Operating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: None so far

Short description of error
Dragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your click-and-drag instruction in reference to the selected object's origin.

Exact steps for others to reproduce the error

Change snapping to Vertex, Edge or Face
Change snapping target to Active
Set active tool to Cursor
Activate snapping during transform
Select default cube
Drag Cursor over cube

Important notes

If you deselect everything it works, but while there's an object selected the snapping won't work.
The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended.
As far as I can tell the offset of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin.
There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: https://blenderartists.org/t/cursor-snapping-issue/1177897
I recorded a video showing the problem: blender_bug_report_complete.mkv
I also uploaded the blend file I used to record the video: bug_report_cursor_snapping.blend

**System Information** Operating system: Linux-5.2.9-125.current-x86_64-with-glibc2.9 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.40 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: None so far **Short description of error** Dragging the cursor and snapping it to a Vertex while having the Target set to Active makes the cursor snap to a point in space that is directly related to where you start your *click-and-drag* instruction in reference to the selected object's origin. **Exact steps for others to reproduce the error** 1) Change snapping to Vertex, Edge or Face 2) Change snapping target to Active 3) Set active tool to Cursor 4) Activate snapping during transform 5) Select default cube 6) Drag Cursor over cube **Important notes** - If you deselect everything it works, but while there's an object selected the snapping won't work. - The problem also happens in Edit Mode, but only if there's an object selected in Object Mode. If you deselect everything in Object Mode and then go back to Edit Mode it works as intended. - As far as I can tell the _offset_ of the snapping is directly related to where you start your click-and-drag in regards to the Objects Origin. - There's a BlenderArtist Topic in which some have tested the behavior in Blender 2.81: https://blenderartists.org/t/cursor-snapping-issue/1177897 - I recorded a video showing the problem: [blender_bug_report_complete.mkv](https://archive.blender.org/developer/F7713337/blender_bug_report_complete.mkv) - I also uploaded the blend file I used to record the video: [bug_report_cursor_snapping.blend](https://archive.blender.org/developer/F7713329/bug_report_cursor_snapping.blend)

Kurt Kellner commented

2019-09-01 22:19:52 +02:00

Added subscriber: @AlienTux

blender-admin commented

2019-09-01 22:19:52 +02:00

#68265 was marked as duplicate of this issue

Philipp Oeser commented

2020-01-02 19:16:23 +01:00

Added subscribers: @mano-wii, @lichtwerk

Philipp Oeser commented

2020-01-02 19:16:23 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2020-01-02 19:16:23 +01:00

Looks like a bug to me.

The offset seems to be the negative distance between active object in relation to the snap element.
Makes sense if you actually have other objects selected, to me it doesnt really make sense for the cursor tool.
(In a way, snapping with active using the cursor doesnt really make sense to begin with, but...)

It is probably best to have no offset at all using the cursor.

@mano-wii: Would you agree?

(confirming for now with low prio...)

Looks like a bug to me. The offset seems to be the negative distance between active object in relation to the snap element. Makes sense if you actually have other objects selected, to me it doesnt really make sense for the cursor tool. (In a way, snapping with active using the cursor doesnt really make sense to begin with, but...) It is probably best to have no offset at all using the cursor. @mano-wii: Would you agree? (confirming for now with low prio...)

Germano Cavalcante commented

2020-01-03 03:20:30 +01:00

In #69392#841268, @lichtwerk wrote:
(...)
It is probably best to have no offset at all using the cursor.

It may be better, but it is not the most correct.
Snap with Active indicates that you use the origin of the active object as the point to snap with.
The problem here is that two operations are called: One when you click and other when you drag the cursor.

When you click with the mouse button, the 3d cursor is projected elsewhere.
Thus origin is no longer in the expected place when you drag, move and snap the 3d cursor.

This is a keymap issue, I'm not sure how to avoid this.

> In #69392#841268, @lichtwerk wrote: > (...) > It is probably best to have no offset at all using the cursor. It may be better, but it is not the most correct. `Snap with` `Active` indicates that you use the origin of the active object as the point to snap with. The problem here is that two operations are called: One when you click and other when you drag the cursor. When you click with the mouse button, the 3d cursor is projected elsewhere. Thus origin is no longer in the expected place when you drag, move and snap the 3d cursor. This is a keymap issue, I'm not sure how to avoid this.

Germano Cavalcante commented

2020-01-24 19:28:36 +01:00

Added subscribers: @ziflin, @dr.sybren, @Patnard, @tomjk

Yianni Papazis commented

2021-07-23 12:36:11 +02:00

Added subscriber: @Yianni

Yianni Papazis commented

2021-07-23 12:40:31 +02:00

I've been finding this frustrating too. I usually have my Pivot Point set to Active Element and my snapping mode set to Center. Whenever I use the 3D cursor tool I have to change my Pivot Point to 3D Cursor in order to snap to where I want it - then change my pivot point back to Active Element.
I feel like the 3D Cursor tool should just ignore the Pivot Point you have set and always use the 3D Cursor as the Pivot Point.

I've been finding this frustrating too. I usually have my Pivot Point set to Active Element and my snapping mode set to Center. Whenever I use the 3D cursor tool I have to change my Pivot Point to 3D Cursor in order to snap to where I want it - then change my pivot point back to Active Element. I feel like the 3D Cursor tool should just ignore the Pivot Point you have set and always use the 3D Cursor as the Pivot Point.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Click-and-Drag the Cursor with Snapping enabled and an Active Object selected missplaces the Cursor #69392