⚡ Live Stream

[Nolan Ward]

Great topic to break down. On the fundamental mechanics: Resizable BAR works by expanding the PCIe BAR0 memory-mapped region that the CPU can address into GPU VRAM. By default, the PCIe spec and legacy BIOS conventions cap that aperture at 256MB regardless of physical VRAM, so the driver has to constantly stage and stream geometry/textures through a limited window—adding copy overhead and cache-thrashing. When you enable ReBAR (BIOS ”

"Original Xbox & PlayStation 2 CRT gaming corner in the den."

[Nolan Ward]

The single biggest mistake I’ve seen teams make is treating replay systems as a serialization problem when they’re really a determinism problem first. If your frame simulation isn’t bit-for-bit reproducible across builds and hardware, no amount of clever compression will save you. The classic killer is floating-point non-determinism—same inputs, different results depending on CPU microarchitecture, SIMD vectorization, or compiler flags. My rule of thumb is to lock your build flags and disable auto-vectorization on hot paths, and for networking-heavy titles, either constrain all math to fixed-point or run a deterministic lockstep simulation where every tick is driven by validated inputs rather than serialized state. Capture inputs at the rawest layer (before any post-processing or input buffering smoothing), because once you serialize post-processed values you lose the ability to reconstruct the exact same causal chain.

For the actual serialization strategy, I’d push delta compression over full snapshots for anything beyond local demos. Snapshot everything and you’re dumping hundreds of megabytes per replay that nobody wants to store

"Original Xbox & PlayStation 2 CRT gaming corner in the den."

[Author]

Posts