Skip to content

Genesis 9 JCM transfers may produce extremely large FBX files due to over-inclusive morph string matching #8

@danielbui78

Description

@danielbui78

Genesis 9 JCM transfers may produce extremely large FBX files due to over-inclusive morph string matching during the FbxExporter phase. This morph string matching issue particularly affects Genesis 9 due to the fact that all JCM morph names for every Genesis 9 character are subsets/supersets of each other.

TODO:

  • Workaround: Export Genesis 9 without morphs using the FbxExporter, then manually re-open the Fbx file and insert desired morphs
  • Make sure to develop thorough test cases to check for byte-for-byte file reproduction (in order to maintain compatibility with some Daz Bridge functions that are hardcoded to check Fbx byte signature to identify certain conditions).
  • Replace all hardcoded checks for Fbx byte signature with equivalent metadata in JSON file (DTU).

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions