lovr
Lua Virtual Reality Framework
Runssource: GitHubhomepageCMITcommit 88fa3d43698f
C, MIT licensed. The project labels itself: game engine, gamedev, lovr, lua, oculus, oculus quest, openvr and openxr.
lovr runs. An Argusic agent installed it in 15 minutes and hit 8 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
LOVR 0.19.0 builds from source and boots with Lavapipe software Vulkan; all 121 module tests pass (audio skips with 'no backend' message); binary + shared libs live in build/bin/
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.
- X11 development headers not installed in container3 minutes
- Missing nested git submodules (phonon deps, enet)2 minutes
- CMake couldn't find X11 headers/libs2 minutes
- Vulkan driver not available (vkCreateInstance failed)2 minutes
- Missing zlib1g-dev for phonon/submodule zlib1 minute
- Runtime missing shared libraries (libglfw, libluajit, etc.)1 minute
- Install time
- 15 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 8 hit, 8 fixed with no human help
- How the result was proved
- cd /work/repo && timeout 90 bash -c 'LD_LIBRARY_PATH=build/bin VK_ICD_FILENAMES=build/bin/lvp_icd.json build/bin/lovr test' returned 121 passes, 0 errors, exit 0
- Model tokens used
- 382,558
- Exact commit tested
- 88fa3d43698f
- 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.
- The `lovr-http` plugin failed (needs `curl/curl.h` — a system -dev package we could download bu…
- Set up Mesa Lavapipe (software Vulkan driver) by extracting `mesa-vulkan-drivers` and pointing …
- Ran the full test suite: **121 passes, 0 errors**
**Errors encountered & fixes:**
- Missing X11 -dev headers → downloaded & extracted libx11-dev, libxcb1-dev, libxau-dev, libxdmcp…
- Missing nested phonon deps (pffft, mysofa, zlib) → `git submodule update --init --recursive`
- Missing enet submodule → plugin submodule init
- Linker couldn't find X11 libs → added `-L` via CMAKE_EXE_LINKER_FLAGS
- Runtime couldn't find shared libs → copied .so files into `bin/`
- Vulkan driver not available → installed Mesa Lavapipe (software renderer) via ICD JSON
- Audio module fails to init ("no backend") → expected in a headless container
- `lovr-http` plugin build failed → missing `curl/curl.h` (optional plugin, doesn't affect main b…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 15 minutes.
- Recovered from all 8 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)
game-enginegamedevlovrluaoculusoculus-questopenvropenxrvirtual-realityvr
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/lovr)Questions
- Does lovr run?
- Yes. lovr runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 8 errors on the way, and recorded the session.
- How did Argusic test lovr?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 88fa3d43698f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test lovr?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does lovr take to install?
- 15 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 lovr need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing lovr?
- 8 things broke in the recorded run, and 8 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for lovr?
- 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.