ursina

A 3D and 2D game engine for Python

Runssource: GitHubhomepagePythonMITcommit 807384a495a9

Python, MIT licensed. The project labels itself: 3d game engine, game development, game engine and python.

ursina runs. An Argusic agent installed it in 10 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Ursina 8.2.0 installed and runs on Python 3.12.3 via Panda3D 1.10.16: package imports, Ursina() window creation, Entity creation, procedural mesh generation, texture loading, math utilities, color system, colliders, Text/Button prefabs, and the Panda3D render loop all function correctly on Xvfb display :99.

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.04 (measured)
recorded runs
2
last tested
stars
2,610
forks
358
open issues
44
watchers
51
size
31 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.

Install time
10 minutes
Cold machine to finish
4 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
python3 -c 'from ursina import *; app = Ursina(borderless=False, ...); Entity(model="cube",color=color.orange); app.run()', output showed 'application successfully started' and '=== QUITTING ===' from userExit; additionally comprehensive import/instantiation/entity/math/texture/model/collider test passed with exit code 0
Model tokens used
173,546
Exact commit tested
807384a495a9
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.

- Entity creation, transforms (position, rotation, scale), color system
- All procedural models: Quad, Cube, Plane, Circle, Cone, Cylinder, Capsule, Grid
- Math utilities: `lerp`, `distance`, `clamp`, `distance_2d`
- Color utilities: `Color`, `hsv`, `rgb`
- Texture loading (`load_texture('noise')`)
- Entity duplication
- Colliders: BoxCollider, SphereCollider
- Text, Button, Sky, DirectionalLight
- Sequences, invoke, Func, Wait
- Panda3D render loop started successfully ("application successfully started")
- panda3d-gltf integration verified
**No errors found** that needed fixing. All audio warnings (ALSA, OpenAL) are expected in a headles…

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 10 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, 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.
  • A quick evaluation: it was running 10 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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.04
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

3d-game-enginegame-developmentgame-enginepython

Embed the badge

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

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

Questions

Does ursina run?
Yes. ursina runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test ursina?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 807384a495a9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test ursina?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does ursina take to install?
10 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 ursina need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing ursina?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for ursina?
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