OpenTTD
OpenTTD is an open source simulation game based upon Transport Tycoon Deluxe
Runssource: GitHubhomepageC++NOASSERTIONcommit ed04d336ed9d
C++, NOASSERTION licensed. The project labels itself: game, isometric, openttd, sandbox and simulation.
OpenTTD runs. An Argusic agent installed it in 35 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
OpenTTD dedicated server compiled from source, started with OpenGFX-8.0 graphics, generated a map, and accepted network connections on port 3979; the test suite passed all 2145 assertions in 94 test cases.
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 100 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 -dev packages (libsdl2-dev, zlib1g-dev, libpng-dev, liblzma-dev, libcurl-dev, libfreetype-dev, libfontconfig-dev, libharfbuzz-dev, libicu-dev) required for full desktop build3 minutes
- No graphics/sound/music base sets present (original TTD files require CD-ROM)1 minute
- Install time
- 35 minutes
- Cold machine to finish
- 35 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- openttd_test exited 0 with 'All tests passed (2145 assertions in 94 test cases)'; dedicated server printed 'Map generated, starting game' and 'Listening on 127.0.0.1:3979'
- Model tokens used
- 179,922
- Exact commit tested
- ed04d336ed9d
- 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.
All work is complete. Here's the summary: **Build**: Compiled `openttd` (dedicated server) and `openttd_test` from source using `-DOPTION_DED… **Tests**: The `openttd_test` binary passed all 2145 assertions across 94 test cases. **Dedicated server**: Started successfully with OpenGFX graphics (downloaded from cdn.openttd.org),… ``` tokens used 179,922 All work is complete. Here's the summary: **Build**: Compiled `openttd` (dedicated server) and `openttd_test` from source using `-DOPTION_DED… **Tests**: The `openttd_test` binary passed all 2145 assertions across 94 test cases. **Dedicated server**: Started successfully with OpenGFX graphics (downloaded from cdn.openttd.org),… ```
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 35 minutes.
- Recovered from all 2 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.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Its license file could not be classified automatically, so check it yourself before using it.
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/openttd)Questions
- Does OpenTTD run?
- Yes. OpenTTD runs. Argusic installed and launched it on a clean machine in 35 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test OpenTTD?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed04d336ed9d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test OpenTTD?
- The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does OpenTTD take to install?
- 35 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 OpenTTD need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing OpenTTD?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for OpenTTD?
- 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.