kohi

A game engine made as part of the Kohi Game Engine series on YouTube (and Twitch!), where we make a game engine from the ground up using C and Vulkan.

Runssource: GitHubhomepageCApache-2.0commit 34e51506f808

C, Apache-2.0 licensed. The project labels itself: engine, game, game development, game engine, gamedev, kohi, linux and macos.

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

12 shared libraries and executables built: libkohi.core.so, libkohi.runtime.so, libkohi.plugin.audio.openal.so, libkohi.plugin.renderer.vulkan.so, libkohi.plugin.ui.kui.so, libkohi.plugin.utils.so, libtestbed.klib.so, kohi.tools, kohi.core.tests, kohi.runtime.tests, testbed.kapp

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.42 (measured)
recorded runs
2
last tested
stars
1,524
forks
116
open issues
0
watchers
39
size
461 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 kohi, 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-specific compilation errors (-Wgnu-folding-constant, -Werror=inline, -Wno-cast-function-type-mismatch, etc)5 minutes
  • Missing assimp development headers and shared library (plus libdraco8, libpugixml1v5, libminizip1t64 deps)3.5 minutes
  • Missing X11 and xkbcommon development headers/libraries3 minutes
  • KINLINE macro caused multiple definition linker errors with -fgnu89-inline3 minutes
  • No clang compiler available (only gcc)2 minutes
  • Missing OpenAL development headers and libraries1.5 minutes
Install time
25 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
10 hit, 10 fixed with no human help
How the result was proved
make all-debug exited 0; kohi.core.tests: 41 passed, 9 failed; kohi.runtime.tests: 1 passed, 0 failed; kohi.tools binary runs and shows usage; testbed.kapp generates expected 'Failed to initialize Vulkan' error (no GPU in container)
Model tokens used
387,674
Exact commit tested
34e51506f808
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

  usage:  tools <mode> [arguments...]
  modes:
    buildshaders -  Builds shaders provided in arguments. For example,
                    to compile Vulkan shaders to .spv from GLSL, a list of filenames
                    should be provided that all end in <stage>.glsl, where <stage> is
                    replaced by one of the following supported stages:
                        vert, frag, geom, comp
                    The compiled .spv file is output to the same path as the input file.
Alright, it's time to produce the final report. Let me compile everything.
tokens used
387,674
Alright, it's time to produce the final report. Let me compile everything.

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 24.5 minutes.
  • Recovered from all 10 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.
  • Measured 2 times, so the result is not a one-off.

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 Runner2/3Runs100.000.42
Argusic Runner1/3Runs100.000.95

Topics (from GitHub)

enginegamegame-developmentgame-enginegamedevkohilinuxmacosvulkanwindows

Embed the badge

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

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

Questions

Does kohi run?
Yes. kohi runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 10 errors on the way, and recorded the session.
How did Argusic test kohi?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 34e51506f808. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test kohi?
The run that produced this verdict cost $0.42: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does kohi take to install?
24.5 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 kohi need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing kohi?
10 things broke in the recorded run, and 10 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for kohi?
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