doriax
Game engine for 2D and 3D projects with entity component system (ECS) and data-oriented design
Runssource: GitHubhomepageC++MITcommit 575ef40d0be0
C++, MIT licensed. The project labels itself: cross platform, data oriented design, directx, ecs, entity component system, game dev, game development and game engine.
doriax runs. An Argusic agent installed it in 32 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Doriax editor builds from source and launches on the virtual display, staying alive with a mapped 1280x720 window; the shaders CLI generates a real compiled mesh_glsl410.sdat containing an embedded GLSL source block.
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 60 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.
- System lacked CURL/X11/GL/dbus/wayland dev packages and no root install possible10 minutes
- Linker could not find libGL/libX11/libXi/libXcursor/libwayland/libdbus and static curl/dbus pulled missing gss/psl/ssh/systemd symbols7 minutes
- CMake FindX11 uses X11_X11_INCLUDE_PATH var and Xrandr needs Xrender target4 minutes
- wayland-scanner missing and nfd needed xdg-foreign protocol3 minutes
- Compiler lacked GL/curl/dbus include paths3 minutes
- editor GUI failed at NFD_Init: /usr/bin/dbus-launch not present3 minutes
- Install time
- 32 minutes
- Cold machine to finish
- 33 minutes
- Errors hit and fixed
- 6 hit, 6 fixed with no human help
- How the result was proved
- build-make/doriax-editor --help returned usage; doriax-editor shaders --out /tmp/shaderout --format binary --backend opengl --shader mesh exited 0 and produced a 4429-byte mesh_glsl410.sdat with SDAT magic and GLSL #version 410 payload; GUI launched under dbus-run-session and xwininfo showed a mapped 1280x720 window titled 'MyDoriaxProject - Doriax Engine' that stayed alive
- Model tokens used
- 240,179
- Exact commit tested
- 575ef40d0be0
- 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.
- Launch succeeded: GUI launched on virtual display under `dbus-run-session`, window mapped as `MyD… - Real behavior: `doriax-editor shaders --out /tmp/shaderout --backend opengl --shader mesh` genera… - No tests exist in the project's own source (only bundled third-party yaml-cpp gtest fixtures), so… Errors encountered and fixed (all via a local `prefix/` extracted from apt `.deb` packages, since n… tokens used 240,179 All verification complete. Let me compile the final report. - Build succeeded: `doriax-editor` (24.3MB), `libdoriax.so` (17.1MB), `shadercompiler` all built vi… - Launch succeeded: GUI launched on virtual display under `dbus-run-session`, window mapped as `MyD… - Real behavior: `doriax-editor shaders --out /tmp/shaderout --backend opengl --shader mesh` genera… - No tests exist in the project's own source (only bundled third-party yaml-cpp gtest fixtures), so… Errors encountered and fixed (all via a local `prefix/` extracted from apt `.deb` packages, since n…
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.
- 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.
What did not, or is not known
- Took 32 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
Of the 13 cross-platform projects Argusic has installed and timed, doriax was the 11th fastest to reach a running state, and 10 of 13 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.28 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.41 |
Topics (from GitHub)
cross-platformdata-oriented-designdirectxecsentity-component-systemgame-devgame-developmentgame-enginegamedevmetalapiopenglopengl-es
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/doriax)Questions
- Does doriax run?
- Yes. doriax runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 6 errors on the way, and recorded the session.
- How did Argusic test doriax?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 575ef40d0be0. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test doriax?
- The run that produced this verdict cost $0.28: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does doriax take to install?
- 32 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 doriax need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing doriax?
- 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 doriax compare with the alternatives?
- Of the 13 cross-platform projects Argusic has installed and timed, doriax was the 11th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for doriax?
- 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.