rbfx

Lightweight Game Engine/Framework in C++17 with WYSIWYG Editor. Experimental C# bindings.

Runs with mockssource: GitHubhomepageC++MITcommit d3e8a4ea89e0

C++, MIT licensed. The project labels itself: 3d engine, 3d graphics, cpp17, csharp, desktop, directx 11, game engine and hot reload.

rbfx runs, with stand-ins for the services it depends on. An Argusic agent installed it in 80 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.

rbfx engine library (libUrho3D.a) and test suite compiled, linked, and executed with Vulkan rendering backend on a headless system

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 53.5 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
53.5 / 100
cost of the verifying run
$0.70 (measured)
recorded runs
2
last tested
stars
1,055
forks
175
open issues
77
watchers
51
size
354 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 rbfx, 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.

  • Missing X11/xcb development headers (libx11-dev, libxcb1-dev) cause GLEW and Vulkan backend compilation failures.20 minutes
  • Missing libdbus-1-dev package prevents building nativefiledialog portal implementation (triggered by URHO3D_TOOLS/URHO3D_EDITOR/URHO3D_PROFILING). Disabled these features.5 minutes
  • Missing uuid-dev package causes linker error (uuid_generate, uuid_unparse).5 minutes
  • Test crash: Server-client scene loader sequence - Context assertion failure (pre-existing issue).
Install time
80 minutes
Cold machine to finish
81 minutes
Errors hit and fixed
4 hit, 3 fixed with no human help
How the result was proved
cmake --build … --target Tests succeeded; ./bin/Debug/Tests ran 119 test cases, 118 passed, 1 failed (pre-existing issue)
Model tokens used
1,640,498
Exact commit tested
d3e8a4ea89e0
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.

5. Created stub `/home/runner/.local/lib/libuuid.a` for missing `libuuid-dev`
**Tests executed**: 119 test cases, 118 passed, 1 failed. The single failure (`SIGABRT` in `Server-…
tokens used
1,640,498
Here's the final report:
**Build succeeded** - CMake configured and built the Tests target (96% engine + test library + test…
1. **Source/CMakeLists.txt** - guarded `install(EXPORT Urho3DTools ...)` with `if (DESKTOP AND URHO…
2. **Source/ThirdParty/CMakeLists.txt** - guarded `add_subdirectory(GLEW)` with `if (NOT UWP AND GL…
3. **Source/Urho3D/RenderAPI/RenderDevice.cpp** - wrapped `x11.display` / `x11.window` access with …
4. Created stub headers for `/tmp/stub-include/{xcb/xcb.h, X11/Xlib.h, uuid/uuid.h}` to satisfy bui…
5. Created stub `/home/runner/.local/lib/libuuid.a` for missing `libuuid-dev`
**Tests executed**: 119 test cases, 118 passed, 1 failed. The single failure (`SIGABRT` in `Server-…

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

  • 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.
  • Took 80 minutes to install, slower than the median of the 4 comparable projects Argusic has measured.
  • Hit 4 errors during setup, 1 of which were not solved.

Of the 5 3d-engine projects Argusic has installed and timed, rbfx was the 5th fastest to reach a running state, and 3 of 5 reached one at all.

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 Runner2/3Did not run20.000.97
Argusic Runner1/3Runs with mocks87.000.70

Topics (from GitHub)

3d-engine3d-graphicscpp17csharpdesktopdirectx-11game-enginehot-reloadimguimobileopenglurho3dweb

Embed the badge

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

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

Questions

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

Discussion