Triager-bot/test
1
0
Code Issues 41 Packages Projects Wiki

The Bevel Modifier cannot find the properties when applying bevels using weights. #131

New Issue
Open
opened 2026-04-12 15:15:36 +00:00 by Triager-bot · 7 comments
Triager-bot commented 2026-04-12 15:15:36 +00:00
Owner
Copy Link

Original bug report: https://projects.blender.org/blender/blender/issues/157219

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 5070 Ti NVIDIA Corporation NVIDIA 576.88 Vulkan Backend

Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash: adfe2921d5f3
Worked: version: 5.0.1

Short description of error
In version 5.1.0, when using the bevel modifier, the properties cannot be found if beveling with weights; however, in version 5.0.1, the properties are available.

Exact steps for others to reproduce the error

  1. Add a basic mesh
  2. Add a bevel modifier to it
  3. Change the bevel modifier's limit method to Weight
  4. In the Edge Weight panel, modify the attributes being used (you'll notice there are no attributes listed)
Original bug report: https://projects.blender.org/blender/blender/issues/157219 **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 5070 Ti NVIDIA Corporation NVIDIA 576.88 Vulkan Backend **Blender Version** Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash: `adfe2921d5f3` Worked: version: 5.0.1 **Short description of error** In version 5.1.0, when using the bevel modifier, the properties cannot be found if beveling with weights; however, in version 5.0.1, the properties are available. **Exact steps for others to reproduce the error** 1. Add a basic mesh 2. Add a bevel modifier to it 3. Change the bevel modifier's limit method to Weight 4. In the Edge Weight panel, modify the attributes being used (you'll notice there are no attributes listed)
5.0.1.png
46 KiB
5.1.0.png
44 KiB
5.0.1.png 5.1.0.png
Triager-bot added the Status/Needs review label 2026-04-12 15:15:36 +00:00
Triager-bot commented 2026-04-12 15:15:47 +00:00
Author
Owner
Copy Link

Report is clear

LLM Reasoning

Got it, let's see. The bug report has a title, body with system info (but we ignore that), Blender versions, short description, and steps to reproduce. The steps are clear: add mesh, add bevel modifier, change limit method to Weight, check Edge Weight panel for attributes. The description says in 5.1.0 properties aren't found when using weights, but in 5.0.1 they are. So the steps and description make sense. Is it clear? Yes, because the steps are specific and the issue is described. So the answer is Yes.

JSON Data

{
"llm_judgement": true,
"processing_time": 7.597607999999999
}

<!-- ID: CLARITY_CHECK --> ### Report is clear <details> <summary>LLM Reasoning</summary> Got it, let's see. The bug report has a title, body with system info (but we ignore that), Blender versions, short description, and steps to reproduce. The steps are clear: add mesh, add bevel modifier, change limit method to Weight, check Edge Weight panel for attributes. The description says in 5.1.0 properties aren't found when using weights, but in 5.0.1 they are. So the steps and description make sense. Is it clear? Yes, because the steps are specific and the issue is described. So the answer is Yes. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 7.597607999999999 } </details>
Triager-bot commented 2026-04-12 15:15:59 +00:00
Author
Owner
Copy Link

Report is specific

LLM Reasoning

Got it, let's analyze this bug report. The title is "The Bevel Modifier cannot find the properties when applying bevels using weights." The body describes a specific issue: in Blender 5.1.0, when using the bevel modifier with weight limit method, the properties aren't found (no attributes listed), but it worked in 5.0.1. The steps to reproduce are detailed (adding mesh, adding bevel modifier, changing limit method to Weight, checking Edge Weight panel).

So this is a specific issue because it's about a particular feature (Bevel Modifier with weights) not working as expected in a specific version, with clear reproduction steps. It's not vague like "crashing while rendering"—it's focused on the Bevel Modifier's weight properties. So the answer should be 'Specific'.

JSON Data

{
"llm_judgement": true,
"processing_time": 10.098965
}

<!-- ID: SPECIFIC_REPORT --> ### Report is specific <details> <summary>LLM Reasoning</summary> Got it, let's analyze this bug report. The title is "The Bevel Modifier cannot find the properties when applying bevels using weights." The body describes a specific issue: in Blender 5.1.0, when using the bevel modifier with weight limit method, the properties aren't found (no attributes listed), but it worked in 5.0.1. The steps to reproduce are detailed (adding mesh, adding bevel modifier, changing limit method to Weight, checking Edge Weight panel). So this is a specific issue because it's about a particular feature (Bevel Modifier with weights) not working as expected in a specific version, with clear reproduction steps. It's not vague like "crashing while rendering"—it's focused on the Bevel Modifier's weight properties. So the answer should be 'Specific'. </details> <details> <summary>JSON Data</summary> { "llm_judgement": true, "processing_time": 10.098965 } </details>
Triager-bot commented 2026-04-12 15:16:12 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Bevel Weights are lost after Subsurf

https://projects.blender.org/blender/blender/issues/17329

Resolution: Fixed
Category: Mesh Modeling

%%%It seems that using the Bevel modifier 'limit by bevel weight' doesn't work if there's a subsurf modifier higher up in the stack. Presumably the subsurf isn't retaining/passing on the bevel weight information. I've attached a test file, you can toggle the subsurf on and off to see the bevel on the edge take effect.

%%%

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the description and steps for each.

Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (compared to 5.0.1). The steps are adding a mesh, bevel modifier, setting limit method to Weight, then checking Edge Weight panel attributes—no attributes listed.

Bug report 2 is about Bevel Weights being lost after Subsurf. The issue is that the subsurf modifier higher up in the stack makes the bevel weight not work, and toggling subsurf shows the effect.

So the first is about missing properties when using weights (maybe a UI or data issue), the second is about weights being lost due to another modifier (subsurf) affecting them. These are different issues: one is about availability of properties in the bevel modifier's weight settings, the other is about weights not persisting after subsurf. So they're not duplicates.

JSON Data

{
"llm_judgement": false,
"processing_time": 12.17876,
"duplicate_report_number": "17329"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Bevel Weights are lost after Subsurf</summary> https://projects.blender.org/blender/blender/issues/17329 **Resolution**: Fixed **Category**: Mesh Modeling %%%It seems that using the Bevel modifier 'limit by bevel weight' doesn't work if there's a subsurf modifier higher up in the stack. Presumably the subsurf isn't retaining/passing on the bevel weight information. I've attached a test file, you can toggle the subsurf on and off to see the bevel on the edge take effect. %%% </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the description and steps for each. Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (compared to 5.0.1). The steps are adding a mesh, bevel modifier, setting limit method to Weight, then checking Edge Weight panel attributes—no attributes listed. Bug report 2 is about Bevel Weights being lost after Subsurf. The issue is that the subsurf modifier higher up in the stack makes the bevel weight not work, and toggling subsurf shows the effect. So the first is about missing properties when using weights (maybe a UI or data issue), the second is about weights being lost due to another modifier (subsurf) affecting them. These are different issues: one is about availability of properties in the bevel modifier's weight settings, the other is about weights not persisting after subsurf. So they're not duplicates. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.17876, "duplicate_report_number": "17329" } </details>
Triager-bot commented 2026-04-12 15:16:27 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Bevel modifier bug

https://projects.blender.org/blender/blender/issues/114860

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01

Blender Version
Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: 878f71061b8e
Worked: (newest version of Blender that worked as expected)

Short description of error
Complex Solidify + Bevel working incorrectly with marked with bevel - ignoring which vertexes have wbevel weight 1.0 or 0.0, making bevel on all vertexes

Exact steps for others to reproduce the error

  • Open attached .blend file or
    • Create plane
    • Add some subdivisions to have more vertecies on the mesh
    • Mark outer edges with bevel weight 1.0
    • Mark corner vertecies with bevel weight 1.0
    • Add Solidify modifier to mesh, change from Simple to Comlex Type
    • Add Bevel modifier. Limit method to Weight

In 3.6 you are getting bevel only on marked edges+marked vertecies
In 4.0 making bevel on all vertecies which are in the marked edges with bevel weight

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the description and steps.

Bug report 1 is about the Bevel Modifier not finding properties when using weights (specifically, no attributes listed in Edge Weight panel). The steps involve adding a mesh, bevel modifier, changing limit method to Weight, then checking Edge Weight panel.

Bug report 2 is about Complex Solidify + Bevel working incorrectly with bevel weights—ignoring vertex weights and beveling all vertices. Steps include creating a plane, subdividing, marking edges/vertices with weight 1.0, adding Solidify (Complex), then Bevel (Weight limit). The issue here is the behavior of beveling based on weights not working as expected.

The core issues are different: one is about missing properties in the Edge Weight panel when using weights, the other is about incorrect bevel application ignoring weight settings. So they're not the same issue. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 14.033717000000001,
"duplicate_report_number": "114860"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Bevel modifier bug</summary> https://projects.blender.org/blender/blender/issues/114860 **System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4090/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 546.01 **Blender Version** Broken: version: 4.0.0, branch: blender-v4.0-release, commit date: 2023-11-13 17:26, hash: `878f71061b8e` Worked: (newest version of Blender that worked as expected) **Short description of error** Complex Solidify + Bevel working incorrectly with marked with bevel - ignoring which vertexes have wbevel weight 1.0 or 0.0, making bevel on all vertexes **Exact steps for others to reproduce the error** - Open attached .blend file or - Create plane - Add some subdivisions to have more vertecies on the mesh - Mark outer edges with bevel weight 1.0 - Mark corner vertecies with bevel weight 1.0 - Add Solidify modifier to mesh, change from Simple to Comlex Type - Add Bevel modifier. Limit method to Weight In 3.6 you are getting bevel only on marked edges+marked vertecies In 4.0 making bevel on all vertecies which are in the marked edges with bevel weight </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the description and steps. Bug report 1 is about the Bevel Modifier not finding properties when using weights (specifically, no attributes listed in Edge Weight panel). The steps involve adding a mesh, bevel modifier, changing limit method to Weight, then checking Edge Weight panel. Bug report 2 is about Complex Solidify + Bevel working incorrectly with bevel weights—ignoring vertex weights and beveling all vertices. Steps include creating a plane, subdividing, marking edges/vertices with weight 1.0, adding Solidify (Complex), then Bevel (Weight limit). The issue here is the behavior of beveling based on weights not working as expected. The core issues are different: one is about missing properties in the Edge Weight panel when using weights, the other is about incorrect bevel application ignoring weight settings. So they're not the same issue. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 14.033717000000001, "duplicate_report_number": "114860" } </details>
Triager-bot commented 2026-04-12 15:16:38 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Weight on Bevel modifier has no effect for edges with weight.

https://projects.blender.org/blender/blender/issues/30832

%%%Default scene, add bevel modifier to cube. Set modifier to weight.

Open the N properties panel and in edit mode at the top adjust bevel weight for one edge, or mean bevel weight for multiples edges which seems to have no effect on the bevel.

Linux 64bit r45431

Cheers <3

O

%%%

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps.

Bug report 1: The issue is that when using the Bevel Modifier with weight limit method, the properties (attributes) aren't found. Steps involve adding a mesh, bevel modifier, setting to Weight, then trying to modify attributes but none are listed.

Bug report 2: The issue is that weight on the Bevel modifier has no effect for edges with weight. Steps: add bevel to cube, set to weight, adjust edge bevel weight in N properties (edit mode) but it doesn't affect the bevel.

So, the first one is about missing attributes when using weight method, the second is about weights not affecting the bevel. Different problems. So they aren't duplicates. Answer: No.

JSON Data

{
"llm_judgement": false,
"processing_time": 10.408116,
"duplicate_report_number": "30832"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Weight on Bevel modifier has no effect for edges with weight.</summary> https://projects.blender.org/blender/blender/issues/30832 %%%Default scene, add bevel modifier to cube. Set modifier to weight. Open the N properties panel and in edit mode at the top adjust bevel weight for one edge, or mean bevel weight for multiples edges which seems to have no effect on the bevel. Linux 64bit r45431 Cheers <3 O %%% </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps. Bug report 1: The issue is that when using the Bevel Modifier with weight limit method, the properties (attributes) aren't found. Steps involve adding a mesh, bevel modifier, setting to Weight, then trying to modify attributes but none are listed. Bug report 2: The issue is that weight on the Bevel modifier has no effect for edges with weight. Steps: add bevel to cube, set to weight, adjust edge bevel weight in N properties (edit mode) but it doesn't affect the bevel. So, the first one is about missing attributes when using weight method, the second is about weights not affecting the bevel. Different problems. So they aren't duplicates. Answer: No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 10.408116, "duplicate_report_number": "30832" } </details>
Triager-bot commented 2026-04-12 15:16:51 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

"Set Attribute" operator allows to set value greater than the hard max

https://projects.blender.org/blender/blender/issues/152012

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4080 SUPER NVIDIA Corporation NVIDIA 581.42 Vulkan Backend

Blender Version
Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: a3db93c5b259
Worked: (newest version of Blender that worked as expected)

Short description of error
With set attribute operator, it is possible to set value >1 of bevel weight, mean crease, etc.

Exact steps for others to reproduce the error

  • Switch to Edit mode
  • From N-panel tweak bevel weight operator (cannot set beyond 1)
  • Mesh -> Set Attribute (possible to set > 1)

Using the shortcut allow for Set Attribute values to be greater than 1 on attributes that's normally not possible (bevel_weight_edge, crease_edge)

LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps.

Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (steps: add mesh, bevel modifier, set limit to weight, check edge weight panel has no attributes).

Bug report 2 is about the "Set Attribute" operator allowing values greater than 1 for bevel weight/crease, which isn't supposed to happen (steps: edit mode, tweak bevel weight in N-panel, use Set Attribute to set >1).

The issues are different: one is about missing properties in the bevel modifier's weight panel, the other is about setting attribute values beyond their max. So they're not the same issue. Therefore, the answer is No.

JSON Data

{
"llm_judgement": false,
"processing_time": 12.118929,
"duplicate_report_number": "152012"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>"Set Attribute" operator allows to set value greater than the hard max</summary> https://projects.blender.org/blender/blender/issues/152012 **System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4080 SUPER NVIDIA Corporation NVIDIA 581.42 Vulkan Backend **Blender Version** Broken: version: 5.0.1, branch: blender-v5.0-release, commit date: 2025-12-15 16:36, hash: `a3db93c5b259` Worked: (newest version of Blender that worked as expected) **Short description of error** With set attribute operator, it is possible to set value >1 of bevel weight, mean crease, etc. **Exact steps for others to reproduce the error** - Switch to Edit mode - From N-panel tweak bevel weight operator (cannot set beyond 1) - Mesh -> Set Attribute (possible to set > 1) Using the shortcut allow for Set Attribute values to be greater than 1 on attributes that's normally not possible (bevel_weight_edge, crease_edge) </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps. Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (steps: add mesh, bevel modifier, set limit to weight, check edge weight panel has no attributes). Bug report 2 is about the "Set Attribute" operator allowing values greater than 1 for bevel weight/crease, which isn't supposed to happen (steps: edit mode, tweak bevel weight in N-panel, use Set Attribute to set >1). The issues are different: one is about missing properties in the bevel modifier's weight panel, the other is about setting attribute values beyond their max. So they're not the same issue. Therefore, the answer is No. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.118929, "duplicate_report_number": "152012" } </details>
Triager-bot commented 2026-04-12 15:17:05 +00:00
Author
Owner
Copy Link

Report flagged as NOT a duplicate by LLM

Reading+Writing edge bevel weights with python api only working correctly on last element

https://projects.blender.org/blender/blender/issues/102404

System Information
Operating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07

Blender Version
Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-10 11:41, hash: bc672e76eb
Worked: 2 days ago, hash 1d71f82033f1

Caused by [0a7308a0f1}

Short description of error
image.png
Reading or writing the edge.bevel_weight only seems to work for the last edge in the mesh. Others are read/set as 0.

Exact steps for others to reproduce the error

File (run script):bevel_weight_transfer.blend

Following code should set the bevel weight of all edges in ob to 1. This only works for the last edge, all others are set to 0.

  for e in ob.data.edges:
      print(e.bevel_weight)
      e.bevel_weight = 1
LLM Reasoning

Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.

Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (vs 5.0.1). The steps involve adding a mesh, bevel modifier, changing limit method to Weight, and noticing no attributes in Edge Weight panel.

Bug report 2 is about Python API for edge.bevel_weight only working on the last edge—others are set to 0. Steps include running a script that sets bevel weights, but only the last edge works.

These are different issues: one is UI/Modifier properties not showing (report 1), the other is Python API behavior with edge bevel weights (report 2). So they aren't duplicates.

JSON Data

{
"llm_judgement": false,
"processing_time": 12.596976,
"duplicate_report_number": "102404"
}

<!-- ID: CHECK_DUPLICATE --> ### Report flagged as NOT a duplicate by LLM <details> <summary>Reading+Writing edge bevel weights with python api only working correctly on last element</summary> https://projects.blender.org/blender/blender/issues/102404 **System Information** Operating system: Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 64 Bits Graphics card: Quadro RTX 6000/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 515.48.07 **Blender Version** Broken: version: 3.5.0 Alpha, branch: master, commit date: 2022-11-10 11:41, hash: `bc672e76eb` Worked: 2 days ago, hash `1d71f82033f1` Caused by [0a7308a0f1} **Short description of error** ![image.png](https://archive.blender.org/developer/F13884931/image.png) Reading or writing the `edge.bevel_weight` only seems to work for the last edge in the mesh. Others are read/set as 0. **Exact steps for others to reproduce the error** File (run script):[bevel_weight_transfer.blend](https://archive.blender.org/developer/F13884944/bevel_weight_transfer.blend) Following code should set the bevel weight of all edges in `ob` to 1. This only works for the last edge, all others are set to 0. ``` for e in ob.data.edges: print(e.bevel_weight) e.bevel_weight = 1 ``` </details> <details> <summary>LLM Reasoning</summary> Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce. Bug report 1 is about the Bevel Modifier not finding properties when using weights in version 5.1.0 (vs 5.0.1). The steps involve adding a mesh, bevel modifier, changing limit method to Weight, and noticing no attributes in Edge Weight panel. Bug report 2 is about Python API for edge.bevel_weight only working on the last edge—others are set to 0. Steps include running a script that sets bevel weights, but only the last edge works. These are different issues: one is UI/Modifier properties not showing (report 1), the other is Python API behavior with edge bevel weights (report 2). So they aren't duplicates. </details> <details> <summary>JSON Data</summary> { "llm_judgement": false, "processing_time": 12.596976, "duplicate_report_number": "102404" } </details>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Status/Needs review
Trager-Bot Will Send Comment
No Label Status/Needs review
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Triager-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Triager-bot/test#131
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?