Post

Brandon Jones
@toji.dev

Me: "Yeah, things are mostly looking good, but I never figured out why the compositor just drops a frame once in a while?" Coworker: "Is it because of this line in your demo that says drop every 200th frame?" Me: "THE. F#@&ING. WHAT???"

EndMalcompetence
@endmalcompetence.bsky.social

🤔 Could it ever have been useful in an inverted "skip 199" sense? Like to speed up a repro test by dropping frames? Then perhaps somebody edited it to "turn it off", and misread it as a boolean feature flag, and changed it from !== to == .

Brandon Jones
@toji.dev

The "somebody" in this case is me. I'm the only one that worked on this code. And yes, I imagine at some point I added it to skip every other frame to test some WebXR reproduction, then dropped it to something lower to test occasional frame drops, then promptly forgot all about it. 😓

0 reposts1 like

No replies yet.