Error when loading a saved pose or preset

[Buddyspencer13]

Hi, Thomas, testing your latest version, I have found this bug, I have tested two versions, an old one where it works, and the new one where it gives error and this is what it shows ;

Error >

Python: Traceback (most recent call last):
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\error.py", line 207, in execute
self.run(context)

File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\animation.py", line 1486, in run
StandardAnimation.run(self, context)

File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\animation.py", line 1241, in run
offset,prop = self.getSingleAnimation(filepath, context, offset)

File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\animation.py", line 726, in getSingleAnimation
nanims,locks = self.prepareAnimations(anims, rig)

File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\animation.py", line 157, in prepareAnimations
bonemap,locks = self.setupBoneMap(anims, rig)

File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.2\scripts\addons\Diffeomorphic-import_daz-28802c5127bc\animation.py", line 187, in setupBoneMap
elif bname[0] in ["l", "r"] and bname[1].isupper():
IndexError: string index out of range

‌

Saving the pose, with the latest version, and loading it gives error, 1.6.2.1135 (Diffeomorphic-import_daz-28802c5127bc).

On the other hand using an older version, 1.6.2.1110, (Diffeomorphic-import_daz-adddb0b9850a) gives no error and the pose loads correctly.

[Buddyspencer13]

Apologies for not having clarified or specified the instructions, the steps to follow are quick;

1- Import GF8 or G8M, and then, pose or move any bone.

2- Selecting the armature “Genesis 8 Female, Genesis 8 Male”, in the panel, Posing, click on the option "Save Pose Preset" to save the pose, and save in any folder.

3- Then Import or load the pose in the character or any other character, selecting the armature, with the option "Import Pose" in the same panel "Posing".

When trying to load any saved pose, on a character, it gives error and does not work.

[engetudouiti]

good report ^^ so anyone can easy confirm..

Yes now I confirmed for G3 with zero pose save and load in blender

[Thomas Larsson]

Fixed in last commit.

[engetudouiti]

maybe we need to save pose preset again?

[Buddyspencer13]

Thanks engetudouiti, good to know it wasn't just me, and many thanks Thomas for looking at it, I have tried your latest version 0ece8be and creating poses with that version, saving and later load them again, works well.

But I wanted to mention something, is that, the poses saved with previous or old versions, when loading them, with the latest version give error, it’s normal? since you have changed the code and that may imply that behavior.

In any case, there is always the option, to load the poses with a previous version, or the stable one 1.6.1, and apply them to the Armatures and duplicate them to apply each pose to each armature, and save them in a Blend scene, then, it would be to save them with the latest version and to be able to update each pose, for later use.

[engetudouiti]

I suspect,, at least some version saved pose will cause issue, when I check verison which was not up-date to new (Thomas corrected)

the saved file somehow strange,, (start with empty, and next duf @ selection value was in dic. so it seems somehow difficult

to edit load funciton which can load correctly… and it make script dirtty ^^;

So thomas way to change saved function to generate clean pose duf, was important..

(And I suppose,, those saved duf can not load in daz studio too, if it not follow daz DSON rule.

I think it may only happen for some version (which Thomas change save function for beta).

[Buddyspencer13]

I see, right, don't think there is much problem for me in that case ^^ as you say, if Thomas had to change the saved function to generate duf's cleanly, with the latest versions and the fix of this last one, it is better to have the code clean and correct.