Fillet curve node's limit radius mode is too often problematic #99232

Closed
opened 2022-06-28 11:05:59 +02:00 by Zhen Dai · 11 comments

System Information
Operating system: Windows-10-10.0.18363-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68

Blender Version
Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: e05e1e3691
Worked: N/A

Short description of error

  • One problem with Fillet Curve node is its Limit Radius mode, which is very prone to create strange curves when users don't make use of the count field.
  • The count field however is only available in Poly mode, making the Bezier mode basically unusable for any large radius.
  • I argue Fillet Curve should ignore curve point with 180 curve angle by default.

Screenshot 2022-06-28 165629.jpg

Screenshot 2022-06-28 165624.jpg

Exact steps for others to reproduce the error

  • Download attached blend file;
  • Notice the fillet curve is probably not what the user want, with or without limit radius mode;
  • The only solution, is to put fillet curve under poly mode, and then use count field to filter points where curve angle isn't 180 (with dot product; this is do-able in GN but non-trivial for new users if they want to handle cyclic + multi splines).

fillet-behaviour.blend

**System Information** Operating system: Windows-10-10.0.18363-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 471.68 **Blender Version** Broken: version: 3.2.0, branch: master, commit date: 2022-06-08 10:22, hash: `e05e1e3691` Worked: N/A **Short description of error** - One problem with Fillet Curve node is its Limit Radius mode, which is very prone to create strange curves when users don't make use of the count field. - The count field however is only available in Poly mode, making the Bezier mode basically unusable for any large radius. - I argue Fillet Curve should ignore curve point with 180 curve angle by default. ![Screenshot 2022-06-28 165629.jpg](https://archive.blender.org/developer/F13234195/Screenshot_2022-06-28_165629.jpg) ![Screenshot 2022-06-28 165624.jpg](https://archive.blender.org/developer/F13234194/Screenshot_2022-06-28_165624.jpg) **Exact steps for others to reproduce the error** - Download attached blend file; - Notice the fillet curve is probably not what the user want, with or without limit radius mode; - The only solution, is to put fillet curve under poly mode, and then use count field to filter points where curve angle isn't 180 (with dot product; this is do-able in GN but non-trivial for new users if they want to handle cyclic + multi splines). [fillet-behaviour.blend](https://archive.blender.org/developer/F13234189/fillet-behaviour.blend)
Author

Added subscriber: @Zhen-Dai

Added subscriber: @Zhen-Dai
Author

Poly mode issue might be easier to overcome for users, if curvature node is merged: https://developer.blender.org/D12550

But Bezier mode would still be unusable.

Poly mode issue might be easier to overcome for users, if curvature node is merged: https://developer.blender.org/D12550 But Bezier mode would still be unusable.
Author

just to show what i want by default (already do-able in poly mode).

Screenshot 2022-06-28 190600.jpg

just to show what i want by default (already do-able in poly mode). ![Screenshot 2022-06-28 190600.jpg](https://archive.blender.org/developer/F13234423/Screenshot_2022-06-28_190600.jpg)

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

I can confirm the weirdness of the Fillet Curve when the curve makes some angles, but it is possible that this is more of a limitation of the algorithm than an actual bug.

I can confirm the weirdness of the Fillet Curve when the curve makes some angles, but it is possible that this is more of a limitation of the algorithm than an actual bug.
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Seems to be fixed in latest master (likely due to 2551cf9087).
Can you confirm that?

Seems to be fixed in latest master (likely due to 2551cf9087). Can you confirm that?
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Hans Goudey self-assigned this 2022-07-27 19:57:40 +02:00
Member

The bug part of this report is fixed by default. For the others I'm not quite sure.

There is no "count" option on Bezier mode because it's easy to make curves with a crazy amount of evaluated points. But you're right that it doesn't work as well for very large curves, at least not until we can choose a segment resolution (the subdivide node might help?)
For ignoring points between parallel segments, I agree it would be helpful, but maybe a good first step would be adding a point selection input to the node.
The node could also merge points that meet because of the limit radius option.

I made two TODO tasks: #100032 and #100031

The bug part of this report is fixed by default. For the others I'm not quite sure. There is no "count" option on Bezier mode because it's easy to make curves with a crazy amount of evaluated points. But you're right that it doesn't work as well for very large curves, at least not until we can choose a segment resolution (the subdivide node might help?) For ignoring points between parallel segments, I agree it would be helpful, but maybe a good first step would be adding a point selection input to the node. The node could also merge points that meet because of the limit radius option. I made two TODO tasks: #100032 and #100031
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
4 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#99232
No description provided.