Object bounds by modifiers are ignored by snapping #121103

Closed
opened 2024-04-26 03:50:00 +02:00 by SmartArtCreations · 7 comments

System Information
Operating system: Linux-6.5.0-28-generic-x86_64-with-glibc2.35 64 Bits, X11 UI
Graphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.171.04

Blender Version
Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: e1743a0317bc
Worked: 4.0.2

Short description of error
Object bounds by modifiers are ignored by snapping

Exact steps for others to reproduce the error
Create an array and try to snap on different mesh from different points/vertexes/axis

  1. Create an array in Blender 4.1.1 and do the same in Blender 3.6 LTS. Now try to snap different axis and vertex of it on different vertexes of another mesh. It ignores the rest of counts of the array except the original mesh.

The following issues should be reported separately

  1. Snap toggle got broken since 3.6 LTS (or maybe in earlier version) The snap does not stay on or off if toggles in edit mode. It hasn't been like that since I started using the Blender 2.67. It got broken somewhere in the 3.X versions.

  2. Snapping is not as snappy as it used to be in the previous versions. The closest vertex do not always snap together, I mean now mostly they don't snap like previous versions before 3.X.

There are many other issues with the snapping compared to the older versions before 2.93.

Snapping is one of the most important feature for accurate modeling in the ArchViz. This was one of the key feature which convinced me to switch from 3dS Max in 2014 after using that for more than a decade. Now its been such a great decade with Blender. But its sad to see the key features like snapping getting broken with the every new iteration. It has been good from version 2.67 to 3 but started breaking somewhere after 3.x and introduces new bugs with every new iteration now a days.

Please do not mess with the snapping, its been perfect, let it be like the old days.

Thanks

**System Information** Operating system: Linux-6.5.0-28-generic-x86_64-with-glibc2.35 64 Bits, X11 UI Graphics card: NVIDIA RTX A4000/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 535.171.04 **Blender Version** Broken: version: 4.1.1, branch: blender-v4.1-release, commit date: 2024-04-15 15:11, hash: `e1743a0317bc` Worked: 4.0.2 **Short description of error** Object bounds by modifiers are ignored by snapping **Exact steps for others to reproduce the error** Create an array and try to snap on different mesh from different points/vertexes/axis 1. Create an array in Blender 4.1.1 and do the same in Blender 3.6 LTS. Now try to snap different axis and vertex of it on different vertexes of another mesh. It ignores the rest of counts of the array except the original mesh. --- The following issues should be reported separately 2. Snap toggle got broken since 3.6 LTS (or maybe in earlier version) The snap does not stay on or off if toggles in edit mode. It hasn't been like that since I started using the Blender 2.67. It got broken somewhere in the 3.X versions. 3. Snapping is not as snappy as it used to be in the previous versions. The closest vertex do not always snap together, I mean now mostly they don't snap like previous versions before 3.X. There are many other issues with the snapping compared to the older versions before 2.93. Snapping is one of the most important feature for accurate modeling in the ArchViz. This was one of the key feature which convinced me to switch from 3dS Max in 2014 after using that for more than a decade. Now its been such a great decade with Blender. But its sad to see the key features like snapping getting broken with the every new iteration. It has been good from version 2.67 to 3 but started breaking somewhere after 3.x and introduces new bugs with every new iteration now a days. Please do not mess with the snapping, its been perfect, let it be like the old days. Thanks
SmartArtCreations added the
Priority
Normal
Type
Report
Status
Needs Triage
labels 2024-04-26 03:50:01 +02:00
SmartArtCreations changed title from Snapping is broken with every enw iteration of Blender. to Arrays ignored while Snapping | Snapping is broken with every enw iteration of Blender. 2024-04-26 03:50:47 +02:00
SmartArtCreations changed title from Arrays ignored while Snapping | Snapping is broken with every enw iteration of Blender. to Arrays ignored while Snapping | Snapping is broken with every new iteration of Blender. 2024-04-26 03:51:03 +02:00
  1. Can confirm - recent regression, worked in 4.0.2. Since 4.1.0, object bounds are unaffected by modifiers (array, subdiv) - but only the bounds used for snap purposes, "dimensions" and "display as bounds" are working correctly. Note that the intended behavior is unintuitive and only ever matched the visual appearance of the mesh by accident.
  2. Can confirm - broken/changed between 3.5.1 and 3.6, snap toggle during transform (shift+tab) doesn't affect the toggle state after the operation is done.
  3. Can't really confirm. I use ctrl-snapping constantly (though mostly in edit mode), and haven't noticed any downgrades. The new snap-by-basepoint is much more transparent and reliable, in object more especially.
