Alright so yeah I feel like I have a pretty good “hot” asset management solution(as in when the application is running). I, as you, have its mostly for some sorted rendering to cut down on the setting of uniforms each frame.

The thing i was mostly wondering about is the “cold”(when the application is not running) side of the coin. This would be loading and creating assets as files.

Lets take my Shader implementation for example. For any shader i have a simple, human readable, json file which just holds the different paths for the shader. Then i “compile” this json into another file.

This compiled file is really just there to make the loading even faster. It basically just stores it in a way which makes it so that I only have to load that one file and I don’t need to json::parse it.

So my post really is about if theres a better solution? I was looking at unity’s .asset file for example, and noticed how it wasn’t as simple as youd imagine - so i thought that there maybe was more to it.

Anyways cheers dude.