Percent even bevel width type for the bevel modifier - basic design suggestion #81931

Closed
opened 2020-10-21 20:00:01 +02:00 by Mr Chocolate Bar · 11 comments

In short, currently theres no width type for the bevel modifier that gives you a bevel that is even on both sides of the original beveled edge but that lets you decide the bevel amount based on the percentual distance of one of the nearby edges. Hence, I think this is something worth getting looked into. Please see the below image or the attached pdf for more detailed explanation of how I think it should work as well as some motivation for why this should be implemented.

Thanks for reading :)

Percent even bevel width type suggestion.jpeg

Percent even bevel width type for the bevel modifier suggestion.pdf

In short, currently theres no width type for the bevel modifier that gives you a bevel that is even on both sides of the original beveled edge but that lets you decide the bevel amount based on the percentual distance of one of the nearby edges. Hence, I think this is something worth getting looked into. Please see the below image or the attached pdf for more detailed explanation of how I think it should work as well as some motivation for why this should be implemented. Thanks for reading :) ![Percent even bevel width type suggestion.jpeg](https://archive.blender.org/developer/F9028905/Percent_even_bevel_width_type_suggestion.jpeg) [Percent even bevel width type for the bevel modifier suggestion.pdf](https://archive.blender.org/developer/F9028887/Percent_even_bevel_width_type_for_the_bevel_modifier_suggestion.pdf)

Added subscriber: @Olliver

Added subscriber: @Olliver
Mr Chocolate Bar changed title from Percent even bevel width type suggestion to Percent even bevel width type for the bevel modifier - basic design suggestion 2020-10-21 20:18:04 +02:00
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

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

Changed status from 'Needs Triage' to: 'Archived'
Hans Goudey self-assigned this 2020-10-21 20:36:16 +02:00
Member

This sort of detailed feature request really belongs on https://blender.community/c/rightclickselect/, not here. Anyway, the policy is not to allow feature requests on the bug tracker.

It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though.

This sort of detailed feature request really belongs on https://blender.community/c/rightclickselect/, not here. Anyway, the policy is not to allow feature requests on the bug tracker. It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though.

In #81931#1038784, @HooglyBoogly wrote:
This sort of detailed feature request really belongs on https://blender.community/c/rightclickselect/, not here. Anyway, the policy is not to allow feature requests on the bug tracker.

It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though.

To me this pretty much seem like a complete design. Ideas coming from the developers dont exactly first post there stuff on rightclickselect, they are first posted as designs - here.

> In #81931#1038784, @HooglyBoogly wrote: > This sort of detailed feature request really belongs on https://blender.community/c/rightclickselect/, not here. Anyway, the policy is not to allow feature requests on the bug tracker. > > It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though. To me this pretty much seem like a complete design. Ideas coming from the developers dont exactly first post there stuff on rightclickselect, they are first posted as designs - here.

In #81931#1038784, @HooglyBoogly wrote:
It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though.

Yes well there are several issues with the bevel modifier currently, one being that the clamp causes all bevels to thrink if you have a bevel go above the threshold, another being that the clamp stops bevels far too soon in some situations (So you cant utelize the whole edge because of the clamp stopping).

Another is that for all edge width types except the current percent doesnt support variable fillets (aka fillets/bevels that change in width between the sweep edges).

Another is that you cant use bevel weights for high precision control due to the float decimal limit for bevel weights while working on very large ranges. Like if you want one edge to be beveled with a width of around X cm and another with a width of around 100x you will need to make the bevel weight for that smaller width edge 0.01 and then you are getting very close (too close in some situations) to the amount of decimals read by the bevel modifier to get a decent amount of control of the width.

So ofc, the Blender team could take the time to fix all those issues. But instead I think its better if they keep there focus on making the long term goals and pushing out other stuff that matter more, but instead both simply the workflow and fix several issues by making another width type based on the percent width type which has its benefits, but that the bevel wont get "stretched" like it does by the current perecnt width type.

Because the current "percent" width type has non of the issues described above and is the only width type that doesnt (Thanks to that it doesnt need clamp and supports variable fillets), but its unusable to create "even"/unstretched bevels without adding support edges or something like that - which is then the hole I want the percent even bevel to fill in.

> In #81931#1038784, @HooglyBoogly wrote: > It's an interesting idea. Although I sort of feel the need for all these width options might be a sign of some other less visible design flaw in bevel. Not sure though. Yes well there are several issues with the bevel modifier currently, one being that the clamp causes all bevels to thrink if you have a bevel go above the threshold, another being that the clamp stops bevels far too soon in some situations (So you cant utelize the whole edge because of the clamp stopping). Another is that for all edge width types except the current percent doesnt support variable fillets (aka fillets/bevels that change in width between the sweep edges). Another is that you cant use bevel weights for high precision control due to the float decimal limit for bevel weights while working on very large ranges. Like if you want one edge to be beveled with a width of around X cm and another with a width of around 100x you will need to make the bevel weight for that smaller width edge 0.01 and then you are getting very close (too close in some situations) to the amount of decimals read by the bevel modifier to get a decent amount of control of the width. So ofc, the Blender team could take the time to fix all those issues. But instead I think its better if they keep there focus on making the long term goals and pushing out other stuff that matter more, but instead both simply the workflow and fix several issues by making another width type based on the percent width type which has its benefits, but that the bevel wont get "stretched" like it does by the current perecnt width type. Because the current "percent" width type has non of the issues described above and is the only width type that doesnt (Thanks to that it doesnt need clamp and supports variable fillets), but its unusable to create "even"/unstretched bevels without adding support edges or something like that - which is then the hole I want the percent even bevel to fill in.

Is there any other way that I can present the idea to the developers?

Ive posted many ideas on right click select in the past but, some of them gotten a lot of upvotes (Like 30-40) yet without any attention from the devs. Some of them being quite simple like this one, but that would make a big difference for the artist.

Is there any other way that I can present the idea to the developers? Ive posted many ideas on right click select in the past but, some of them gotten a lot of upvotes (Like 30-40) yet without any attention from the devs. Some of them being quite simple like this one, but that would make a big difference for the artist.

Added subscriber: @rjg

Added subscriber: @rjg

In #81931#1039652, @Olliver wrote:
To me this pretty much seem like a complete design. Ideas coming from the developers dont exactly first post there stuff on rightclickselect, they are first posted as designs - here.

If you would intend to implement this yourself, then this would be fine e.g. on DevTalk to discuss it with other developers. If you want other people to implement this for you, then it's a feature request and should be posted on right-click select.

In #81931#1039673, @Olliver wrote:
Is there any other way that I can present the idea to the developers?

Ive posted many ideas on right click select in the past but, some of them gotten a lot of upvotes (Like 30-40) yet without any attention from the devs. Some of them being quite simple like this one, but that would make a big difference for the artist.

Unfortunately we can't give certain users and their ideas special treatments. The rule that feature requests are off-topic for the bug tracker applies to everyone. If this is something that both the community and the developers consider important and there are developers available to implement this, then it will be picked up. We get far more improvement suggestions and feature requests every day than our developers could possibly implement. Hence it is to be expected that only a very small subset of ideas actually get integrated into Blender.

> In #81931#1039652, @Olliver wrote: > To me this pretty much seem like a complete design. Ideas coming from the developers dont exactly first post there stuff on rightclickselect, they are first posted as designs - here. If you would intend to implement this yourself, then this would be fine e.g. on DevTalk to discuss it with other developers. If you want other people to implement this for you, then it's a feature request and should be posted on right-click select. > In #81931#1039673, @Olliver wrote: > Is there any other way that I can present the idea to the developers? > > Ive posted many ideas on right click select in the past but, some of them gotten a lot of upvotes (Like 30-40) yet without any attention from the devs. Some of them being quite simple like this one, but that would make a big difference for the artist. Unfortunately we can't give certain users and their ideas special treatments. The rule that feature requests are off-topic for the bug tracker applies to everyone. If this is something that both the community and the developers consider important and there are developers available to implement this, then it will be picked up. We get far more improvement suggestions and feature requests every day than our developers could possibly implement. Hence it is to be expected that only a very small subset of ideas actually get integrated into Blender.

If you would intend to implement this yourself, then this would be fine e.g. on DevTalk to discuss it with other developers.

Aha alright.

Unfortunately we can't give certain users and their ideas special treatments. The rule that feature requests are off-topic for the bug tracker applies to everyone. If this is something that both the community and the developers consider important and there are developers available to implement this, then it will be picked up. We get far more improvement suggestions and feature requests every day than our developers could possibly implement. Hence it is to be expected that only a very small subset of ideas actually get integrated into Blender.

Thanks for the elaborate answer :) I understand the situation

> If you would intend to implement this yourself, then this would be fine e.g. on DevTalk to discuss it with other developers. Aha alright. > Unfortunately we can't give certain users and their ideas special treatments. The rule that feature requests are off-topic for the bug tracker applies to everyone. If this is something that both the community and the developers consider important and there are developers available to implement this, then it will be picked up. We get far more improvement suggestions and feature requests every day than our developers could possibly implement. Hence it is to be expected that only a very small subset of ideas actually get integrated into Blender. Thanks for the elaborate answer :) I understand the situation
Member

Even if it seems like not much happens to stuff on right click select, I expect that's more a function of developers' lack of time than lack of interest in what's posted there. Thanks for understanding.

Even if it seems like not much happens to stuff on right click select, I expect that's more a function of developers' lack of time than lack of interest in what's posted there. Thanks for understanding.
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#81931
No description provided.