Bridge Edge Loops operation has inconsistent results #75181

New Issue

Jachym Michal · 2020-03-29T11:57:33+02:00

Jachym Michal commented

2020-03-29 11:57:33 +02:00

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.

Jachym Michal commented

2020-03-29 11:57:33 +02:00

Added subscriber: @jachymmichal

Germano Cavalcante commented

2020-03-31 17:07:03 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-03-31 17:07:03 +02:00

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

Germano Cavalcante commented

2020-03-31 17:07:15 +02:00

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

Germano Cavalcante closed this issue

2020-03-31 17:07:15 +02:00

Germano Cavalcante self-assigned this 2020-03-31 17:07:15 +02:00

Robert Guetzkow commented

2020-03-31 17:12:47 +02:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-03-31 17:13:13 +02:00

Removed subscriber: @rjg

Jachym Michal commented

2020-05-13 14:48:10 +02:00

@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.

Germano Cavalcante commented

2020-05-13 15:49:00 +02:00

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

Germano Cavalcante reopened this issue

2020-05-13 15:49:00 +02:00

Germano Cavalcante commented

2020-05-13 16:25:09 +02:00

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