Bzzrt 1.1.1

Bzzrt 1.1.1 adds the app icon and fixes a few bugs. The tests and measurements are unchanged from 1.1.0.

⬇️ Downloads

System	File	Start
🪟 Windows 10/11 (x64)	bzzrt-1.1.1-windows-x64.zip	double-click vrrdiag.exe on the monitor you want to test
🐧 Linux (x86_64, glibc 2.34+)	bzzrt-1.1.1-linux-x86_64.tar.gz	./vrrdiag-launch
🏔️ Arch Linux and derivatives (x86_64)	bzzrt-1.1.1-1-x86_64.pkg.tar.zst	sudo pacman -U the link, then start Bzzrt from the app menu or run bzzrt
🍎 macOS 12+ (Apple silicon)	bzzrt-1.1.1-macos-arm64.zip	open Bzzrt.app (first time: right-click → Open; macOS 15: System Settings → Privacy & Security → Open Anyway)

Check the files against SHA256SUMS.

🖼️ App icon

• Windows: vrrdiag.exe and its window have the Bzzrt icon.
• macOS: Bzzrt.app has the Bzzrt icon.
• Linux: the app-menu entry uses the new icon. Run ./package-linux.sh --install again to update it.

🐛 Fixes

• --double-frames could freeze on Linux (Vulkan, Wayland or X11). When a repeated frame was already late, the app rendered it but never showed it. A few of those could stall the test. Late repeats are now skipped before they are rendered. The direct KMS mode, which the Linux results so far were measured with, was not affected.
• Bad command-line numbers are rejected. Values such as --fps nan, an empty value or a negative --duration used to slip through; out-of-range --seed, --gpu, --pattern and --spike-frames values are now reported instead of misbehaving.
• CSV logs keep display times after skipped frames. When frames were skipped (for example while the window was minimized), the next frames could lose their display_time_s values.
• Smaller fixes: an unexpected Vulkan error now ends the run cleanly instead of rendering to an invalid image, and the direct KMS mode no longer leaks memory when it fails to start.

The note from 1.0.0 still applies: the macOS build has not yet been tested on a real Mac with an Adaptive-Sync monitor.