Fast mesh IO for addon development

archibate · August 12, 2021, 2:39pm

Exactly, I have tried NumPy arrays, it did work, but not too much faster than raw Python list… here was my attempt:

taichi-dev/taichi_blend/blob/907fdbee6027375324c9605ffc14db16e590f992/taichi_blend/bundle-packages/numblend/numio.py#L11


      
          '''Blender-NumPy interface'''
          
          import numpy as np
          from .common import np_array
          
          
          def to_numpy(b, key, dim=None):
              dim = dim or len(getattr(b[0], key))
              dim = len(getattr(b[0], key))
              seq = [0] * (len(b) * dim)
              b.foreach_get(key, seq)
              return np.array(seq).reshape(len(b), dim)
          
          
          def from_numpy(b, key, a, dim=None):
              a = np_array(a)
              if dim is None:
                  dim = len(getattr(b[0], key)) if len(b) else a.shape[1]
              assert len(a.shape) == 2
              assert a.shape[1] == dim
              if len(b) < a.shape[0]:

So I was thinking if it actually silently convert NumPy array to Python list in foreach_get, maybe I was wrong.

Thank for your information! So Blender will build something like a lookup table for geometry processing, every time after I update vertices of it?
But actually I don’t expect user to be able to enter Object Mode (by pressing Tab) to edit the generated mesh… it will update every frame… Is it possible to dump a read-only mesh, to prevent Blender from building the lookup tables, like what the Blender built-in fluid solver does?

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Fast mesh IO for addon development