when you import Victoria 8.1 It says the type of character is Genesis 8

Issue #1757 invalid
Joe Morris @ FAST Animation Studio Toolz created an issue

I don't think you need the DUF file because when I importer the character actually says Victoria 8.1 in the name so there shouldn't be any reason for error… but if you need I could provide blender file or duf I just thought you should know this… It says the Rig and armature name are Victoria 8….

e.object): C:\Users\blender\git\blender-v360\blender.git\source\blender\blenkernel\intern\object.cc:3252 ob_parbone: Parent Bone: 'lForearmTwist(drv)' for Object: 'Teen Kitty Bangles.001' doesn't exist
Make All Bones Posable completed in 2.3 seconds
File  loaded in 115.882 seconds
Merging rigs...
obj.name: Victoria 8.002
Armature Name: Victoria 8.002
Parent collection: V_base.001
Armature Name: Victoria 8.002
Rig Name: Victoria 8.002
Mesh Name: Victoria 8.002 Mesh
Rig not found
Load C:\Users\W\AppData\Roaming\Blender Foundation\Blender\3.6\scripts\addons\import_daz\data\altmorphs\genesis8.json

--------------------
* V_POSE.duf 1
Character: genesis_8_female

Comments (6)

  1. Thomas Larsson repo owner
    • changed status to open

    The base figure of Victoria 8.1 is Genesis 8; it has the same mesh topology and armature. So what is the problem?

  2. Joe Morris @ FAST Animation Studio Toolz reporter

    Okay I had no idea …. So are you saying all Genesis 8.1 use the Genesis 8 armature or just Victoria

  3. Alessandro Padovani

    G8.1 use the same rig as G8, and the same base mesh. It adds different morphs for FACS, and a different uv map for pbrskin materials. Indeed even in daz studio G8 and G8.1 figures share the same content folders. Outfits and materials can be exchanged.

    If there’s nothing to add we can close as invalid.

  4. Joe Morris @ FAST Animation Studio Toolz reporter

    I really appreciate that information now I could just do it blindly instead of guessing

  5. Joe Morris @ FAST Animation Studio Toolz reporter

    One more thing in my mind I would usually seek when I write a function like this to find one more identifying feature I could grab ahold of and accentuate my functionality with so would unequivocally Tell me whenever I will import a character a 100 percent what type of character it is so I would have the power in the future to use that as conditionals in my code and rely on it, why haven't you done that in this instance just out of curiosity… You know D a Z studio so well I assume it's because it's not necessary…

  6. Log in to comment