Textures mapping mtl file #5
Notifications
Due Date
No due date set.
Depends on
#3 App DLL library and bridge EXE for standalone operation
JCS-Prod/RSE-Texture
#10 New library version of the RS parser
JCS-Prod/RSE-Model
#17 Add texture mtl exporting pre-release
JCS-Prod/RSE-Model
Reference: JCS-Prod/RSE-Model#5
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Use resources of RSE-Texture to permit texture export?
The module should be standalone between them. But in case of mtl materials textures export, the call of Texture module can be justified.
To be solved with the new DLL/LIB implementation of the code.
Approach review:
In conclusion, Model lib can detect texture lib dll presence (or maybe static compilation with correct build options?) and do the texture data search and export MTL after that.
Working on this topic reported after upgrading all RSE modules to new lib structure.
Approach review:
2 point of approach can be quoted:
Tool app will load HOB file AND HMT file using user input (opt. arguments, auto loading using name formating, etc.), tool will use both Model lib and Texture lib.
developto external-libIntegrated in PR #17