Asset Pipeline Introduction
.png)
I've always had this pipe dream of being able to live-edit all assets in a game project while the game is running and I'm feeling really strong about the progress of this newest project!
Most/all of my personal side-project revolve around C/C++ desktop apps with homespun engines. It's usually as much a journeyman effort for learning more CS as it is a desire to make a game. A big part of solving the issue of finishing a game has to do with having good architecture with a good assets pipeline.
In this example we have:
- The assets data-catalog is on the top left
- A running game instance in the top right (can have multiple running in windows independently in the same exe)
- A tile schema editor for map tiles in the bottom left
- A homemade pixel image editor in the bottom right.
Any pixel edits to the graphics in the editor live-update anywhere they are used (in this case both the running game and the schema editor) giving you redundancy to test your edits. It also has perfect referential integrity so you never have to worry about your game crashing when an assert comes up missing.
I will have to come up with some thoughtful posts digging into the how's and why's of all of this but the main concepts at play here are:
- “C-Style” C++
- Generated reflection code from struct definitions
- Generic recursive file format
- Live++
- Dear ImGui
| 🌐 | 🙋 | 
@britown@blog.brianna.town