Page MenuHome

"normal" attribute created with python cause rotation bugs
Closed, ArchivedPublic

Description

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-01-31 14:53, hash: rBb10fac0432c6

Short description of error
Hello, I played a bit with geo node and python, I was playing with a custom script that spawns vertices with custom attr named "normal" so geo node could create an instance with the correct normal orientation from the given mesh. (Nothing else)

But it seems that there are conflicts going on with meshes with custom "normal" attr?
In the file below, the mesh with the custom "normal" attr have a weird behavior:
-random non-used connected nodes are changing points rotation
-enter edit mode will change points rotation

I'm not sure if this is purely linked with the custom-created normal attr or this is a more generic bug?

Exact steps for others to reproduce the error
Open file below
disable node called "DISABLE ME" or enter edit mode

Event Timeline

NoobiePoopsie (helloidonthaveanyideaformyusername) renamed this task from "normal" attribute created with python cause conflicts to "normal" attribute created with python cause bugs .Feb 1 2021, 10:37 PM
NoobiePoopsie (helloidonthaveanyideaformyusername) renamed this task from "normal" attribute created with python cause bugs to "normal" attribute created with python cause rotation bugs .
Jacques Lucke (JacquesLucke) changed the task status from Needs Triage to Needs Information from User.Mar 19 2021, 1:36 PM

Can't say for sure what is happening there. Also the normal attribute is now builtin, so you should use a different name for your custom attribute. Please update your initial post for latest master and use a different attribute name.

Will close this because there was no reply within a week. Feel free to open it again when the first post has been updated.

I believe the issue got fixed in february