Skip to content
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

Error with Pulga Inflate Force node #5171

Open
scorpion451 opened this issue Nov 22, 2024 · 1 comment
Open

Error with Pulga Inflate Force node #5171

scorpion451 opened this issue Nov 22, 2024 · 1 comment

Comments

@scorpion451
Copy link

The Pulga Inflate Force node is returning the following error in Blender 4.2.3:

[ERROR] sverchok.node_error __init__.py:305 - module 'numpy' has no attribute 'object'.
`np.object` was a deprecated alias for the builtin `object`. To avoid this error in existing code, use `object` by itself. Doing this will not modify any behavior and is safe.
The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
    https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

Steps to reproduce

  1. Add Pulga Inflate Force node
  2. Attach an input to the polygon socket
  3. Attach output socket to something
  4. Once steps 2 and 3 have been done, the above error message appears in both node editor and the console

A plane, box and torus all throw the error with Inflate node, but not other Pulga nodes:
image

Not shown but possibly relevant for troubleshooting, the error is also thrown when an invalid input like Vertices is connected to the Polygons socket

Sverchok version

installed from release zip file, release 1.3.0, Blender version is 4.2.3 compiled for Windows 7

@scorpion451
Copy link
Author

scorpion451 commented Nov 22, 2024

Managed to find the fix:

line 1336 of pulga_physics_modular_core.py in sverchok's utils folder (part of the SvInflateForce class code)
if np_pols.dtype == np.object:
needs to be changed to:
if np_pols.dtype == object:
The node functions without issue with this fix applied.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant