bevel select adjacent faces after operation #74189

Closed
opened 2020-02-25 05:16:32 +01:00 by Massimiliano Puliero · 11 comments

System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7
Worked: blender 2.81

Short description of error
bevel select adjacent faces after the operation.

Exact steps for others to reproduce the error
Open the attached file, select all the edges and perform a bevel operation.
Also please take a look at the animated gif.

Thank you

sample.blend
281.gif
282.gif

**System Information** Operating system: Windows-10-10.0.17763-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.86 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` Worked: blender 2.81 **Short description of error** bevel select adjacent faces after the operation. **Exact steps for others to reproduce the error** Open the attached file, select all the edges and perform a bevel operation. Also please take a look at the animated gif. Thank you [sample.blend](https://archive.blender.org/developer/F8368419/sample.blend) ![281.gif](https://archive.blender.org/developer/F8368420/281.gif) ![282.gif](https://archive.blender.org/developer/F8368421/282.gif)

Added subscriber: @MassimilianoPuliero

Added subscriber: @MassimilianoPuliero
Member

Added subscriber: @ankitm

Added subscriber: @ankitm
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

could you add some details about what the bug is ? What is the expected behaviour?

could you add some details about what the bug is ? What is the expected behaviour?

the expected behavior is the one we have in 2.81 and before.

please see the attached gif.

the expected behavior is the one we have in 2.81 and before. please see the attached gif.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Philipp Oeser self-assigned this 2020-02-25 11:11:14 +01:00
Member

Yes, true, blender now flushes selection (from edges to faces etc) immediately -- and since all face edges are selected, the face will be as well....
Please have a look at the discussion in #73771 (New Bevel: Scaling Vertices, Edges by their individual origins has different behavior if bevel regions are direct neighbors (selection flushing to edges immediately?)).

This might have disadvantages in certain scenarios (this one in particular - since it is not so obvious how to preserve new geo selection), BUT there is always a workaround:
In this case you can perform the operation with same results in face select mode (instead of edge select mode) --> you are left with the nice selection you were expecting, no? (blender is not flushing faces to adjacent faces)

Afraid we have to close this since this is working as intended...
(feel free though to comment again if issues persist...)

Yes, true, blender now flushes selection (from edges to faces etc) immediately -- and since all face edges are selected, the face will be as well.... Please have a look at the discussion in #73771 (New Bevel: Scaling Vertices, Edges by their individual origins has different behavior if bevel regions are direct neighbors (selection flushing to edges immediately?)). This might have disadvantages in certain scenarios (this one in particular - since it is not so obvious how to preserve new geo selection), BUT there is always a workaround: In this case you can perform the operation with same results in face select mode (instead of edge select mode) --> you are left with the nice selection you were expecting, no? (blender is not flushing faces to adjacent faces) Afraid we have to close this since this is working as intended... (feel free though to comment again if issues persist...)

hi, thanks for the reply.
I still think this is a regression, from an artist standpoint there is no real benefit to have this new behavior, but I can see a number of cases where this behavior can cause problems:

Here a clear case where using faces is not helpful:

bevel.gif

thank you

hi, thanks for the reply. I still think this is a regression, from an artist standpoint there is no real benefit to have this new behavior, but I can see a number of cases where this behavior can cause problems: Here a clear case where using faces is not helpful: ![bevel.gif](https://archive.blender.org/developer/F8370560/bevel.gif) thank you
Member

You can still work around it by using edge and face mode?
image.png
image.png
(dont get me wrong, I also think it has disadvantages, but to me it looks like you can still get what you want?)

You can still work around it by using edge **and** face mode? ![image.png](https://archive.blender.org/developer/F8373166/image.png) ![image.png](https://archive.blender.org/developer/F8373169/image.png) (dont get me wrong, I also think it has disadvantages, but to me it looks like you can still get what you want?)

sure, but still, no advantages at all by this new behavior.

sure, but still, no advantages at all by this new behavior.
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#74189
No description provided.