hannesdelbeke / mesh-data-transfer Goto Github PK
View Code? Open in Web Editor NEWMeshDataTransfer Blender addon
Home Page: https://mmemoli.gumroad.com/l/tOKEh
License: GNU General Public License v3.0
MeshDataTransfer Blender addon
Home Page: https://mmemoli.gumroad.com/l/tOKEh
License: GNU General Public License v3.0
Hi, I just bought a again the addon on gumroad for support.
Whatever I do I get this error. TRied blender 3.5, 3.6, 4.1, addon version 2.02 2.03, vertex ID, UV (both meshes have exact same UVs.)
Trying to transfer the shape (realistic CC4 to cartoony CC4 character.)
Error: Python: Traceback (most recent call last):
File "C:\Users\Admin\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\MeshDataTransfer\operators.py", line 115, in execute
transfer_data = MeshDataTransfer(target=active, source =source, world_space=world_space,
File "C:\Users\Admin\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\MeshDataTransfer\mesh_data_transfer.py", line 633, in __init__
self.cast_verts()
File "C:\Users\Admin\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\MeshDataTransfer\mesh_data_transfer.py", line 1141, in cast_verts
self.related_ids = np.zeros(v_count * 3, dtype=np.int)
File "C:\Users\Admin\AppData\Roaming\Python\Python310\site-packages\numpy\__init__.py", line 338, in __getattr__
raise AttributeError(__former_attrs__[attr])
AttributeError: module 'numpy' has no attribute 'int'.
`np.int` was a deprecated alias for the builtin `int`. To avoid this error in existing code, use `int` by itself. Doing this will not modify any behavior and is safe. When replacing `np.int`, you may wish to use e.g. `np.int64` or `np.int32` to specify the precision. If you wish to review your current use, check the release note link for additional information.
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. Did you mean: 'inf'?
This happens to me sometimes when i use shape transfer based on UV map, in cases where the mesh is reasonably dense. Some vertices might end up with NaN for coordinates, which effectively makes them disappear from viewport, making it impossible to select and move them manually.
I tried to look at the code myself, and i think the bug occurs somewhere in get_barycentric_coords method, particularly in:
main_triangle_areas = np.cross((triangles[:, 0] - triangles[:, 1]), (triangles[:, 0] - triangles[:, 2]))
where, i think, some values end up being 0, and then division by 0 ends up happening later down. But i don't really understand this code, and can't fix it myself.
I'll attach a file with two meshes which you can replicate the bug with.
example.zip
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.