# Fmod\_playback\_bus.cpp - assert 'level \>= 0.0f' failed

**URL:** <https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513>\
**Category:** Unity\
**Created:** [March 2, 2020, 8:20pm UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513 "2020-03-02T20:20:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![indygames](https://avatars.discourse-cdn.com/v4/letter/i/f17d59/32.png) [@indygames](https://qa.fmod.com/u/indygames)\
**Post date:** [March 2, 2020, 8:20pm UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/1 "2020-03-02T20:20:21Z")

</div>

We just upgraded to the latest FMOD on unity 2019.2.21 (also tried on 2019.3.3) and are now getting an assert that says:

"[FMOD] c:\jk\workspace\Build\_\_2.0\_\_UnityLibs\_Win\studio\_api\src\fmod\_playback\_bus.cpp (45) - assert : assertion: ‘level \>= 0.0f’ failed.

Ive tried this on multiple computers, both desktop and laptop, and multiple versions of unity (2019.2.21 and 2019.3.3) and it will always fail after a play or two. Yes, for some reason, the first time or two you run the game it will work and then fail continuously. After that, you have to reboot in order for it to (maybe) play. It sometimes fails first time.

That assert is a DEBUG\_CALLBACK from a dll so there is no call stack, making it so I cant see who is making the offending call.

Any help would be much appreciated. We are totally blocked on this and under the gun. Thanks in advance!

---

<div class="post-metadata">

**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:** [March 5, 2020, 4:28am UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/2 "2020-03-05T04:28:48Z")

</div>

Are you able to set the `Logging Level`, in the FMOD Unity settings, to “Log” and run it until you get the error. Then send us the console log file, hopefully that will contain more useful information. You can upload it to the website if you prefer: [https://fmod.com/profile#uploads](https://fmod.com/profile#uploads).

---

<div class="post-metadata">

**Author:** ![PabloWunderlich](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@PabloWunderlich](https://qa.fmod.com/u/PabloWunderlich)\
**Post date:** [December 29, 2023, 3:43am UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/3 "2023-12-29T03:43:58Z")

</div>

I’m having the same issue. I have uploaded my log to the link provided. I’m unsure how to solve it.

[AssertAssertion Error.txt](https://qa.fmod.com/uploads/short-url/lb7rNtfZTooAKDe0AzAXHhXDGtq.txt) (971.1 KB)

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [January 8, 2024, 3:41am UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/4 "2024-01-08T03:41:23Z")

</div>

Hi,

What version of the FMOD integration and Unity are you using?

Is it happening in the same circumstances? Playing the editor once without issue and then running into the error?

---

<div class="post-metadata">

**Author:** ![PabloWunderlich](https://avatars.discourse-cdn.com/v4/letter/p/d2c977/32.png) [@PabloWunderlich](https://qa.fmod.com/u/PabloWunderlich)\
**Post date:** [January 8, 2024, 4:06am UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/5 "2024-01-08T04:06:14Z")

</div>

I was able to fix the issue. I was calling the event in update and it was overloading FMOD. All good now!

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [January 8, 2024, 4:07am UTC](https://qa.fmod.com/t/fmod-playback-bus-cpp-assert-level-0-0f-failed/15513/6 "2024-01-08T04:07:24Z")

</div>

Hi,

Thank you for sharing the solution.
