Find a solution to preview of a part of the nodetree #83239

Closed
opened 2020-11-30 15:22:37 +01:00 by Dalai Felinto · 14 comments
No description provided.
Author
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto
Pablo Vazquez self-assigned this 2020-11-30 15:23:15 +01:00
Pablo Vazquez was unassigned by Dalai Felinto 2021-02-15 14:05:54 +01:00
Author
Owner

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez
Member

Added subscriber: @wannes.malfait

Added subscriber: @wannes.malfait
Member

Isn't it possible to just use the thing that node wrangler does for shaders nodes, i.e. CTRL + SHIFT + RMB connects the geometry socket of the selected node to the group output?

Isn't it possible to just use the thing that node wrangler does for shaders nodes, i.e. `CTRL + SHIFT + RMB` connects the geometry socket of the selected node to the group output?

Added subscriber: @Erindale

Added subscriber: @Erindale

I second this re: CTRL+SHIFT+LMB. We're all so accustomed to Node Wrangler and the same shortcut creates a viewer in Sverchok to allow you to preview current step.
I think as long as a Geometry Socket is present, it should just auto connect to the Group Output node.

There also should be a text viewer to check numeric output of math nodes as doing multiple complex transforms get's a bit much for mental arithmetic. I think something like the Animation Nodes viewer is neat and practical for this purpose: {F9817727}

Edit: spreadsheet already fulfills the text viewer comment.

I second this re: `CTRL+SHIFT+LMB`. We're all so accustomed to Node Wrangler and the same shortcut creates a viewer in Sverchok to allow you to preview current step. I think as long as a Geometry Socket is present, it should just auto connect to the Group Output node. ``` There also should be a text viewer to check numeric output of math nodes as doing multiple complex transforms get's a bit much for mental arithmetic. I think something like the Animation Nodes viewer is neat and practical for this purpose: {F9817727} ``` Edit: spreadsheet already fulfills the text viewer comment.

Added subscriber: @Low_Polygon42

Added subscriber: @Low_Polygon42

Added subscriber: @elfoglalt

Added subscriber: @elfoglalt

Design ideas for how this could look like:

1.jpg
2.jpg
3.jpg

I think none of the existing solutions tick all the boxes:
4.jpg

Design ideas for how this could look like: ![1.jpg](https://archive.blender.org/developer/F9895221/1.jpg) ![2.jpg](https://archive.blender.org/developer/F9895223/2.jpg) ![3.jpg](https://archive.blender.org/developer/F9895225/3.jpg) I think none of the existing solutions tick all the boxes: ![4.jpg](https://archive.blender.org/developer/F9895252/4.jpg)

I think the pop over probes are a really sharp design for within the node tree. My question though would be, how is this displayed in 3D?
For example if you're putting the probe on a Geometry socket, does it change the geometry in the viewport?
In Sverchok the viewer nodes will output the model as an overlay instead of real geometry so there's no risk of you rendering them and / or missing them in the viewport.

Also what would happen when probing a single value like that from a math / vector math node as opposed to an Attribute?
It could be a good opportunity to have some kind of display attached to the probe as things that aren't on an attribute won't appear in the spreadsheet.
The current method of creating a burner attribute on an Attribute Fill node just to debug math nodes feels like a long way around.

I think the pop over probes are a really sharp design for within the node tree. My question though would be, how is this displayed in 3D? For example if you're putting the probe on a Geometry socket, does it change the geometry in the viewport? In Sverchok the viewer nodes will output the model as an overlay instead of real geometry so there's no risk of you rendering them and / or missing them in the viewport. Also what would happen when probing a single value like that from a math / vector math node as opposed to an Attribute? It could be a good opportunity to have some kind of display attached to the probe as things that aren't on an attribute won't appear in the spreadsheet. The current method of creating a burner attribute on an Attribute Fill node just to debug math nodes feels like a long way around.

Added subscriber: @CreatorSiSo

Added subscriber: @CreatorSiSo

Good questions!

Initially, 3d visualization would be just overriding the geometry output with the probed geometry (see #3). As for more complicated overlays, I think that would fall more under #85653.

As for inspecting non-geometry, I'd imagine in the future the spreadsheet editor will be able to display all sorts of data, not just attributes. So when you inspect a wire, you could see it's "contents" in the spreadsheet editor in a similar fashion. One exciting future possibility would be to inspect a node directly, and see it's inputs, implicit conversions, and outputs as columns all in the same spreadsheet. node_inspect.jpg However, this is probably something for the far future.

Other usability tidbits, instead of the x icon and removing probes, they could also use the pinning method already present in some editors:
detail_pinning_alt.jpg

Good questions! Initially, 3d visualization would be just overriding the geometry output with the probed geometry (see #3). As for more complicated overlays, I think that would fall more under #85653. As for inspecting non-geometry, I'd imagine in the future the spreadsheet editor will be able to display all sorts of data, not just attributes. So when you inspect a wire, you could see it's "contents" in the spreadsheet editor in a similar fashion. One exciting future possibility would be to inspect a node directly, and see it's inputs, implicit conversions, and outputs as columns all in the same spreadsheet. ![node_inspect.jpg](https://archive.blender.org/developer/F9896876/node_inspect.jpg) However, this is probably something for the far future. Other usability tidbits, instead of the x icon and removing probes, they could also use the pinning method already present in some editors: ![detail_pinning_alt.jpg](https://archive.blender.org/developer/F9896877/detail_pinning_alt.jpg)
Contributor

Added subscriber: @RedMser

Added subscriber: @RedMser
Member

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Jacques Lucke self-assigned this 2022-11-16 15:51:09 +01: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 project
No Assignees
8 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#83239
No description provided.