1. Can confirm - recent regression, worked in 4.0.2. Since 4.1.0, object bounds are unaffected by modifiers (array, subdiv) - but only the bounds used for snap purposes, "dimensions" and "display as bounds" are working correctly. Note that the [intended behavior](https://projects.blender.org/blender/blender/issues/72815#issuecomment-367699) is unintuitive and only ever matched the visual appearance of the mesh by accident. 2. Can confirm - broken/changed between 3.5.1 and 3.6, snap toggle during transform (shift+tab) doesn't affect the toggle state after the operation is done. 3. Can't really confirm. I use ctrl-snapping constantly (though mostly in edit mode), and haven't noticed any downgrades. The new snap-by-basepoint is much more transparent and reliable, in object more especially.
Member

Create an array in Blender 4.1.1 and do the same in Blender 3.6 LTS. Now try to snap different axis and vertex of it on different vertexes of another mesh. It ignores the rest of counts of the array except the original mesh.

Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex?

snap toggle during transform (shift+tab) doesn't affect the toggle state after the operation is done.

Can confirm the change in behavior, was caused by 45379d9b59
Could you, however, create a separate report for this (it just makes sense to handle each issue individually), You can mention the culprit commit there already and ping me in that report if you like.

Snapping is not as snappy as it used to be in the previous versions. The closest vertex do not always snap together, I mean now mostly they don't snap like previous versions before 3.X.

Also not exactly sure what to test here. Can you, again, create a separate report for this?

>Create an array in Blender 4.1.1 and do the same in Blender 3.6 LTS. Now try to snap different axis and vertex of it on different vertexes of another mesh. It ignores the rest of counts of the array except the original mesh. Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex? >snap toggle during transform (shift+tab) doesn't affect the toggle state after the operation is done. Can confirm the change in behavior, was caused by 45379d9b5963e10be7959902a0a47479a1d75c19 Could you, however, create a separate report for this (it just makes sense to handle each issue individually), You can mention the culprit commit there already and ping me in that report if you like. >Snapping is not as snappy as it used to be in the previous versions. The closest vertex do not always snap together, I mean now mostly they don't snap like previous versions before 3.X. Also not exactly sure what to test here. Can you, again, create a separate report for this?
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-04-30 13:51:23 +02:00

Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex?

> Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex?
Member

OK, can confirm that one, will check.

Will update the report description to clarify we are just handling this particular case in this report

OK, can confirm that one, will check. Will update the report description to clarify we are just handling this particular case in this report
Philipp Oeser changed title from Arrays ignored while Snapping | Snapping is broken with every new iteration of Blender. to Object bounds by modifiers are ignored by snapping 2024-04-30 14:43:41 +02:00
Philipp Oeser added
Status
Confirmed
Module
Modeling
and removed
Status
Needs Information from User
labels 2024-04-30 14:45:12 +02:00

Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex?

Attached two files, one created in Blender 4.1 and another in Blender 3.6. Open them in their respective blender versions.

Now move the array object towards left outside the first vertex of the plane in the center, and try to snap. The behavior in the 3.6 is correct but 4.1 ignores the rest of the objects and snaps only the main mesh of the array to the plane.

> > Sorry if I am having trouble following along (it is just not clear to me if what you are trying to snap where). Could you share an example .blend file along with clear steps which vertex you are trying to snap to which other vertex? > Attached two files, one created in Blender 4.1 and another in Blender 3.6. Open them in their respective blender versions. Now move the array object towards left outside the first vertex of the plane in the center, and try to snap. The behavior in the 3.6 is correct but 4.1 ignores the rest of the objects and snaps only the main mesh of the array to the plane.
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-04-30 15:04:23 +02:00
Blender Bot added
Status
Needs Triage
and removed
Status
Archived
labels 2024-04-30 15:07:19 +02:00
Philipp Oeser added
Status
Confirmed
and removed
Status
Needs Triage
labels 2024-04-30 15:09:14 +02:00

Here is the video showing issue with the closest snap mentioned in the point number 3.

Target is highlighted in the circle.

The closest vertex is not snapping with the target, instead the vertex after that is snapping. This issues has been there since long time but has worsen in 4.1 versions.

Here is the video showing issue with the closest snap mentioned in the point number 3. Target is highlighted in the circle. The closest vertex is not snapping with the target, instead the vertex after that is snapping. This issues has been there since long time but has worsen in 4.1 versions.
Member

This was caused by 1cbd0f5a85, but it is actually already fixed in 4.2 (see 935666a622)

@SmartArtCreations : please try a fresh 4.2 build from https://builder.blender.org/download/daily/

Will close, but feel free to comment again if issues persist in a fresh build

This was caused by 1cbd0f5a8583a898ebba45723847d1e5fb3d03a1, but it is actually already fixed in 4.2 (see 935666a622e88f50f525d78e85655e4217b9025a) @SmartArtCreations : please try a fresh 4.2 build from https://builder.blender.org/download/daily/ Will close, but feel free to comment again if issues persist in a fresh build
Blender Bot added
Status
Archived
and removed
Status
Confirmed
labels 2024-05-02 10:26:23 +02: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
3 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#121103
No description provided.