snap to face broken with mirror modifier #68674

Open
opened 2019-08-15 05:13:06 +02:00 by Casey Connor · 6 comments

System Information
Operating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits
(same behavior on Windows 8.1)

Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-12 22:20, hash: 8d12c2a836
Also broken in 2.80 stable

  • open demonstration blend file with no config dir
  • note that snap-to-face (target:closest, affect:move) is already enabled
  • select small cuboidal in lower left
  • G, then X, to move along X, and attempt to snap to broad side of nearby horizontal cuboidal
  • see that the object flashes erratically, alternately assuming its original position, and alternately assuming an incorrectly snapped position
  • if instead the cuboidal we are trying to move is moved a bit first, without snapping, and then we again try to snap to the face, it doesn't flicker any more, but it still snaps incorrectly (and actually still does flicker on the overlapping face but doesn't jump around in position)
  • if the mirror modifier on the cuboidal we are trying to move is disabled, it snaps correctly

Starting position: starting_position.png

Incorrect snap result: result.png

Correctly snapped result: desired_result.png

Demo blend file: snapbug.blend

**System Information** Operating system: Linux-4.18.0-25-generic-x86_64-with-debian-buster-sid 64 Bits (same behavior on Windows 8.1) Graphics card: GeForce GTX 1060 6GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116 **Blender Version** Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-12 22:20, hash: `8d12c2a836` Also broken in 2.80 stable * open demonstration blend file with no config dir * note that snap-to-face (target:closest, affect:move) is already enabled * select small cuboidal in lower left * G, then X, to move along X, and attempt to snap to broad side of nearby horizontal cuboidal * see that the object flashes erratically, alternately assuming its original position, and alternately assuming an incorrectly snapped position * if instead the cuboidal we are trying to move is moved a bit first, without snapping, and then we again try to snap to the face, it doesn't flicker any more, but it still snaps incorrectly (and actually still does flicker on the overlapping face but doesn't jump around in position) * if the mirror modifier on the cuboidal we are trying to move is disabled, it snaps correctly Starting position: ![starting_position.png](https://archive.blender.org/developer/F7665332/starting_position.png) Incorrect snap result: ![result.png](https://archive.blender.org/developer/F7665338/result.png) Correctly snapped result: ![desired_result.png](https://archive.blender.org/developer/F7665344/desired_result.png) Demo blend file: [snapbug.blend](https://archive.blender.org/developer/F7665323/snapbug.blend)
Author

Added subscriber: @clepsydrae

Added subscriber: @clepsydrae
Author

Same behavior on Windows 8.1, for the record.

Same behavior on Windows 8.1, for the record.
Author

Tested in latest 2.81 as well: still broken

Tested in latest 2.81 as well: still broken

Added subscribers: @ideasman42, @mano-wii

Added subscribers: @ideasman42, @mano-wii
Germano Cavalcante self-assigned this 2019-09-13 15:26:09 +02:00

The problem is that the Snap with of type Closest uses the bound box to snap.
But in this case the bound box varies with the movement.
One solution would be to use Texture Space as it does not change.
@ideasman42, any ideas?

The problem is that the `Snap with` of type `Closest` uses the bound box to snap. But in this case the bound box varies with the movement. One solution would be to use Texture Space as it does not change. @ideasman42, any ideas?
Germano Cavalcante was unassigned by Dalai Felinto 2019-12-23 16:33:18 +01:00

Marked as Known Issue because it is necessary to plan carefully on what to do in these cases and because the problem can be easily remedied by the user.

Marked as `Known Issue` because it is necessary to plan carefully on what to do in these cases and because the problem can be easily remedied by the user.
Philipp Oeser removed the
Interest
Modeling
label 2023-02-09 15:29:40 +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
2 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#68674
No description provided.