Simulation Nodes: Add Pass-through boolean input to Simulation Output Node #112082

Closed
opened 2023-09-07 14:39:15 +02:00 by Simon Thommes · 3 comments
Member

Behavior

If true pass through all simulation data from the previous to the next simulation step. Needs to be evaluated before the rest of the simulation step.

Use case

Skip individual frames/steps in the simulation based on some heuristic and replace this kind of setup in a much more convenient way:
image

UI

Name: Pass-through
Default: False
Position: 1st

### Behavior If true pass through all simulation data from the previous to the next simulation step. Needs to be evaluated before the rest of the simulation step. ### Use case Skip individual frames/steps in the simulation based on some heuristic and replace this kind of setup in a much more convenient way: ![image](/attachments/8dd751a1-90a1-49fb-9058-89eff2eec612) ### UI Name: Pass-through Default: False Position: 1st
138 KiB
Simon Thommes added the
Type
To Do
label 2023-09-07 14:39:15 +02:00
Simon Thommes added this to the Nodes & Physics project 2023-09-07 14:39:18 +02:00
Iliya Katushenock added the
Interest
Geometry Nodes
label 2023-09-07 14:44:31 +02:00
Member

This is definitely a "convenience" feature, and the need might be lessened with some improvements to the switch node (arbitrary number of sockets?). But it also makes sense, and doesn't seem to interact with other convenience sockets we talked about in the past like "Start", "Stop", and "Ended".

This is definitely a "convenience" feature, and the need might be lessened with some improvements to the switch node (arbitrary number of sockets?). But it also makes sense, and doesn't seem to interact with other convenience sockets we talked about in the past like "Start", "Stop", and "Ended".
Author
Member

When using the simulation nodes several times now it felt like this was missing multiple times already. and to me it's something quite integral, so even with the multi input switch that would still require you to manually add connections, especially those that go all the way from input to output and make the tree less readable.

And generally vs start/stop this seems to me to be the most intuitive way of doing this. If we still decide to add others later, that should be compatible.

When using the simulation nodes several times now it felt like this was missing multiple times already. and to me it's something quite integral, so even with the multi input switch that would still require you to manually add connections, especially those that go all the way from input to output and make the tree less readable. And generally vs start/stop this seems to me to be the most intuitive way of doing this. If we still decide to add others later, that should be compatible.
Member

Thanks, makes sense! In the future, it's helpful to have this sort of context in the design/todo task itself.

Thanks, makes sense! In the future, it's helpful to have this sort of context in the design/todo task itself.
Blender Bot added the
Status
Archived
label 2023-09-11 16:49:49 +02:00
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 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#112082
No description provided.