Incorrect 3D Cursor Movement with Axis Constraint #68265

Closed
opened 2019-08-05 16:54:50 +02:00 by Doug Cox · 14 comments

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36

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

Short description of error
While moving the 3D cursor press one of the axis constraint keys (x, y, or z). The 3D cursor changes position when the key is pressed.

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]

  • Start Blender with a default scene.
  • Select the Cursor toolbar item on the left (or Shift+Right click)
  • Press the "x" key on the keyboard.

Observe that as "x" is pressed the position of the 3D cursor changes along the Y-axis. This is quite annoying, especially when trying to offset the location of a new object/etc.

This also happens when snapping is enabled with "Absolute Grid Snap" enabled resulting in the position of the 3D cursor not actually being on the grid.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.36 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: (optional) **Short description of error** While moving the 3D cursor press one of the axis constraint keys (x, y, or z). The 3D cursor changes position when the key is pressed. **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] * Start Blender with a default scene. * Select the Cursor toolbar item on the left (or Shift+Right click) * Press the "x" key on the keyboard. Observe that as "x" is pressed the position of the 3D cursor changes along the Y-axis. This is quite annoying, especially when trying to offset the location of a new object/etc. This also happens when snapping is enabled with "Absolute Grid Snap" enabled resulting in the position of the 3D cursor not actually being on the grid.
Author

Added subscriber: @ziflin

Added subscriber: @ziflin

Added subscriber: @tomjk

Added subscriber: @tomjk

This is expected behaviour. Moving an object and constraining along an axis works in the same way. If you want to move only on X axis, then it makes sense to cancel any Y movement. If you want to constrain the cursor to the XY plane (ie. horizontal/ground plane, without Z/vertical movement), press Shift+Z.

edit: can't say for absolute grid snapping though, never used it.

This is expected behaviour. Moving an object and constraining along an axis works in the same way. If you want to move only on X axis, then it makes sense to cancel any Y movement. If you want to constrain the cursor to the XY plane (ie. horizontal/ground plane, without Z/vertical movement), press Shift+Z. edit: can't say for absolute grid snapping though, never used it.
Author

@tomjk Try in top ortho view with Snap + Absolute Grid Snap as I think this demonstrates the issue. I'm able to move it nicely along the grid points and if I have it at a y=0.0 location, when I press "x", then the 3D cursor jumps on the y-axis based on where I initially clicked. It seems to be taking the initial mouse-click location as the position to use when constraining, but this makes it impossible to be positioned exactly on the grid.

If there was a way to move the 3D cursor more like other objects, then this probably wouldn't be an issue as moving an object does snap it to the clicked position first like it does with the 3d cursor.

@tomjk Try in top ortho view with Snap + Absolute Grid Snap as I think this demonstrates the issue. I'm able to move it nicely along the grid points and if I have it at a y=0.0 location, when I press "x", then the 3D cursor jumps on the y-axis based on where I initially clicked. It seems to be taking the initial mouse-click location as the position to use when constraining, but this makes it *impossible* to be positioned exactly on the grid. If there was a way to move the 3D cursor more like other objects, then this probably wouldn't be an issue as moving an object does snap it to the clicked position first like it does with the 3d cursor.

Ah! You're right, that behaviour is almost certainly not as intended.

Ah! You're right, that behaviour is almost certainly not as intended.

Added subscriber: @Patnard

Added subscriber: @Patnard

Might I add that when dragging to move the 3D Cursor, the "move" command window that opens shows the transformation to apply at each update of the values. To understand it better, place the corsor at 0,0,0, then drag to move it a little bit. Shift edit the values in x, y, and z of the move window at the bottom and observe as the cursor doesn't position itself as you'd expect.

To simplify, if (C)ursor = 0,0,0, then (M)ove =1,1,0 then C=1,1,0. If you edit the values in the box to M=0.5,1,0 then C=1.5,2,0. M=1,0,0 C=2.5,2,0.

Editing the values in the box apply the transform everytime they are updated. Seems counter intuitive.

Might I add that when dragging to move the 3D Cursor, the "move" command window that opens shows the transformation to apply at each update of the values. To understand it better, place the corsor at 0,0,0, then drag to move it a little bit. Shift edit the values in x, y, and z of the move window at the bottom and observe as the cursor doesn't position itself as you'd expect. To simplify, if (C)ursor = 0,0,0, then (M)ove =1,1,0 then C=1,1,0. If you edit the values in the box to M=0.5,1,0 then C=1.5,2,0. M=1,0,0 C=2.5,2,0. Editing the values in the box apply the transform everytime they are updated. Seems counter intuitive.

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

Confirmed on Blender 88a872dd6e.

To reproduce:

  • Snap the cursor to world origin (0, 0, 0)
  • Activate the Cursor tool
  • Drag diagonally, starting the drag with the mouse in a different location than (0, 0, 0)
  • Press X
  • Note that the movement of the 3D cursor is now constrained to the mouse cursor's Y and Z location when the dragging started, and not to the expected Y=Z=0 (i.e. the cursor's position when the dragging started).
Confirmed on Blender 88a872dd6eac10e99afbd18243d39be68921642a. To reproduce: - Snap the cursor to world origin (0, 0, 0) - Activate the Cursor tool - Drag diagonally, starting the drag with the mouse in a different location than (0, 0, 0) - Press X - Note that the movement of the 3D cursor is now constrained to the mouse cursor's Y and Z location when the dragging started, and not to the expected Y=Z=0 (i.e. the cursor's position when the dragging started).

Added subscriber: @mano-wii

Added subscriber: @mano-wii

I can't reproduce the problem here.

I can't reproduce the problem here.

In #68265#746816, @mano-wii wrote:
I can't reproduce the problem here.

Here's what it looks like.

3D cursor.gif

> In #68265#746816, @mano-wii wrote: > I can't reproduce the problem here. Here's what it looks like. ![3D cursor.gif](https://archive.blender.org/developer/F7652013/3D_cursor.gif)

What happens here is that the projecting action (at the click of the mouse) gets in the way before transforming the cursor.
It is the same problem described in #69392
So I will merge the reports.

What happens here is that the projecting action (at the click of the mouse) gets in the way before transforming the cursor. It is the same problem described in #69392 So I will merge the reports.

Closed as duplicate of #69392

Closed as duplicate of #69392
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#68265
No description provided.