-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new "Get Objects Data" node broke backward compatibility and usability #5105
Comments
Hi @rendetto Can you give a file for tests? I try an example of grid and do not see any vectors: |
Hello @satabol Here's a screenshot from master and the problem is still present: It appears that it's present when the input object is a mesh and is in edit mode. When the input mesh is in object mode the problem is not present: I'm attaching the test file for convenience: |
I see. I look code and see this feature: sverchok/nodes/scene/get_objects_data.py Lines 408 to 414 in 6db84ff
I don't know why this feature is used but now it is work as expected. |
Do you mean that it is supposed to output Vector when in edit mode? |
It is my turn to send you my sorry. I understood all problems now! ))) I need some time to think. Please wait. |
@rendetto Try this trick for a while: turn on numpy for vertices: It will work without errors in object or edit mode now. I continue thinking... |
@satabol now it works as expected. Thank you! |
With the merge of #5022 the node "Get Objects Data" now outputs vertices and normals in Vector(( )) format.
This brakes the compatibility with other nodes and also it makes it harder to modify the data further using list nodes.
The text was updated successfully, but these errors were encountered: