Shorten RGB-split bands to 4px max, per request

GLITCH_STATE_POOL's height values were 10-13px (sized to reliably show
2-3 scanlines within a band); capped to 2-4px thin slivers instead. No
longer tall enough to guarantee scanline overlap, which is fine -- the
shorter height was the explicit ask.

Verified 0 black-corner hits across 228 frames, payload 291KB (down
from 320KB with the taller bands).
This commit is contained in:
poprhythm committed 2026-10-09 18:51:25 -04:00
1 parent eee2125421
commit 40a740f7e4
1 file changed
+13 -13
+13 -13
View File
@@ -393,19 +393,19 @@ GLITCH_STATES_PER_CYCLE = 4
# height) -- see the note above GLITCH_HOLD_TICKS for why that's the only # height) -- see the note above GLITCH_HOLD_TICKS for why that's the only
# part grounded in anything observed rather than invented. # part grounded in anything observed rather than invented.
GLITCH_STATE_POOL = [ GLITCH_STATE_POOL = [
# Scanlines (see _glitch_scanlines below) repeat every 4px, so each # Capped to 4px tall -- thin RGB-split slivers rather than the
# band's height needs to be at least ~9-13px to reliably show 2-3 of # original 10-13px bands. No longer tall enough to reliably show 2-3
# them, regardless of the band's exact vertical alignment against the # scanlines within a given band (that required ~9-13px against
# scanline grid -- much shorter and a band can land entirely between # _glitch_scanlines' 4px repeat), so a band can land entirely between
# two scanline rows and show none at all. # two scanline rows; accepted, since the shorter height was the ask.
(3, 12, -2, 150.0, 19, 11, 2, -60.0), (3, 3, -2, 150.0, 18, 4, 2, -60.0),
(2, 11, 2, 150.0, 20, 12, -3, -60.0), (2, 4, 2, 150.0, 20, 3, -3, -60.0),
(5, 10, -3, 150.0, 17, 13, 1, -60.0), (5, 2, -3, 150.0, 16, 4, 1, -60.0),
(1, 13, 1, 150.0, 21, 10, -2, -60.0), (1, 4, 1, 150.0, 22, 2, -2, -60.0),
(6, 10, 1, 150.0, 14, 12, 3, -60.0), (6, 3, 1, 150.0, 14, 3, 3, -60.0),
(0, 11, 3, 150.0, 20, 10, -1, -60.0), (0, 2, 3, 150.0, 24, 4, -1, -60.0),
(4, 10, -1, 150.0, 12, 13, 2, -60.0), (4, 3, -1, 150.0, 19, 2, 1, -60.0),
(2, 12, -3, 150.0, 22, 10, 1, -60.0), (2, 4, -3, 150.0, 26, 3, 1, -60.0),
] ]
# render.Sequence doesn't loop on its own (see _glitch_scanlines below), so # render.Sequence doesn't loop on its own (see _glitch_scanlines below), so
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.