Currently there is only a runtime resource solution for VixenEngine. There needs to be an offline (not runtime) resource management solution that can transform DCC content into the content packages loadable by the game engine itself. This system will be needed for VixenEditor at some point to be able to compile content.
Features:
manage multiple types in consistent manner
create new resources
delete resources
inspect / modify existing resources
change resource file location on disk
resources must have built in cross-reference dependency checking to assist in resource building and loading process
maintain referential integrity across all resource operations such as deleting or moving
maintain revision history of resource changes, with comments for changes
query system for developers or artists to know where resources are being used in the game
How do we implement such a feature?
content compilers will be written as subsystem VixenEngine
leverage the libgit2 C-api to develop a resource database.
utilize the XML file format to serialize database entries and maintain the relational database
develop and integrate a GUI front-end into VixenEditor for developers to easily manage resources.
Comments
Please let me know if you have any questions or concerns involving this project. It is no small task to create such a resource system, but I believe developing such a feature for Vixen will greatly improve the engine.
Currently there is only a runtime resource solution for VixenEngine. There needs to be an offline (not runtime) resource management solution that can transform DCC content into the content packages loadable by the game engine itself. This system will be needed for VixenEditor at some point to be able to compile content.
Features:
How do we implement such a feature?
Comments
Please let me know if you have any questions or concerns involving this project. It is no small task to create such a resource system, but I believe developing such a feature for Vixen will greatly improve the engine.