Geometry Nodes: Switch node doesn't detect single value for data type correct #47
Assignees
Triager-bot
Clear assignees
Triager-bot
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Triager-bot/blender-bug-reports#47
Reference in New Issue
Block a user
Delete Branch "%!s()"
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?
Original bug report: https://projects.blender.org/blender/blender/issues/157222
System Information
Operating system: Linux-6.18.7-76061807-generic-x86_64-with-glibc2.39 64 Bits, WAYLAND UI
Graphics card: NVIDIA GeForce RTX 5070 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 580.126.18 Opengl Backend
Blender Version
Broken: version: 5.1.0, branch: blender-v5.1-release, commit date: 2026-03-16 18:50, hash:
adfe2921d5f3(also broken in 5.1.1 RC)
Worked: 5.0.1
Short description of error
The
Switchnode should have "single value" sockets and show a warning if a field is linked to the Switch input but set to a single-value data type like Geometry or Bundle.Exact steps for others to reproduce the error
Add
Switchnode, linkPositionor similar to the switch and change data type to Geometry or other single-value data type.Report is clear
LLM Reasoning
Got it, let's analyze the bug report. The question is whether it clearly describes the issue. First, check the title: "Geometry Nodes: Switch node doesn't detect single value for data type correct" – that's clear. Then the body: short description explains what the Switch node should do (have single value sockets and show a warning when a field linked to Switch input is set to single-value types like Geometry). The steps to reproduce are given: add Switch node, link Position or similar, change data type to Geometry. Also, there's a comparison table with images for 5.0 vs 5.1, which helps visualize the issue.
Now, check clarity: the description of the error is specific (what should happen vs what does), steps are clear, and the visual comparison supports it. Even though there's system info, we ignore that as per instructions. The text part about the bug is clear. So the answer should be Yes.
JSON Data
{
"llm_judgement": true,
"processing_time": 11.546507
}
Report is specific
LLM Reasoning
Got it, let's analyze this bug report. The title is "Geometry Nodes: Switch node doesn't detect single value for data type correct". The body talks about a specific issue with the Switch node in Geometry Nodes—how it should handle single-value data types like Geometry or Bundle. The steps to reproduce are adding a Switch node and linking Position (or similar) then changing the data type. This is a specific issue because it's about a particular node (Switch) and a specific behavior (detecting single value for data type). So the answer should be 'Specific'.
JSON Data
{
"llm_judgement": true,
"processing_time": 8.062098
}
Report flagged as NOT a duplicate by LLM
Geometry Nodes : Switch node boolean input does not evaluate fields
https://projects.blender.org/blender/blender/issues/155353
System Information
Operating system: Windows-11-10.0.26200-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 582.28 Opengl Backend
Blender Version
Broken: version: 5.1.0 Beta, branch: blender-v5.1-release, commit date: 2026-03-06 21:31, hash:
4cbe9ce2fe78Worked: (newest version of Blender that worked as expected)
Short description of error
The Switch node boolean input does not appear to support fields correctly. When a field (for example from a Named Attribute node) is connected to the Switch input of the Switch node in Geometry Nodes,nothing happens.
According to the Blender 5.1 documentation, the node should support field evaluation per element when fields are involved. However, the field connected to the Switch input does not seem to be evaluated.
This also occure in 5.2
Exact steps for others to reproduce the error
Open Blender 5.1 (or 5.2).
Add a Geometry Nodes modifier to the default cube.
Create the following node setup (see screenshot):
Observe the result in the viewport.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug Report 1 is about the Switch node not detecting single-value data types (like Geometry) correctly when linked to the switch input. The steps involve linking a Position or similar to the switch and changing the data type to Geometry.
Bug Report 2 is about the Switch node's boolean input not evaluating fields correctly. The steps involve using Named Attribute, Store Named Attribute, Delete Geometry, etc., where the field connected to the Switch input doesn't evaluate.
The core issues seem different: one is about data type detection (single-value vs field), the other is about field evaluation on the boolean input. So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.042845000000002,
"duplicate_report_number": "155353"
}
Report flagged as NOT a duplicate by LLM
Using switch node with one field input automatically makes the output a field
https://projects.blender.org/blender/blender/issues/137304
System Information
Operating system: Windows-10-10.0.26100-SP0 64 Bits
Graphics card: AMD Radeon (TM) Graphics ATI Technologies Inc. 4.6.0 Core Profile Context 24.9.1.240813 Opengl Backend
Blender Version
Broken: version: 4.4.0, branch: blender-v4.4-release, commit date: 2025-03-17 17:00, hash:
05377985c527Worked: Possibly never
Short description of error
The switch node in geometry nodes produces a field output even when the input it's using is not a field, so long as the other one is.
Exact steps for others to reproduce the error
Open Blender 4.4. Add a new geometry nodes modifier. Add a switch node, set it to vector. Set one of the inputs to be the position field and the other to be a single value (0,0,0). Toggle the switch so that the output uses the single value. Your output should still be a field.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps.
Bug report 1 is about the Switch node not detecting single values correctly—specifically, when you link a field (like Position) to the switch input but set its data type to Geometry or other single-value types, the node should have single value sockets and show warnings. The steps involve linking Position and changing data type.
Bug report 2 is about the Switch node outputting a field even when one input is a single value (non-field) because the other is a field. The steps are setting up a switch with position (field) and a single value, toggling to use the single value but output remains a field.
So, are these the same issue? Let's check: Report 1 is about the node not handling single-value data types correctly (maybe socket detection or warnings), report 2 is about the output type being a field when it should be a single value. Wait, maybe they're related but different aspects. But let's see the core issues.
Report 1: Switch node doesn't detect single value for data type correct—so when you link a field to switch input and change its data type to single-value (like Geometry), the node should adjust sockets. Report 2: When one input is field and other is single, output is field even if using single. So maybe different symptoms but same underlying issue? Or not?
Wait, let's check the steps. Report 1's steps: link Position (field) to switch, change data type to Geometry (single-value). Report 2's steps: set switch to vector, one input position (field), other single value (0,0,0), toggle to use single but output is field.
Hmm, maybe they are different. Report 1 is about the node not recognizing the data type as single when linked, report 2 is about output type being field even when using single input. So perhaps not the same issue. Therefore, answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 24.395686,
"duplicate_report_number": "137304"
}
Report flagged as NOT a duplicate by LLM
Geometry Nodes: Compare node in `String` mode shows dynamic output structure type, while only single values are supported
https://projects.blender.org/blender/blender/issues/144046
System Information
Operating system: Linux-6.15.4-gentoo-dist-x86_64-AMD_Ryzen_9_5950X_16-Core_Processor-with-glibc2.41 64 Bits, WAYLAND UI
Graphics card: NVIDIA RTX A6000 NVIDIA Corporation NVIDIA 575.64.03 Vulkan Backend
Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-08-06 00:20, hash:
e8501d2f54c4Worked: (newest version of Blender that worked as expected)
Short description of error
Both string inputs are single values, so only a single value boolean can be produced.
Exact steps for others to reproduce the error
StringLLM Reasoning
Got it, let's analyze these two bug reports. First, look at the titles and descriptions.
Bug report 1 is about the Switch node not detecting single value data types (like Geometry) correctly. The steps involve adding a Switch node, linking Position, changing to Geometry type.
Bug report 2 is about the Compare node in String mode showing dynamic output when only single values are supported. Steps: add compare node, set to String.
The issues are with different nodes (Switch vs Compare) and different contexts (data type detection for Switch vs output structure for Compare). So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 10.957332000000001,
"duplicate_report_number": "144046"
}
Report flagged as NOT a duplicate by LLM
Geometry Node: Socket structure type infered error.
https://projects.blender.org/blender/blender/issues/144322
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce MX450/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 536.99 Opengl Backend
Blender Version
Broken: version: 5.0.0 Alpha, branch: main, commit date: 2025-08-08 18:26, hash:
43850d3223d0Worked: (newest version of Blender that worked not as expected)
Short description of error
The Integer output socket in Separate Bundle is single value, but it infered as field.
Exact steps for others to reproduce the error
Open the file Socket structure type infered error.
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1 is about the Switch node not detecting single value data types (like Geometry) correctly. The steps involve adding a Switch node, linking Position or similar, and changing the data type to Geometry. So the issue is with the Switch node's handling of single-value inputs.
Bug report 2 is about the Separate Bundle node's Integer output socket being inferred as a field instead of single value. The steps are opening a specific file. The problem here is about socket type inference in a different node (Separate Bundle) and a different data type (Integer output).
The key differences: different nodes (Switch vs Separate Bundle), different issues (Switch not detecting single value vs Separate Bundle's output inferred wrong). So they're not the same issue. Therefore, the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 13.246766,
"duplicate_report_number": "144322"
}
Report flagged as NOT a duplicate by LLM
Geometry Nodes: Show "Single Value" only for socket types that can be a field
https://projects.blender.org/blender/blender/issues/113194
The Geometry socket allows users to choose it to be single-value/field, while this option makes no sense for it:
We should use
is_possible_field_socket(make it public, ...) for that.For the records, at the moment the function is lacking the rotation socket type.
Test file: fields.blend
LLM Reasoning
Got it, let's analyze these two bug reports. First, look at the descriptions and steps to reproduce.
Bug report 1 is about the Switch node not detecting single value for data types like Geometry or Bundle when linked. The steps involve adding a Switch node, linking Position (or similar) to switch and changing data type to Geometry.
Bug report 2 is about the Geometry socket allowing "Single Value" option which doesn't make sense, suggesting using
is_possible_field_socketto restrict that. The issue here is about the Geometry socket's single value option being inappropriate, not specifically about the Switch node.So the first is about Switch node's behavior with single-value data types, the second is about the Geometry socket's "Single Value" option in general. They're different issues. So the answer is No.
JSON Data
{
"llm_judgement": false,
"processing_time": 12.063116,
"duplicate_report_number": "113194"
}