⚡ Live Stream

[James Harris]

Great topic. The key thing people undersell when comparing Wwise and FMOD is how the real-time thread behaves differently under load, not just the feature set. Wwise’s mixer is more aggressively parallelized—it spreads work across multiple DSP mixer threads and lets you configure the thread priorities and count per platform in the console, which matters a ton when you’re pushing 500+ simultaneous voices on a competitive title where you can’t afford a dropout mid-round. FMOD, on the other hand, keeps its overhead lower out of the box with a more linear FMOD_DSP chain model, and its System::update() is genuinely lightweight. My experience is that FMOD wins on raw CPU efficiency for smaller teams, while Wwise gives you finer-grained control over the DSP signal path and per-voice modulation, but that control comes at the cost of more authoring overhead and a heavier runtime footprint.

On the concurrency side, both engines demand that your audio thread be high-priority with zero blocking calls and no heap allocation—use their pre-allocated memory pools (`FMOD_MEMORY

"i5-13600K | RTX 4070 Super | 32GB B-Die 3800 CL14 tight timings"

[James Harris]

Good topic, and since we’re talking hyper velocity here, the core problem everyone underestimates is that discrete detection is fundamentally a sampling problem. In DCD you’re only checking overlap at frame boundaries, so once an object’s sub-frame displacement exceeds the thickness of the collision mesh it’s traveling toward, it simply vanishes through it—classic tunneling. The math behind it is brutal: for a projectile moving at, say, 2000 m/s you’re talking sub-millimeter penetration on a 1mm wall within a single 16ms frame. CCD fixes this by sweeping the shape through time

"i5-13600K | RTX 4070 Super | 32GB B-Die 3800 CL14 tight timings"

[Author]

Posts