Move to Nodes does not work if the node tree has no Geometry input or output #106257

New Issue

Closed

opened 2023-03-29 07:52:19 +02:00 by Sun Kim · 3 comments

Sun Kim commented

2023-03-29 07:52:19 +02:00

Contributor

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315

Blender Version
Broken: version: 3.6.0 Alpha, branch: main, commit date: 2023-03-27 23:56, hash: 16576beb222a
Worked: n/a

Move to Nodes operator is introduced in 3.5.

Short description of error
Move to Nodes operator does not work if Geometry Nodes has no geometry input or output.

Error:

Python: Traceback (most recent call last):
  File "C:\Program Files (x86)\Steam\steamapps\common\Blender\3.6\scripts\startup\bl_operators\geometry_nodes.py", line 189, in execute
    group.links.new(first_geometry_output, group_output_node.inputs[data_("Geometry")])
TypeError: NodeLinks.new(): error with argument 1, "input" -  Function.input does not support a 'None' assignment NodeSocket type

If the operator should not work in this case, it's missing proper error message and documentation for it.

Exact steps for others to reproduce the error

From startup file, add Geometry Nodes to the cube
From node editor, go to Sidebar > Group, and remove either Geometry input or output
From modifier panel, select Move to Nodes

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.0 Core Profile Context 23.3.2.230315 **Blender Version** Broken: version: 3.6.0 Alpha, branch: main, commit date: 2023-03-27 23:56, hash: `16576beb222a` Worked: n/a Move to Nodes operator is introduced in 3.5. **Short description of error** `Move to Nodes` operator does not work if Geometry Nodes has no geometry input or output. Error: ``` Python: Traceback (most recent call last): File "C:\Program Files (x86)\Steam\steamapps\common\Blender\3.6\scripts\startup\bl_operators\geometry_nodes.py", line 189, in execute group.links.new(first_geometry_output, group_output_node.inputs[data_("Geometry")]) TypeError: NodeLinks.new(): error with argument 1, "input" - Function.input does not support a 'None' assignment NodeSocket type ``` If the operator should not work in this case, it's missing proper error message and documentation for it. **Exact steps for others to reproduce the error** - From startup file, add Geometry Nodes to the cube - From node editor, go to `Sidebar > Group`, and remove either Geometry input or output - From modifier panel, select Move to Nodes ![MovetoNodes.png](/attachments/3d86312d-cc44-4b4f-93b6-06cd55545d44)

MovetoNodes.png

16 KiB

Sun Kim added the

labels 2023-03-29 07:52:20 +02:00

Iliya Katushenock added

Nodes & Physics

and removed

labels 2023-03-29 12:28:21 +02:00

Hans Goudey added the

Good First Issue

label 2023-03-29 20:10:57 +02:00

Elena-Peng commented

2023-03-30 16:07:50 +02:00

If no one else is working on this, could I take it as my first issue?

If no one else is working on this, could I take it as my first issue?

Iliya Katushenock commented

2023-03-30 16:15:01 +02:00

Member

@Elena-Peng Hey, of course

@Elena-Peng Hey, of course

Sun Kim referenced this issue

2023-06-10 14:35:11 +02:00

Error in "Move to Nodes" operator when the tree has no Geometry inputs #107791

Hyu Ogawa commented

2023-08-01 05:56:07 +02:00

Contributor

There is a difference between removing Geometry input/output from Sidebar > Group and removing input/output nodes in Node Editor.
Actually, removing input/output nodes directory has no problem because input/output geometries are still saved in group input/output. However, removing group input/output makes this issue.

As @persun says, I think correct error handling and documentation is needed, and I'll work on it.

There is a difference between removing Geometry input/output from `Sidebar > Group` and removing input/output nodes in Node Editor. Actually, removing input/output nodes directory has no problem because input/output geometries are still saved in group input/output. However, removing group input/output makes this issue. As @persun says, I think correct error handling and documentation is needed, and I'll work on it.

Hyu Ogawa referenced this issue from blender/blender-manual

2023-08-01 05:57:57 +02:00

Add constraints executing Move to Nodes #104529

Hyu Ogawa referenced a pull request that will close this issue

2023-08-01 06:07:58 +02:00

Fix #106257: Move to Nodes does not work if the node tree has no Geometry input or output #110670

Hans Goudey referenced this issue from a commit

2023-08-02 14:00:38 +02:00

Fix #106257: Move to Nodes error with no geometry input/output

Hans Goudey closed this issue

2023-08-02 14:00:40 +02:00

Blender Bot added

and removed

labels 2023-08-02 14:00:41 +02:00

Aaron Carlisle referenced this issue from a commit

2023-08-07 02:09:15 +02:00

Add constraints executing Move to Nodes

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

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#106257

No description provided.