Better error handling of unsupported node group inputs #82438

New Issue

Right now if you connect a geometry input in the modifier stack you get a warning in the UI:

Right now if you connect a geometry input in the modifier stack you get a warning in the UI: ![image.png](https://archive.blender.org/developer/F9210918/image.png)

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

Added subscriber: @dfelinto

Done in {1ddd71780365796efde9c08b0aa08990d2d004a4}.

The types of errors it checks for should be clear from the strings in that commit.

Done in {1ddd71780365796efde9c08b0aa08990d2d004a4}. The types of errors it checks for should be clear from the strings in that commit.

If I connect a vector3 (e.g., Object Info -> Location) in the group output it throws an error regarding "The node group must have a single geometry output".

I don't think we should throw any error re: output nodes, unless there is NONE Geometry output. Since users can re-use the nodes as either groups or modifiers I don't think they need to be warned about the output.

Suggestion of error when there is no "Geometry Output" socket: "The node group must one geometry output".

If I connect a vector3 (e.g., Object Info -> Location) in the group output it throws an error regarding "The node group must have a single geometry output". I don't think we should throw any error re: output nodes, unless there is NONE Geometry output. Since users can re-use the nodes as either groups or modifiers I don't think they need to be warned about the output. Suggestion of error when there is no "Geometry Output" socket: "The node group must one geometry output".

96ce1e9a95 addresses this.

Changed status from 'Confirmed' to: 'Resolved'

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Better error handling of unsupported node group inputs #82438