ezEngine
An open source C++ game engine.
Runssource: GitHubhomepageC++MITcommit 4fd77fbc2bc1
C++, MIT licensed. The project labels itself: 3d game engine, 3d graphics, c plus plus, game engine and gamedev.
ezEngine runs. An Argusic agent installed it in 60 minutes and hit 10 errors on a clean machine with no GPU, and the whole session was recorded.
EzEngine non-renderer libraries compile and link on Linux, three unit-test suites pass (CoreTest and ToolsFoundationTest fully, FoundationTest 24/25 with one pre-existing Process test failure), and two CLI tools (ezArchiveTool, ezTexConv) launch successfully.
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 98 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.
- Missing X11 dev headers (X11/X.h, XKBlib.h, extensions/XKB.h, extensions/Xrandr.h etc)15 minutes
- Missing libfreetype-dev headers5 minutes
- Missing libvulkan-dev (Vulkan_INCLUDE_DIR/Vulkan_LIBRARY)5 minutes
- Pre-existing Vulkan 1.3.275 API incompatibility (VK_KHR_ -> VK_EXT_ rename, swapchain maintenance features)5 minutes
- No root access - system packages cannot be installed, used .deb extraction workaround5 minutes
- Missing uuid/uuid.h headers3 minutes
- Install time
- 60 minutes
- Cold machine to finish
- 62 minutes
- Errors hit and fixed
- 10 hit, 9 fixed with no human help
- How the result was proved
- ninja -j4 built FoundationTest/CoreTest/ToolsFoundationTest; ran each with LD_LIBRARY_PATH=. and captured results: FoundationTest 'Tests failed: 1. Tests passed: 24' (pre-existing Process sub-test), CoreTest 'All tests passed', ToolsFoundationTest 'All tests passed'; ezTexConv reported usage text confirming it starts
- Model tokens used
- 723,281
- Exact commit tested
- 4fd77fbc2bc1
- 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.
FoundationTest: Tests failed: 1. Tests passed: 24 CoreTest: All tests passed. ToolsFoundationTest: All tests passed. NON-RENDERER APPLICATIONS: 2 The work is complete. Let me produce the final report. tokens used 723,281 The work is complete. Let me produce 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 60 minutes.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Hit 10 errors during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ezengine)Questions
- Does ezEngine run?
- Yes. ezEngine runs. Argusic installed and launched it on a clean machine in 60 minutes, hitting 10 errors on the way, and recorded the session.
- How did Argusic test ezEngine?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4fd77fbc2bc1. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test ezEngine?
- The run that produced this verdict cost $0.74: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ezEngine take to install?
- 60 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 ezEngine need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ezEngine?
- 10 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for ezEngine?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.