Geometry Nodes: Mesh to Volume and/or Volume to Mesh causing non-deterministic behaviour #115578
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#115578
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 960/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.23
Blender Version
Broken: version: 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-16 16:40, hash:
d0dd92834a08as well as the daily build: version: 4.1.0 Alpha, branch: main, commit date: 2023-11-28 21:58, hash:
09caf5969010Worked: Never.
Short description of error
Starting with a basemesh that gets "remeshed" in a Geometry nodes Modifier with 'Mesh to Volume' and 'Volume to Mesh', subsequent geometry nodes operations that are random are non-deterministic. This seems to be, to a certain degree, dependent on the complexity of the basemesh.
Exact steps for others to reproduce the error
open the provided file test.blend and toggle the viewer node in the geometry node tree "random" that is already open.
According to my experimentations, any forced recalculation of the geometry nodes should work to expose the non-determinism. In the provided file, a 'Mesh to Points' Node with a random boolean as the Selection is used to illustrate the bug. According to my experimentations, any random value evaluated over the remeshed geometry should exhibit the non-deterministic behaviour. This also goes for 'Distribute Points on Faces'.
This nodes are not exists in this blender version at all.
I think we had a similar report in the past, but I can't find it right now. I'm quite sure the problem is in the Volume to Mesh node. Unfortunately, the code uses OpenVDB internally.
I seems like OpenVDB tries to make this deterministic, so we have to see if there is anything we can do about it on our side or if it's a just a bug in OpenVDB.
This sounds related, but the version we use should already include that fix.