⚡ Live Stream

[Jayden Collins]

Hey everyone, just circling back to say a massive thanks — I followed the advice from earlier in this thread and changed that BIOS setting you pointed out, and my framedrops basically disappeared. Went from constant hitches during the most intense moments of matches to buttery smooth 144fps, no more stutter spikes. Turns out some power management thing was throttling my network stack and messing with the jitter buffer, so the dynamic delay smoothing was basically fighting a losing battle the whole time. Really appreciate all the help debugging this from root cause instead of just throwing bandwidth at it — you guys are legends. Marking this as solved!

"Flat frametimes > peak FPS"

[Jayden Collins]

Great topic to dig into. Historically, the evolution here really tracks the demands of the workload: uniform grids and grid hashes dominated early because they’re trivially O(1) to query and need zero rebuild time, which mattered when you were doing collision broadphases on static-ish geometry. But they collapse on sparse scenes—memory footprint explodes and you waste cycles on empty cells. That drove the shift toward k-d trees, which give you provably optimal splitting for ray traversal and nearest-neighbor queries

"Flat frametimes > peak FPS"

[Jayden Collins]

Here’s where most people get tripped up: Reflex and Anti-Lag 2 solve different problems, so misdiagnosing which one you need is the root cause of most “it didn’t work” reports. Reflex is a per-game, engine-integrated SDK that lets the driver synchronize the CPU-to-GPU queue—it actively reduces how many frames are in flight by having the CPU wait for the GPU’s current frame, which is why it shines in GPU-bound, low-FPS competitive titles (CS2, VALORANT, Apex). Anti-Lag 2 is a driver-level frame-timing controller that works globally across any DX11/DX12/Vulkan/D3D9 game by compressing the frame queue, but it can’t reduce in-flight frames the way Reflex does—it just schedules them tighter. The classic failure mode: you enable Anti-Lag 2 in a GPU-bound Reflex-supported game and see higher

"Flat frametimes > peak FPS *"

[Jayden Collins]

The sub-tick issue isn’t client tickrate itself, but Valve’s animation render interpolation. The bullet registers when clicked, but the visual kill feedback is delayed to the next rendered frame.

🎮 Battlestation & Rig: Ryzen 7 9800X3D | RX 7900 XTX Taichi | 32GB DDR5 6000 CL28 | Corsair 5000D | AOC AGON Pro AG276QZD 240Hz QHD OLED | Moza R9 V2 Direct Drive + Moza FSR Formula Wheel + CRP Load Cell Pedals | Audio-Technica ATH-R70x + Schiit Magni/Modi Stack

📍 Frankfurt (Germany)

"Smooth frame time pacing matters infinitely more than peak FPS."

[Author]

Posts