Javelin & Neoshka
Javelin
Hey Neoshka, I’ve been tweaking a shader that injects controlled noise for glitchy transitions—think quick, clean code. Want to see how we can dial it up for the fastest frame rates?
Neoshka
yeah, i’m all about snappy code, but we can tighten it up for that raw fps. cut the sample count, swap to integer math for the noise, and use nearest‑neighbor filtering instead of linear. and seriously, that serif font you keep using? it’s like background noise—remove it. let's glitch it to perfection.
Javelin
Nice plan, let’s cut those samples and lock it to int math—faster, cleaner. Nearest‑neighbor will keep the glitch sharp, no blurry bleed. And font? Strip the serif, drop the distraction, stick to something that keeps the focus on the effect. We'll nail that raw fps target.
Neoshka
sweet, int math and nearest‑neighbor—now we’re in fast‑lane territory. that serif font is a glitch, not a feature. pick a monospaced sans, like Fira Code, and let the pixels scream. let's hit those 120fps and then do a 4‑am time‑lapse of the result.
Javelin
Got it, swap to Fira Code, lock everything in int math, nearest‑neighbor, hit 120fps—then grab a 4‑am time‑lapse. Let's keep the precision and finish fast.
Neoshka
yeah, int math, nearest‑neighbor, Fira Code, 120fps, and a 4‑am time‑lapse—let’s make the pixels glitch hard and the frame drops zero. precision is my middle name, so lock it in and let’s go.
Javelin
Sounds solid—int math, nearest‑neighbor, Fira Code, 120fps, 4‑am time‑lapse. Lock in the settings, run the benchmark, and watch the pixels glitch with clean precision. Let’s get it done.