Fyrox
3D and 2D game engine written in Rust
Runssource: GitHubhomepageRustMITcommit dc354e0d9827
Rust, MIT licensed. The project labels itself: 3d, 3d engine, engine, game development, game engine, gamedev, gui and rendering.
Fyrox runs. An Argusic agent installed it in 10.2 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Fyrox 2.0.0-rc.1 Rust game engine compiles with rustc 1.98.1 (stable), all 28 test suites pass (0 failures), and CLI tools (fyrox-template, fyroxed) print help correctly. The project-manager needs a GPU and was not tested. ALSA audio output was enabled via extracted libasound2-dev headers/libraries.
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.
- alsa-sys build failed: system libasound2-dev package not installed3 minutes
- fyrox-core-derive test `doc_comments` failed: doc comment format changed in Rust 1.98 (multiline doc strings now include literal newlines)0.5 minutes
- Install time
- 10 minutes
- Cold machine to finish
- 19 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cargo test exited 0: 28 test suites, 0 failures across all workspace members (fyrox-animation: 11 passed, fyrox-autotile: 19, fyrox-core: 166, fyrox-core-derive: 28+6 doc-tests, fyrox-graph: 4, fyrox-graphics: 3, fyrox-graphics-gl: 1, fyrox-graphics-wgpu: 4, fyrox-impl: 156 passed/3 ignored, fyrox-material: 1, fyrox-math: 136, fyrox-resource: 49, fyrox-sound: 4, fyrox-ui: 81), plus doc-tests (fyrox-ui: 116 passed) and integration tests. fyroxed --help and fyrox-template --help both printed usage correctly. fyrox-project-manager exits with BadConfig (no GPU in container) which is expected.
- Model tokens used
- 89,364
- Exact commit tested
- dc354e0d9827
- 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.
-p, --project-directory <PROJECT_DIRECTORY> Project root directory -s, --scenes <SCENES> List of scenes to load -n, --named-objects -h, --help Print help -V, --version Print version All binaries compile and respond correctly. Let me summarize the exec /bin/sh -lc '. "$HOME/.cargo/env" && cd /work/repo && cargo build --profile github-ci 2>&1 | tail -… All done. Let me clean up and construct the final report. 2026-09-27T16:35:18.617904Z ERROR codex_core::tools::router: error=exec_command failed: CreateProce… tokens used 89,364
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 10.2 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.
- Licensed MIT, as reported by its host.
What did not, or is not known
- 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)
3d3d-engineenginegame-developmentgame-enginegamedevguirenderingrustrust-lang
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fyrox)Questions
- Does Fyrox run?
- Yes. Fyrox runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test Fyrox?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc354e0d9827. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test Fyrox?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does Fyrox take to install?
- 10.2 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 Fyrox need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing Fyrox?
- 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 Fyrox?
- 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.