# Stop Events Outside Max Distance Bug **URL:** \ **Category:** Unity\ **Created:** [July 21, 2025, 1:19pm UTC](https://qa.fmod.com/t/stop-events-outside-max-distance-bug/23182 "2025-07-21T13:19:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Katharina\_zaum](https://avatars.discourse-cdn.com/v4/letter/k/ba8739/32.png) [@Katharina\_zaum](https://qa.fmod.com/u/Katharina_zaum)\ **Post date:** [July 21, 2025, 1:19pm UTC](https://qa.fmod.com/t/stop-events-outside-max-distance-bug/23182/1 "2025-07-21T13:19:07Z")
Hello, I wanted to try the Stop Events Outside Max Distance feature and got a bug when hitting play in Unity the **second** time. The first time after opening Unity everything works great, but after stopping and starting play mode, this error is spamming. It is happening in every scene. After closing and opening Unity again, play mode works fine again once, next time, I get the error again. We’re using Fmod 2.03.07, recently updated from 2.02. and Unity 2022.3.62f1 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/7/7842338fa336a410d271fb4d37f391f1376d1a1c.png) We have investigated a little bit and it seems like there is a bug in the Fmod plugin where `OnApplicationQuit` is called and events are not disposed. We added a workaround by commenting out `isQuitting` true on StudioEventEmitter (line 151), but it would be great if there was an official fix for this, so we don’t run into issues when updating fmod again. ---
**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\ **Post date:** [July 31, 2025, 6:01am UTC](https://qa.fmod.com/t/stop-events-outside-max-distance-bug/23182/2 "2025-07-31T06:01:10Z")
Apologies for the delay. Thanks very much for the information, I have been able to repro this and have made a task to investigate it further.