# Best way to make smooth sounding automatic fire bullet flybys

**URL:** <https://qa.fmod.com/t/best-way-to-make-smooth-sounding-automatic-fire-bullet-flybys/24620>\
**Category:** Unity\
**Created:** [November 19, 2026, 5:01am UTC](https://qa.fmod.com/t/best-way-to-make-smooth-sounding-automatic-fire-bullet-flybys/24620 "2026-11-19T05:01:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kalman](https://avatars.discourse-cdn.com/v4/letter/k/59ef9b/32.png) [@kalman](https://qa.fmod.com/u/kalman)\
**Post date:** [November 19, 2026, 5:01am UTC](https://qa.fmod.com/t/best-way-to-make-smooth-sounding-automatic-fire-bullet-flybys/24620/1 "2026-11-19T05:01:27Z")

</div>

Making smooth sounding automatic bullet flybys is a different challenge from smooth sounding automatic fire reports. Automatic fire is generally at exactly the same RPM, say for a 600 RPM weapon you’d want the report audio to trigger precisely every 100ms. There are a few ways to do this. Not my question though.

The challenge with flybys is that they’re not exactly every 100ms since bullets do not flyby at the exactly precise moment each time. Many games (including ours) have an aiming drift as you fire automatic weapons. It’ll be like… 99ms, 101ms, 97ms since the trajectory is slightly different.

Apart from the actual calculation of when/where the flyby should play (I got that sorted) there are 2 other challenges:

1. make it frame rate agnostic smooth. You can instinctively feel the frame rate jitter with a slower frame rate (\< 30FPS) if you’re just triggering on Update, and it sounds awkward. I.e. you cannot trigger in 99ms, 101ms because your frame rate is not 2ms.
2. make it not flood the voice and/or instance count.

Solving (2) is more important and there is of course the instance limit/stealing in the FMOD event. I’ve actually written my own for various reasons but it’s the same kind of thing. But many solutions for (1) are impossible with instance limiting.

For example:

- one idea I had was to just start the flyby at the projected correct position but in a paused state, then use the DSP delay stuff with the event’s ChannelGroup to trigger at the precise time. This works well timing wise, but the problem is that future flybys will cancel scheduled flybys before they play.
- a more complicated version of this is to try and do this scheduling thing as late as possible, like aim for a couple of frames before, but I can only grab the ChannelGroup once the event has been created and by this time it might be too late to delay it. From what I can tell it helps a little bit, could be a placebo though.
- another idea I had, but have not tried, is to have a pool of persistent flyby events. Let’s say 3. Ditch instance limiting and instead do setTimelinePosition/setDelay/setPosition/setDSPDelay to reset/delay/position/trigger the flybys. This would solve the problem of not having a ChannelGroup. It’s more complicated to write the code though so I haven’t tried it.

right now I’ve given up on solving (1) and hope that player frame rates are high enough to not sound too weird, or if it is low then they might not care. but I’d like to solve it for real.

we are using FMOD 2.03 currently.

also: bullets are physically simulated and they have visual tracers, so I can’t introduce a delay buffer sort of thing.
