QuakeSpasm

Played sessions

Testing is done with Walnut's rating tool (walnut-rate, planned): how ratings are made and submitted.

Download all sessions as CSV (one row per session, the aspects as columns)

Rating history

The rating on each version it was tested on, newest first: each row is rated from that version's sessions alone, under the newest rules those sessions have the data for.

Scripted benchmarks

Not rated: tests of driver and game changes. A script plays the same scene on the PS3 again and again (the desktop stopped, vsync off) to compare two builds of the game or of the graphics driver. The numbers say which build is faster; they never feed the medal.

How the script plays it: QuakeSpasm 0.96.3 (Debian) with the Quake shareware data (quake-shareware from make game-data: /usr/share/games/quake/id1/pak0.pak): timedemo of the shareware's demo1, fullscreen 1920x1080. -nopackedpixels: 0.96.3's packed-pixels lightmaps have wrong colours on big-endian (quakespasm issue #114; nv30 has no 10-bit format anyway). It doesn't quit after a timedemo: stopped at the result line. Base keeps GLSL on (alias models; gamma stays 1.0, so the full-screen gamma pass doesn't run); noglsl is GL 1.x only, glslgamma turns the gamma pass on (it runs off 1.0 only). +timedemo on the command line doesn't work: the shareware's quake.rc runs "startdemos demo1 demo2 demo3" after the command line's commands and the attract loop replaces the timedemo. So a quake.rc of ours in the user's id1 (~/.quakespasm/id1, searched before the system's pak0.pak) runs the timedemo instead. (A -game directory would do it too, but the shareware refuses those.) Steady state: the timedemo repeated in one session (PASSES=1; client.sh counts the passes that start 54 s or more after the first, and stops the game once they cover ~120 s: ~5 warm-up passes of ~13 s, then ~9 measured). QuakeSpasm has no hook at a demo's end (Host_EndGame skips the attract loop in a timedemo and CL_FinishTimeDemo clears cls.timedemo), so quake.rc loops by frame count: `bench` starts the timedemo, waits 1100 host frames (a wait is one frame; demo1's timedemo is 969 frames, about 2 s idle at the console after it) and starts the next. A timedemo started before the last one ended would print a "-1 frames" line: FPS_RE wants a line starting with a count. fps= stays the first pass's (the run as before); steady is the median of the measured passes.

Conditions: what a variant adds to the recipe (its environment switches) and what ran alongside (the stall recorder, a profiler). Length: "warm-up + 120 s" is a steady-state run, which leaves out a 60 s warm-up and measures 120 s or more; "whole run" counted everything from the start, the way runs before 2026-10-17 did. Rows marked invalid or not comparable say why.