NovelRT

A cross-platform 2D game engine accompanied by a strong toolset for visual novels.

Runssource: GitHubC++MITcommit 7b23d9d5f66d

C++, MIT licensed. The project labels itself: 2d, 2d game engine, c plus plus, cross platform, engine, game, game development and game engine.

NovelRT runs. An Argusic agent installed it in 21 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The NovelRT game engine builds completely with GCC 13, all 408 unit tests pass, and no build errors remain.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.44 (measured)
recorded runs
1
last tested
stars
219
forks
43
open issues
95
watchers
11
size
33 MB
created
last push

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.

Time lost to each failure while testing NovelRT, 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.

  • GCC compilation errors: -Wabi warns about nothing, unused variables, extra semicolons, -Wconversion errors6 minutes
  • Missing X11 development headers (libx11-dev, x11proto-dev, libxcb-*-dev, etc.)5 minutes
  • Missing Vulkan development headers (libvulkan-dev only provided v1.3.275, code requires v1.4+ for VK_KHR_MAINTENANCE_7)3 minutes
  • Missing wayland-scanner binary1 minute
  • CMake 3.28 too old for cmake_policy(VERSION 3.29..3.31) in NovelRTBuildSystem.cmake1 minute
  • Samples abort at runtime due to missing Vulkan GPU driver
Install time
21 minutes
Cold machine to finish
21 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
cmake --build . -j4 exited 0, then ./Tests/Tests exited 0 with 408/408 passed
Model tokens used
245,909
Exact commit tested
7b23d9d5f66d
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.

echo "Total: ~21 minutes"' in /work/repo
 succeeded in 0ms:
Starting time tracking...
Started at approximately 02:27 (shell startup)
Now at 02:48
Total: ~21 minutes
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 2…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 21, "errors": [{"msg": "Mi…
tokens used
245,909

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 6 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

  • Took 21 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 6 2d projects Argusic has installed and timed, NovelRT was the 6th fastest to reach a running state, and 5 of 6 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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.44

Topics (from GitHub)

2d2d-game-enginec-plus-pluscross-platformenginegamegame-developmentgame-enginevisual-novelvisual-novel-engine

Embed the badge

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

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

Questions

Does NovelRT run?
Yes. NovelRT runs. Argusic installed and launched it on a clean machine in 21 minutes, hitting 6 errors on the way, and recorded the session.
How did Argusic test NovelRT?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7b23d9d5f66d. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test NovelRT?
The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does NovelRT take to install?
21 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 NovelRT need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing NovelRT?
6 things broke in the recorded run, and 6 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does NovelRT compare with the alternatives?
Of the 6 2d projects Argusic has installed and timed, NovelRT was the 6th fastest to reach a running state, and 5 of 6 reached one at all.
Where is the evidence for NovelRT?
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.

Discussion