$ show gan74/Yave
Yave is a C++20 Vulkan-based real-time graphics engine paired with a custom ImGui-driven editor and a self-contained core utility library named `y`. The repository is structured as three layers: `y` provides reusable containers, math, concurrency, IO, serialization, and a test framework; `yave` implements the engine itself (Vulkan device/window management, frame graph, render passes, ECS, asset pipeline, physics, animation, and scripting); and `editor` is a full 3D scene editor application with workspaces, widgets, gizmos, importers, thumbnails, and undo/redo. The renderer supports deferred PBR, cascaded shadow maps, TAA, bloom, SSAO/RTAO, RTGI, atmosphere scattering, and tone mapping, and it runs through a declarative frame graph with automatic resource pooling and barrier insertion. The editor is not a separate toy: it provides asset browsing, glTF/image import, material editing, scene outliner, inspector, file system views, performance metrics, GPU profiling, and RenderDoc integration. The engine uses a modern ECS with component groups, async asset pointers, and a serialization framework that supports schema evolution. The `y` library is particularly notable for its clean, high-performance primitives: SSO strings, flat hash maps with SIMD probing, sparse component sets, dependency-aware job system, and a forward/backward-compatible binary serialization layer. Externally, it depends on Vulkan, VMA, Volk, Dear ImGui, JoltPhysics, LuaJIT, tinygltf, stb, Tracy, and spirv_reflect, mostly vendored. While the project is described by its author as a learning/pet engine, the code is generally well-structured and professionally organized. However, it is a single-author codebase with many `Y_TODO` markers, some stubbed platform paths, global device singletons, and an explicit compiler-dependent serialization format. Tests exist mainly for the `y` core containers and math, not for the engine or editor. The repository is active and uses current C++/Vulkan practices, but should be treated as an evolving research-quality engine, not a stable library.
The LLM identified 4 files worth highlighting for reuse:
A self-contained binary serialization framework with compile-time reflection, compiler-aware archive versioning, backward-compatible member skipping, deferred size patching, and polymorphic type support. It solves a recurring data-persistence problem and can be extracted into a new C++ project with minimal adaptation.
A high-performance open-addressing flat hash map using SIMD group probing, tombstone recycling, stateful hashers, and max-probe-length tracking. It is isolated in the core library and demonstrates non-obvious container engineering that can be reused independently.
A dependency-aware task scheduling system with job handles, parallel_for support, and structured waiting semantics. It is self-contained enough to be dropped into other C++ applications and shows careful concurrency design (lock-free-ish task dependencies and thread-pool management).
A reusable binary read/write buffer abstraction used across serialization and asset loading. It is small, isolated, and implements a clean streaming interface with ownership semantics, making it a good candidate for extraction into other C++ projects.