Python script has visual bugs when inputting floats and integers into geometry node inputs #119064

New Issue

Edward-Savage · 2024-03-04T21:44:52+01:00

Edward-Savage commented

2024-03-04 21:44:52 +01:00

System Information
Edition Windows 10 Home
Version 22H2
Installed on ‎29/‎09/‎2023
OS build 19045.4046
Experience Windows Feature Experience Pack 1000.19053.1000.0

Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor

Blender Version
Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b7

Short description of error
When using the python console or text editor, geometry node inputs do weird things. (visually, and can be returned by making any change to the nodes)(putting an integer value into a 'float' type input causes the input box to disappear, and putting a number with decimal places (e.g. "1.0")in will change the subtype of the input)

Exact steps for others to reproduce the error

The video attached says these steps in more detail, and is easier to understand, but i included the process in text just in case.

Create a new geometry node tree data block
Add any geometry node (I've been using subdivision surface)
Connect any float value into the group input node, so that the value can be edited in the modifier panel
Change the value to any integer number
In the Info panel, copy the latest action
Change the value to anything (this is just to see if the code does anything)
Paste the action into the python console
The input box (in geometry nodes in modifiers panel) disappears, and an error shows saying "Property type does not match input socket "(Edge Crease)"". (I was using the edge crease from the subdivision surface node). When i say disappears, i mean its a visual bug, so it is not actually gone, any change to the nodes will refresh it and make the box reappear.
If you change the code to have a number with a decimal place (e.g. "1.0"), then the value does change, and the box does not disappear. However, the 'subtype' of the input has been visually changed to 'none'. (e.g. it changes from 'factor'). Any change to the nodes will refresh it and turn it back into the original subtype.

(keep in mind that in order to see the change to the object, you have to turn off and on the viewport visibility. This is a separate bug that has been reported here)

**System Information** Edition Windows 10 Home Version 22H2 Installed on ‎29/‎09/‎2023 OS build 19045.4046 Experience Windows Feature Experience Pack 1000.19053.1000.0 Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz Installed RAM 16.0 GB System type 64-bit operating system, x64-based processor **Blender Version** Broken: version: 4.0.2, branch: blender-v4.0-release, commit date: 2023-12-05 07:41, hash: 9be62e85b727 **Short description of error** When using the python console or text editor, geometry node inputs do weird things. (visually, and can be returned by making any change to the nodes)(putting an integer value into a 'float' type input causes the input box to disappear, and putting a number with decimal places (e.g. "1.0")in will change the subtype of the input) <video src="/attachments/879c065d-f2c2-4e4a-a0cf-65b9f537bb25" controls></video> **Exact steps for others to reproduce the error** The video attached says these steps in more detail, and is easier to understand, but i included the process in text just in case. 1. Create a new geometry node tree data block 2. Add any geometry node (I've been using subdivision surface) 3. Connect any float value into the group input node, so that the value can be edited in the modifier panel 4. Change the value to any integer number 5. In the Info panel, copy the latest action 6. Change the value to anything (this is just to see if the code does anything) 7. Paste the action into the python console 8. The input box (in geometry nodes in modifiers panel) disappears, and an error shows saying "Property type does not match input socket "(Edge Crease)"". (I was using the edge crease from the subdivision surface node). When i say disappears, i mean its a visual bug, so it is not actually gone, any change to the nodes will refresh it and make the box reappear. 9. If you change the code to have a number with a decimal place (e.g. "1.0"), then the value does change, and the box does not disappear. However, the 'subtype' of the input has been visually changed to 'none'. (e.g. it changes from 'factor'). Any change to the nodes will refresh it and turn it back into the original subtype. (keep in mind that in order to see the change to the object, you have to turn off and on the viewport visibility. This is a separate bug that has been reported [here](https://projects.blender.org/blender/blender/issues/87006))

bug report.mov

34 MiB

Edward-Savage added the

labels 2024-03-04 21:44:52 +01:00

Edward-Savage changed title from ~~Python script~~ to Python script has visual bugs when inputting floats and integers into geometry node inputs

2024-03-04 21:47:46 +01:00

Germano Cavalcante commented

2024-03-05 16:09:53 +01:00

I can confirm the issue reported.
It seems to be related to #112646: "Geometry Nodes input subtype changes on assign".

I also noticed another issue when testing on Blender 4.2. The operations Log in the Info Editor is wrong in 4.2. Will report separately.

I can confirm the issue reported. It seems to be related to #112646: "Geometry Nodes input subtype changes on assign". I also noticed another issue when testing on Blender 4.2. The operations Log in the Info Editor is wrong in 4.2. Will report separately.

Germano Cavalcante added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Python script has visual bugs when inputting floats and integers into geometry node inputs #119064