BMesh Operator "connect_vert_pairs" bug in special cases #112772

Open
opened 2023-09-23 13:55:48 +02:00 by Peng Yan · 1 comment
Contributor

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99

Blender Version
Broken: version: 4.0.0 Alpha, branch: dev_connect_vert (modified), commit date: 2023-09-22 16:42, hash: 9e6b6f31b8c0
Worked: (newest version of Blender that worked as expected)

Short description of error
When the connection line between vertex pairs passes through a concave vertex of a polygon, it may produce undesirable results, see the screenshots below.

Exact steps for others to reproduce the error

  1. Create a mesh that contain a concave polygon.

  2. Select the start point and end point, see fig1.

note that the concave vertex must exactly fall on the connection line between two input points (with distance less than 0.0001m).

  1. perform Vertex/Connect Vertex Path or Vertex/Connect Vertex Pairs will generate unsatisfying results, for case1 see fig2:

  2. Undo the connection, just move the concave point in x axis by 0.0001m (the CONNECT_EPS defined in bmo_connect_pair.cc), another awkward result (case2) will be produced by performing connection again. The path is not even continuous, see fig3:

  3. in another similar example below, I move another point on the direction of connection line, this time, Blender gives the error message “Could not connect vertices”. This is case3, see fig4:

I also provide the .blend file here to reproduce these results.
I have written code to fix this bug, I'll make a pull request later.

For more detailed discussion of the cause and fix ideas, see this topic on Dev forum:
https://devtalk.blender.org/t/bug-report-and-proposed-fix-for-bmesh-operator-connect-vert-pairs-in-special-cases/31249?u=sayaka

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99 **Blender Version** Broken: version: 4.0.0 Alpha, branch: dev_connect_vert (modified), commit date: 2023-09-22 16:42, hash: `9e6b6f31b8c0` Worked: (newest version of Blender that worked as expected) **Short description of error** When the connection line between vertex pairs passes through a concave vertex of a polygon, it may produce undesirable results, see the screenshots below. **Exact steps for others to reproduce the error** 1. Create a mesh that contain a concave polygon. 2. Select the start point and end point, see fig1. note that the concave vertex must exactly fall on the connection line between two input points (with distance less than 0.0001m). 3. perform Vertex/Connect Vertex Path or Vertex/Connect Vertex Pairs will generate unsatisfying results, for case1 see fig2: 4. Undo the connection, just move the concave point in x axis by 0.0001m (the CONNECT_EPS defined in bmo_connect_pair.cc), another awkward result (case2) will be produced by performing connection again. The path is not even continuous, see fig3: 5. in another similar example below, I move another point on the direction of connection line, this time, Blender gives the error message “Could not connect vertices”. This is case3, see fig4: I also provide the .blend file here to reproduce these results. I have written code to fix this bug, I'll make a pull request later. For more detailed discussion of the cause and fix ideas, see this topic on Dev forum: [https://devtalk.blender.org/t/bug-report-and-proposed-fix-for-bmesh-operator-connect-vert-pairs-in-special-cases/31249?u=sayaka](url)
Peng Yan added the
Severity
Normal
Status
Needs Triage
Type
Report
labels 2023-09-23 13:55:49 +02:00
Member

Confirming this

Confirming this
YimingWu added
Module
Modeling
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-09-25 05:27:19 +02:00
Bart van der Braak added
Type
Bug
and removed
Type
Report
labels 2024-08-14 13:08:25 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
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
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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#112772
No description provided.