macroquad
Cross-platform game engine in Rust.
Runssource: GitHubRustApache-2.0commit 8d602d3f8ebb
Rust, Apache-2.0 licensed. The project labels itself: android, game engine, ios, rust and wasm.
macroquad runs. An Argusic agent installed it in 26 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
macroquad v0.4.16 builds, all 14 unit/integration tests pass individually when filtered, and 5 example binaries run successfully on X11 via Xvfb with a virtual display.
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.
- cargo test --test coroutine_pause: multi-test binary crashes with free(): invalid pointer when >1 X11-dependent test runs in same process5 minutes
- Rust toolchain not installed3 minutes
- cargo test --test coroutine_pause: 2 tests panicked with 'NATIVE_DISPLAY already set'2 minutes
- cargo run --example window_conf fails: needs Wayland (XDG_RUNTIME_DIR not set)
- Install time
- 26 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- cargo test --lib: 7 passed; cargo test --test back_to_the_future 1 passed; cargo test --test back_to_the_future_coroutines 1 passed; cargo test --test coroutine_pause (each test filtered individually) 3 passed; cargo test --test coroutine_values (each test filtered individually) 2 passed; timeout 5 cargo run --example basic_shapes launched via Xvfb and ran until timeout; timeout 5 cargo run --example events, input_keys, text, texture all launched and ran
- Model tokens used
- 99,792
- Exact commit tested
- 8d602d3f8ebb
- 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.
Now I have all the data. Let me compile the final result
exec
/bin/sh -lc 'cd /work/repo && . "$HOME/.cargo/env" && echo "=== RUNNING coroutine_manual_poll alone…
succeeded in 295ms:
=== RUNNING coroutine_manual_poll alone ===
Running tests/coroutine_pause.rs (target/debug/deps/coroutine_pause-ceaee254f1499e80)
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 3 filtered out; finished in 0.00s
The test run is complete. Let me compile the final report.
tokens used
99,792
The test run is complete. Let me compile 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.
- Recovered from all 4 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Took 26 minutes to install, slower than the median of the 12 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 13 android projects Argusic has installed and timed, macroquad was the 13th 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/macroquad)Questions
- Does macroquad run?
- Yes. macroquad runs. Argusic installed and launched it on a clean machine in 26 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test macroquad?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8d602d3f8ebb. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test macroquad?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does macroquad take to install?
- 26 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 macroquad need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing macroquad?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does macroquad compare with the alternatives?
- Of the 13 android projects Argusic has installed and timed, macroquad was the 13th fastest to reach a running state, and 10 of 13 reached one at all.
- Where is the evidence for macroquad?
- 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.