BIOVOID ENGINE Source
Custom game engine / C++

SYSTEMSUNDER THESURFACE.

Biovoid is a ground-up engine project connecting low-level graphics, runtime architecture, and a practical editor into one coherent system.

EDITOR / LIVE BUILD VULKAN + OPENGL
Biovoid Engine editor showing a moon and crate in the viewport, with scene hierarchy, properties, live frame data, and content browser panels
01 / Editor viewport

Authentic running build — captured from the project.

02Graphics backends
11Engine modules
221Project commits
One developer. The whole stack.
01 — Scope

NOT A TECH DEMO.
AN ENGINE SYSTEM.

The work spans the boundaries recruiters care about: graphics APIs, engine architecture, developer tools, data flow, and the discipline to make them operate together.

01

Rendering abstraction

A hand-built RHI keeps high-level rendering independent from the backend, with concrete Vulkan and OpenGL implementations.

Pipelines · buffers · textures · swapchains
02

Render graph

Scene and UI passes declare targets, depth, MSAA, and callbacks before the graph drives execution in a predictable order.

Passes · resources · resolve targets · MSAA
03

Editor tooling

The engine ships with its own scene hierarchy, inspector, content browser, docked layout, editor camera, and live frame data.

Hierarchy · inspector · assets · profiling
04

ECS & persistence

Scenes are composed through an EnTT-based ECS and serialized with FlatBuffers for a data-oriented runtime workflow.

Entities · components · scenes · serialization
05

Native UI system

A custom component layer handles layout, styling, scrolling, tabs, file views, events, and textured UI rendering.

Components · layout · input · text
06

Asset pipeline

Meshes, materials, textures, and shaders move from source assets into GPU-ready resources through dedicated engine systems.

Assimp · shaderc · SPIR-V · materials
02 — Architecture

FROM EVENT
TO PIXEL.

Each layer has a clear responsibility. Platform events become runtime state, scene data becomes render work, and the RHI translates that work to the selected graphics API.

01Platform

Window & input

  • Windows / GLFW
  • Events
  • Frame timing
02World

Runtime & ECS

  • Scenes
  • Components
  • FlatBuffers
03Frame

Renderer

  • Render graph
  • Materials
  • Meshes
04Hardware

RHI backends

  • Vulkan
  • OpenGL
  • GPU resources
A frame, expressed clearly

High-level intent.
Low-level control.

The render graph keeps frame construction readable while the backend owns synchronization, memory, command buffers, pipelines, and targets. That separation makes experimentation possible without hiding the hardware.

EditorClient.cppC++
// Build the scene pass
auto& scenePass = renderGraph.addPass("scene");

scenePass.setCallback([scene] {
  scene->updateAllPrimitiveSceneInfos();
  scene->render();
});

scenePass.setMsaa(msaaSamples);
scenePass.setOutput("scene-raw", target);
scenePass.setDepthStencil();
03 — Why it matters
“I built Biovoid to understand—and own—the entire path from scene data to pixels.”

This project is evidence of how I approach hard technical work: trace the system end to end, design strong boundaries, work close to the platform, and build the tools that make the result usable.

I’m looking for engine, rendering, or systems work where depth matters and where I can contribute across layers—not just inside one isolated box.

01Modern C++02Vulkan03OpenGL04CMake05EnTT 06FlatBuffers07GLSL08SPIR-V09Assimp10GLFW
Available for the right team

NEED SOMEONE WHO
CAN CROSS THE
ABSTRACTION BOUNDARY?

Engine programming · Rendering · Systems