Overload runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 9 errors on the way, and recorded the session.

How did Argusic test Overload?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit d013cf05a90b. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test Overload?

The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does Overload take to install?

15 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 Overload need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing Overload?

9 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 Overload?

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.

Overload

3D game engine with lua scripting

Runs with mockssource: GitHub homepageC++MITcommit d013cf05a90b

C++, MIT licensed. The project labels itself: 3d engine, 3d graphics, c plus plus, cpp, game editor, game engine, gamedev and graphics.

Overload runs, with stand-ins for the services it depends on. An Argusic agent installed it in 15 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Overload v1.9 builds completely on Linux with GCC 13, producing OvGame (231 MB) and OvEditor (266 MB) binaries; OvGame runs headlessly via Xvfb, initializes OpenGL 4.5 with Mesa llvmpipe software renderer, and exits cleanly; OvEditor launches, initializes OpenGL, and stays up.
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 86 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 86 / 100
cost of the verifying run: $0.21 (measured)
recorded runs: 2
last tested: 2026-10-03
stars: 2,489
forks: 289
open issues: 112
watchers: 39
size: 55 MB
created: 2019-06-13
last push: 2026-09-20

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-03. 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.

Time lost to each failure while testing Overload, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

X11/Xlib.h: No such file or directory — missing X11 development headers5 minutes
GL/gl.h: No such file or directory — missing OpenGL development headers3 minutes
cannot find -lGL, cannot find -lX11 — linker missing .so symlinks for libGL and libX112 minutes
clang++: not found — premake5 Lua generates Makefiles that invoke clang/clang++ by default on Linux1 minute
KHR/khrplatform.h: No such file or directory1 minute
X11/extensions/Xrender.h: No such file or directory — cascading X11 header dependency1 minute

Install time: 15 minutes
Cold machine to finish: 18 minutes
Errors hit and fixed: 9 hit, 9 fixed with no human help
How the result was proved: timeout 5 ./Build/Debug/Builder/Debug/OvGame ran on :99 via Xvfb, initialized OpenGL 4.5 Core Profile with Mesa llvmpipe (LLVM 20.1.2), printed driver info (Vendor=Mesa, Hardware=llvmpipe, Version=4.5), exited cleanly with code 0. timeout 15 ./Build/Debug/OvEditor with mocked zenity initialized OpenGL identically and stayed up until timeout (exit 124, not a crash).
Model tokens used: 207,785
Exact commit tested: d013cf05a90b
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
Behaviour against real services: this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

# Quick check: does ldd show all linked for both?
ldd /work/repo/Build/Debug/Builder/Debug/OvGame 2>&1 | grep "not found"
ldd /work/repo/Build/Debug/OvEditor 2>&1 | grep "not found"' in /work/repo
 exited 1 in 0ms:
Start time vs now context: started ~13:41, now
1791035916
Here's the final result based on everything I observed:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 15, "e…
tokens used
207,785
Here's the final result based on everything I observed:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 15, "e…

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

Installed in 15 minutes.
Recovered from all 9 errors without a human stepping in, which says the failures are documented well enough to solve.
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

Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

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 with mocks	92.00	0.21	2026-10-03 13:59 UTC
Argusic Runner	1/3	Unverified	80.00	0.19	2026-10-03 13:33 UTC

Topics (from GitHub)

3d-engine 3d-graphics c-plus-plus cpp game-editor game-engine gamedev graphics graphics-engine imgui linux lua opengl physically-based-rendering rendering-engine windows

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/Overload.svg)](https://argusic.com/subject/overload)

Questions

Does Overload run?: Overload runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 15 minutes, hitting 9 errors on the way, and recorded the session.
How did Argusic test Overload?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit d013cf05a90b. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test Overload?: The run that produced this verdict cost $0.21: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does Overload take to install?: 15 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 Overload need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing Overload?: 9 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 Overload?: 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.