Moving vertices along Y cannot snap to the edge #115699

Closed
opened 2023-12-02 08:17:12 +01:00 by SensArice · 7 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13

Blender Version
Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: d0dd92834a08
Worked: (newest version of Blender that worked as expected)

Short description of error
In the top view, moving vertices along Y cannot snap to the edge.

Exact steps for others to reproduce the error

  • Open attached file
  • Move selected vertex along Y
**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13 **Blender Version** Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash: `d0dd92834a08` Worked: (newest version of Blender that worked as expected) **Short description of error** In the top view, moving vertices along Y cannot snap to the edge. **Exact steps for others to reproduce the error** - Open attached file - Move selected vertex along Y
SensArice added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2023-12-02 08:17:12 +01:00
Iliya Katushenock added the
Interest
Modeling
label 2023-12-02 08:43:39 +01:00
Author

This is not aligned, it is true that the selected vertices are not aligned to this edge, and if there is no screen space in the mathematical model, it will not be really aligned, so whether I should submit a functional request for "snap with screen space", that is, to add the tickable option "Screen space" to "snap menu"

This is not aligned, it is true that the selected vertices are not aligned to this edge, and if there is no screen space in the mathematical model, it will not be really aligned, so whether I should submit a functional request for "snap with screen space", that is, to add the tickable option "Screen space" to "snap menu"
Member

Hi, thanks for the report. I didn't quite understand the use of "screen space" here. Also the reported bug is bit unclear to me.
Do you have difficulties in snapping selected data with the gizmo dragging? I can confirm in that case

Hi, thanks for the report. I didn't quite understand the use of "screen space" here. Also the reported bug is bit unclear to me. Do you have difficulties in snapping selected data with the gizmo dragging? I can confirm in that case
Pratik Borhade added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-04 12:23:46 +01:00
Author

I think the current mobile tool can not snap to the desired edge in the current view, it should be a bug.

About "screen space snap" is a functional request that makes snap more accurate visually.

I think the current mobile tool can not snap to the desired edge in the current view, it should be a bug. About "screen space snap" is a functional request that makes snap more accurate visually.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-12-05 17:38:26 +01:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2023-12-05 17:39:56 +01:00
Iliya Katushenock added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-12-05 19:14:13 +01:00
Author

In the top view, moving vertices along Y cannot snap to the edge, I still insist that this is a bug

In the top view, moving vertices along Y cannot snap to the edge, I still insist that this is a bug
Pratik Borhade changed title from vector snap edge is no screen space ? to moving vertices along Y cannot snap to the edge 2023-12-06 04:53:04 +01:00
Pratik Borhade changed title from moving vertices along Y cannot snap to the edge to Moving vertices along Y cannot snap to the edge 2023-12-06 04:53:12 +01:00
Member

Thanks, can confirm.
cc @mano-wii

Thanks, can confirm. cc @mano-wii
Member

I think I dont get it.

If you move along Y, this should change nothing but the Y value, I mean you are specifically telling blender to constrain the movement to the Y axis and nothing but the Y axis, why would this be a bug?

I think I dont get it. If you move along Y, this should change **nothing but** the Y value, I mean you are specifically telling blender to constrain the movement to the Y axis and nothing but the Y axis, why would this be a bug?

This is not a bug, the vertex is constrained to its expected position: the nearest position between the axis constraint and the edge, regardless of the view angle.

The request in this report is to change this behavior if we are in a side view by making the vertex constraint to the intersection between the axis and the projection f the edge.

While the proposed change in behavior for side views might appear beneficial for specific cases, it introduces complexity for users as they would need to know that the vertex to edge constraint behaves differently in side views. This could also lead to unpredictable results in other scenarios, and we strive to keep behavior consistent across different situations to avoid confusion.

Since this is not a bug but a design choice, I would suggest that any requests for adjusting this behavior be directed to the feature request channels. We encourage users to provide their feedback and ideas, which can be invaluable for the development of Blender. You can do so at the following link: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests.

This is not a bug, the vertex is constrained to its expected position: the nearest position between the axis constraint and the edge, regardless of the view angle. The request in this report is to change this behavior if we are in a side view by making the vertex constraint to the intersection between the axis and the projection f the edge. While the proposed change in behavior for side views might appear beneficial for specific cases, it introduces complexity for users as they would need to know that the vertex to edge constraint behaves differently in side views. This could also lead to unpredictable results in other scenarios, and we strive to keep behavior consistent across different situations to avoid confusion. Since this is not a bug but a design choice, I would suggest that any requests for adjusting this behavior be directed to the feature request channels. We encourage users to provide their feedback and ideas, which can be invaluable for the development of Blender. You can do so at the following link: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2023-12-06 14:22:41 +01:00
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
4 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#115699
No description provided.