vulkan-renderer
A new, render-graph based 3D game engine for Linux and Windows using C++20 and Vulkan API 1.3 (in early development)
Runssource: GitHubhomepageC++MITcommit ac0b20fd80b9
C++, MIT licensed. The project labels itself: 3d engine, 3d game engine, cplusplus, cplusplus 20, engine, framegraph, game development and game engine.
vulkan-renderer runs. An Argusic agent installed it in 21 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
CMake configuration succeeds with all dependencies downloaded via FetchContent, project builds to completion producing library, test binary (47 tests, 45 pass), and example binary (segfaults without Vulkan ICD).
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- X11 development headers (X11/Xlib.h, X11/X.h etc.) missing from container5 minutes
- Numerous xcb extension headers and libs missing (xcb/randr.h, composite.h, etc.)4 minutes
- FindX11 failed to locate XKB headers (X11/extensions/XKB.h)3 minutes
- glslangValidator (shader compiler) not found on system2 minutes
- GLFW required Wayland but wayland-scanner not present on system1 minute
- GL/gl.h not found when compiling against glfw3.h1 minute
- Install time
- 21 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- cd /work/repo/build && LD_LIBRARY_PATH=/tmp/sysroot/usr/lib/x86_64-linux-gnu ./tests/inexor-vulkan-renderer-tests exited 0, 45 passed, 2 failed (pre-existing)
- Model tokens used
- 132,792
- Exact commit tested
- ac0b20fd80b9
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
[----------] 1 test from CubeCollision (0 ms total) [----------] Global test environment tear-down [==========] 1 test from 1 test suite ran. (0 ms total) [ PASSED ] 0 tests. [ FAILED ] 1 test, listed below: [ FAILED ] CubeCollision.CollisionCheck 1 FAILED TEST Press Enter to close Now I have all the evidence. Let me compile the final report. tokens used 132,792 Now I have all the evidence. Let me compile the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 21 minutes, faster than the median of the 4 comparable projects Argusic has measured.
- Recovered from all 6 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 5 3d-engine projects Argusic has installed and timed, vulkan-renderer was the 3rd fastest to reach a running state, and 3 of 5 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.17 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.29 |
Topics (from GitHub)
3d-engine3d-game-enginecpluspluscplusplus-20engineframegraphgame-developmentgame-enginegamedevgraphics-programmingmit-licenseopen-sourcerendergraphrenderingvulkanvulkan-apivulkan-enginevulkan-game-enginevulkan-renderer
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/vulkan-renderer)Questions
- Does vulkan-renderer run?
- Yes. vulkan-renderer runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test vulkan-renderer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ac0b20fd80b9. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test vulkan-renderer?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does vulkan-renderer take to install?
- 21 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does vulkan-renderer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing vulkan-renderer?
- 6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does vulkan-renderer compare with the alternatives?
- Of the 5 3d-engine projects Argusic has installed and timed, vulkan-renderer was the 3rd fastest to reach a running state, and 3 of 5 reached one at all.
- Where is the evidence for vulkan-renderer?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.