Merge Geograft Error

[Fab 3DX]

The plugin keeps showing me the “At least two meshes must be selected” error even though I have the geografts selected and my G8 body as active.
I’m using the version from 25.06.21

[Fab 3DX]

I just tested it with the latest stable version and the latest development version, all give me the same error. I also replaced the exporter scripts in Daz to make sure they’re right. I’m using Blender 2.93 right now.

[Fab 3DX]

I was able to pin down the issue.
I’m using “dForce Majestic Nile for Genesis 8 Females” (from the Daz3D Shop) as clothes, and the neck jewelry is creating an error on import, I somehow missed it on the first imports. Once I removed that piece in Daz and exported the char again it worked fine.
I checked if that object had any face groups and it does. So maybe that group isn’t recognized properly?

Error code:
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\error.py", line 246, in execute self.run(context)
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\daz.py", line 47, in run getMainAsset(self.filepath, context, self)
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\main.py", line 103, in getMainAsset asset.build(context, inst) # Builds morphs
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\modifier.py", line 457, in build self.addVertexGroups(ob, geonode, rig)
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\modifier.py", line 522, in addVertexGroups reportError("No weights for %s in %s" % (bname, ob.name), trigger=(2,5))
File "C:\Users\fab\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\import_daz\error.py", line 130, in reportError raise DazError(msg)

[Thomas Larsson]

I don’t have that asset, but the error should only arise if you have set the global verbosity setting = 5. If you lower that setting, the asset should be imported with a warning message printed in the console window.

[Fab 3DX]

Setting verbosity to 1 fixed it. Like you said it just shows a warning in the console and not an error like before.