If you want to go through the codebase with neovim do cmake -B build -G Ninja to generate the compilation database it needs for code-completion.
Depending on the IDE you want use, do cmake -B build -G followed by the generator, refer to https://cmake.org/cmake/help/latest/manual/cmake-generators.7.html#manual:cmake-generators(7) for a list of generators. I haven't tested all configurations and this is a pretty rough build system right now so be nice.
After that do cmake --build ./build to build the project. Currently only Debug config is working.
To run the exe, go into Binaries/App/Debug/App.exe
- Architecture Refactor: The engine started as a vulkan learning testbed but is growing past that now as my understanding matures. To accommodate more complex features the architecture will need to change.
- PBR System
- Physics Simulation
- Scene Hierarchy
- Runtime Shader Recompilation
- Event System to further separate concerns
- Multithreading
First implementation of PBR. Primitive material system that I'm going to be moving to bindless soon. Next big plays are descriptor indexing and shadow maps. Hoping to learn a lot more about render passes and framebuffers with shadow maps.
After a year of typescript and C# it feels good to get some real work done in C++ and Vulkan. Bridge Engine now supports loading and texturing multiple models, and up to 16 lights in the scene. The codebase is very scrappy but that's a symptom of my Vulkan learning journey. The architecture will improve as time passes and my understanding of how the different parts of Vulkan work together to produce the effects of more complex modern computer graphics applications.
