Bridge Edge Loops operation has inconsistent results #75181

Closed
opened 3 years ago by jachymmichal · 14 comments

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50

Blender Version
Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-28 20:40, hash: a24f52c51c
Worked: N/A

Short description of error
Bridge Edge Loops operation result is different when mesh is duplicated in Edit Mode vs. duplicated in Object Mode and joined into one object.

Exact steps for others to reproduce the error

Works in default startup file.

  • Add plane through Add > Mesh > Plane
  • In Edit Mode duplicate it and move the duplicate a bit sideways (along X or Y axis)
  • Select All vertices and go Edge > Bridge Edge Loopsto connect them with an arch. Set Number of cuts to 2+.
  • The resulting arch is weirdly 'cut' in the middle, introduces non-manifold faces and flipped normals.

No such issues occur when the original plane is duplicated in Object Modeand joined into one object. Only direct duplicating in Edit Mode causes this behavior.

Duplicated in Edit Mode. Gives weird results.
{F8434956, size=full}

Duplicated in Object mode and joined. Creates a nice arch.
{F8434969, size=full}

Thanks a lot for looking into this problem.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.50 **Blender Version** Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-03-28 20:40, hash: `a24f52c51c` Worked: N/A **Short description of error** *Bridge Edge Loops* operation result is different when mesh is duplicated in *Edit Mode* vs. duplicated in *Object Mode* and joined into one object. **Exact steps for others to reproduce the error** Works in default startup file. - Add plane through *Add > Mesh > Plane* - In *Edit Mode* duplicate it and move the duplicate a bit sideways (along X or Y axis) - Select All vertices and go *Edge > Bridge Edge Loops*to connect them with an arch. Set *Number of cuts* to 2+. - The resulting arch is weirdly 'cut' in the middle, introduces non-manifold faces and flipped normals. No such issues occur when the original plane is duplicated in *Object Mode*and joined into one object. Only direct duplicating in *Edit Mode* causes this behavior. *Duplicated in Edit Mode. Gives weird results.* {[F8434956](https://archive.blender.org/developer/F8434956/bridge_loops_edit_mode.gif), size=full} *Duplicated in Object mode and joined. Creates a nice arch.* {[F8434969](https://archive.blender.org/developer/F8434969/bridge_loops_object_mode.gif), size=full} Thanks a lot for looking into this problem.
Poster

Added subscriber: @jachymmichal

Added subscriber: @jachymmichal
Collaborator

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Collaborator

The Bridge Edge Loop operator does not consider the average Normal of Faces. It just reads the edges loops.
So it makes no difference whether the edge loop has a face in it or if the normal is pointed to one side or the other of the face.
This is something that could improve, but it is not so simple to implement.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

The Bridge Edge Loop operator does not consider the average Normal of Faces. It just reads the edges loops. So it makes no difference whether the edge loop has a face in it or if the normal is pointed to one side or the other of the face. This is something that could improve, but it is not so simple to implement. Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Collaborator

Changed status from 'Needs Triage' to: 'Archived'

Changed status from 'Needs Triage' to: 'Archived'
mano-wii closed this issue 3 years ago
mano-wii self-assigned this 3 years ago
rjg commented 3 years ago
Collaborator

Added subscriber: @rjg

Added subscriber: @rjg
rjg commented 3 years ago
Collaborator

Removed subscriber: @rjg

Removed subscriber: @rjg
Poster

@mano-wii Thanks for you reply, but perhaps I didn't explain it well enough :).

Those flipped normals aren't the main issue, they're just one of the consequent problems.
The main issue is deformed geometry, and that happens no matter if the loops has a face or not, or if the normal is pointed up/down.

Please consider reopening the task, this doesn't look like intended behavior.

@mano-wii Thanks for you reply, but perhaps I didn't explain it well enough :). Those flipped normals aren't the main issue, they're just one of the consequent problems. The main issue is *deformed geometry*, and that happens no matter if the loops has a face or not, or if the normal is pointed up/down. Please consider reopening the task, this doesn't look like intended behavior.
Collaborator

Changed status from 'Archived' to: 'Needs Triage'

Changed status from 'Archived' to: 'Needs Triage'
mano-wii reopened this issue 3 years ago
Collaborator

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Collaborator

It is indeed a bug.
A similar problem has been reported before and 304501193b was supposed to have fixed it.

It is indeed a bug. A similar problem has been reported before and 304501193b was supposed to have fixed it.
Owner

Closed as duplicate of #79375

Closed as duplicate of #79375
ideasman42 closed this issue 2 years ago

Added subscriber: @litinskiyA

Added subscriber: @litinskiyA

This comment was removed by @litinskiyA

*This comment was removed by @litinskiyA*

Hi, steel reproduced in blender 2.93 Beta, 2.92, 2.93, 2.93.1 Release Candidate

Hi, steel reproduced in blender 2.93 Beta, 2.92, 2.93, 2.93.1 Release Candidate
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Overrides
Interest/Performance
Interest/Pipeline, Assets & I/O
Interest/Translations
Interest/Undo
Interest/USD
Interest/Video Sequencer
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/Nodes & Physics
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Performance
legacy project/Physics
legacy project/Platforms, Builds, Tests & Devices
legacy project/Pose Library Basics
legacy project/Python API
legacy project/Render & Cycles
legacy project/Render Pipeline
legacy project/Retrospective
legacy project/Sculpt, Paint & Texture
legacy project/Text Editor
legacy project/Tracker Curfew
legacy project/Triaging
legacy project/User Interface
legacy project/UV Editing
legacy project/VFX & Video
legacy project/Virtual Reality
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#75181
Loading…
There is no content yet.