1. These first attempt exports were exported AS IS.
FBX had warnings (usupported maps/textures, animation curves, skin definitions...)
DAE had warnings (usupported maps/textures, animation curves, skin definitions...)
OBJ had warnings (shaders, flatten hierarchy)
2. Updated Assets
Victor_rig_01.FBX - minor fixes in hierarchy and skeleton for blender, unity and assimp (asset import lib)
Victor_rig_01.3ds - new 3ds export
3. New Directory Structure for File Formats
This was the best possible solution I could come up with (without duplicating tons of files and bloating the repo with multiple copes of each file) In each directory of assets, where new models/rigs have been made using new file formats, the file formats have been divided by subdirectory This should allow for easy picking and choosing of what assets to open/look for based upon the program being used. Yes, there will be some bloat because, for example, if you only need the Maya files, you'll be downloading the rest anyway-
But I have no desire to maintain multiple branches and track changes across all of those branches for other assets, such as the scripts. If there is a better solution, please feel free to suggest- otherwise, if we merge this into the main branch of cyb3rdog's fork, this will enable the PR for this fork to be merged into main of the DDL official repo.
4. Clean up
wavefront OBJ material (*.mtl) files moved to OBJ sub-dirs
1. These first attempt exports were exported AS IS.
FBX had warnings (usupported maps/textures, animation curves, skin definitions...) DAE had warnings (usupported maps/textures, animation curves, skin definitions...) OBJ had warnings (shaders, flatten hierarchy)
2. Updated Assets
3. New Directory Structure for File Formats
This was the best possible solution I could come up with (without duplicating tons of files and bloating the repo with multiple copes of each file) In each directory of assets, where new models/rigs have been made using new file formats, the file formats have been divided by subdirectory This should allow for easy picking and choosing of what assets to open/look for based upon the program being used. Yes, there will be some bloat because, for example, if you only need the Maya files, you'll be downloading the rest anyway- But I have no desire to maintain multiple branches and track changes across all of those branches for other assets, such as the scripts. If there is a better solution, please feel free to suggest- otherwise, if we merge this into the main branch of cyb3rdog's fork, this will enable the PR for this fork to be merged into main of the DDL official repo.
4. Clean up