joint rotations not aligned due to error in python

[Gurgaljev]

This is a followup to a comment in #50 - tried your suggestion but did not solve the issue.

When i import the joint rotations all remain zeroed - the window stays at saying 'importing - please wait'. Your idea was right that this could mean the python script has stopped (and i remember the correction of the joint rotations being the last step in earlier versions)
So the imported figure looks like the first screenshot - the console log of python in C4d reads like the second screenshot

i work on mac with DS 4.21 and C4D R19
was able to reproduce the same thing when importing to C4D R20

My tests were with plain G9 the way it loads (with or without materials) - i get the same result with G8

[danielbui78]

The latest bridge update should fix the joint rotation and alignment issues on both G8 and G9. I've tested it with Python 2.7.14 final on R21, lower versions may also work. Please let me know if there are any other problems.

Regards

[Gurgaljev]

Thank you for trying and sorry for the long delay with an answer...
I tried the new version last year and it did not change anything in R19 and R20, so i used a different setup.

But now i am back for different characters and at least found a workaround that works in R19 and R20 (maybe this helps someone looking for help here)
The issue seems to be hidden in the creation of materials. I can also add a screenshot of the console in C4D:

It is similar to the old error, just this time he expects a float and gets unicode.

At that point the script stops and so later steps, especially the crucial fix of joint rotations is not performed.

The workaround is to simply delete the materials in Daz before export ;-)
I replaced everything with the standard Daz Material (light grey) and do not use any textures.
A model exported that way imports without any problems and also the joint rotations are adapted!
So the only thing needed to do is export it twice - and get the materials across from the import where the script crashes ;-)

Maybe this is even easy to fix but for me it is also ok that way - so it works fine for the newer versions of C4D there is no reason to put more time into it (after all i have heard from another developer there seems to be some bug in the older python versions if C4D that was corrected with version R21 - maybe this is also the culprit here)