Geometry Nodes: Add 'Fill Interior' option to Mesh to SDF Volume #107827

Closed
Erik Abrahamsson wants to merge 1 commits from erik85/blender:mesh-to-sdf-fill into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

Adds an input socket 'Fill Interior' to the Mesh to SDF Volume node.
Enabling it will make the interior band fill the entire interior of the mesh.

This is useful for example to be able to use the Threshold of
'Volume to Mesh' smoothly all the way down until the mesh disappears
without needing to also increase the exterior band width.

bild

Adds an input socket 'Fill Interior' to the Mesh to SDF Volume node. Enabling it will make the interior band fill the entire interior of the mesh. This is useful for example to be able to use the Threshold of 'Volume to Mesh' smoothly all the way down until the mesh disappears without needing to also increase the exterior band width. ![bild](/attachments/ebbd2e77-b1e9-4414-a33a-52dd0c818d19)
28 KiB
Erik Abrahamsson added the
Module
Nodes & Physics
label 2023-05-11 00:36:10 +02:00
Erik Abrahamsson added 1 commit 2023-05-11 00:36:16 +02:00
281c785189 Geometry Nodes: Add 'Fill Interior' option to Mesh to SDF Volume
Adds an input socket 'Fill Interior to the Mesh to SDF Volume node.
This will make the interior band fill the entire interior of the mesh.
This is useful for example to be able to use the Threshold of
'Volume to Mesh' smoothly all the way down until the mesh disappears
without needing to also increase the exterior band width.
Erik Abrahamsson requested review from Hans Goudey 2023-05-11 00:36:52 +02:00
Hans Goudey added this to the Nodes & Physics project 2023-05-11 03:01:05 +02:00
Hans Goudey reviewed 2023-05-11 03:12:47 +02:00
Hans Goudey left a comment
Member

Just to be sure, the change from meshToLevelSet to meshToSignedDistanceField doesn't affect behavior here (assuming the new option is turned off). Intuitively that makes sense, but there are so many overloads in the OpenVDB header that it's hard to be sure.

I guess this is one case where the "SDF Volume" naming is better than "level set" since it gives more flexibility.

I do wonder about how this compares to exposing the inner and outer band widths as separate inputs and just requiring users to write some large number here. How did you decide to go for this option instead?

Just to be sure, the change from `meshToLevelSet` to `meshToSignedDistanceField` doesn't affect behavior here (assuming the new option is turned off). Intuitively that makes sense, but there are so many overloads in the OpenVDB header that it's hard to be sure. I guess this is one case where the "SDF Volume" naming is better than "level set" since it gives more flexibility. I do wonder about how this compares to exposing the inner and outer band widths as separate inputs and just requiring users to write some large number here. How did you decide to go for this option instead?
@ -41,1 +41,4 @@
.max(10.0f);
b.add_input<decl::Bool>(N_("Fill Interior"))
.default_value(false)
.description(N_("Fill the entire interior of the mesh with distance values"));
Member

Maybe "with distance values" could be more clear as "with a gradient" or something

Maybe "with distance values" could be more clear as "with a gradient" or something
Author
Member

Just to be sure, the change from meshToLevelSet to meshToSignedDistanceField doesn't affect behavior here (assuming the new option is turned off). Intuitively that makes sense, but there are so many overloads in the OpenVDB header that it's hard to be sure.

As far as I can tell yes it's absolutely the same thing.

I do wonder about how this compares to exposing the inner and outer band widths as separate inputs and just requiring users to write some large number here. How did you decide to go for this option instead?

It feels a bit less intuitive to me that you need to enter a very large number to be sure that the whole gradient is filled. It could be an option to have both separate band widths and a fill option. I went for the simplest option because it feels like it's more common to need to fill the interior fully than set a specific number.

> Just to be sure, the change from `meshToLevelSet` to `meshToSignedDistanceField` doesn't affect behavior here (assuming the new option is turned off). Intuitively that makes sense, but there are so many overloads in the OpenVDB header that it's hard to be sure. As far as I can tell yes it's absolutely the same thing. > I do wonder about how this compares to exposing the inner and outer band widths as separate inputs and just requiring users to write some large number here. How did you decide to go for this option instead? It feels a bit less intuitive to me that you need to enter a very large number to be sure that the whole gradient is filled. It could be an option to have both separate band widths and a fill option. I went for the simplest option because it feels like it's more common to need to fill the interior fully than set a specific number.
Member

The node has been removed in the meantime with the transition to the grid socket design. Better to reconsider this when the node is back. I'll close the PR.

The node has been removed in the meantime with the transition to the grid socket design. Better to reconsider this when the node is back. I'll close the PR.
Hans Goudey closed this pull request 2024-01-30 04:43:08 +01:00

Pull request closed

Sign in to join this conversation.
No reviewers
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 Assignees
2 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#107827
No description provided.