Index error: arrays used as indices must be of integer or boolean type when transferring morphs

Issue #784 closed
Jake created an issue

When I tranfer morphs to a clothing object, I get this:

Python: Traceback (most recent call last):
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\error.py", line 208, in execute
self.run(context)
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\transfer.py", line 267, in run
failed = self.transferAllMorphs(context, src, targets)
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\transfer.py", line 286, in transferAllMorphs
if not self.transferMorphs(src, trg, context):
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\transfer.py", line 299, in transferMorphs
if not self.findMatch(src, trg):
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\transfer.py", line 473, in findMatch
self.findMatchNearest(self.trihuman, trg)
File "C:\Users\Yay\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\transfer.py", line 110, in findMatchNearest
tverts = self.verts[tris]
IndexError: arrays used as indices must be of integer (or boolean) type

location: <unknown location>:-1

I’ve already done that on multiple objects, why does it do this with this one?

Comments (5)

  1. Thomas Larsson repo owner

    Weird. I don’t have this problem, and looking at the code I don’t see how it could possibly happen. Perhaps something is corrupt on your side. Have you tried to restart Blender and perhaps rebooting your computer.

  2. Thomas Larsson repo owner

    Now I explicitly specify the type of the offending array to be uint32. I don’t see how that can change everything, because it is an array of vertex numbers, i.e. integers, and the numpy documentation clearly states that the array type will be the minumum type of the entries. But specifying the type cannot hurt.

  3. Log in to comment