[FMOD] transform : assertion: 'previousPoint != NULL' failed on macOS (Unity + FMOD 2.03.07)

Unity
1

Hello,

After upgrading our project from FMOD 2.02.22 to FMOD 2.03.07 we started seeing a recurring error on macOS builds (it never occurs on Windows):

[FMOD] transform : assertion: 'previousPoint != NULL' failed
UnityEngine.Debug:LogError (object)
FMODUnity.RuntimeUtils:DebugLogError (string) (at Assets/Plugins/FMOD/src/RuntimeUtils.cs:594)
FMODUnity.RuntimeManager:DEBUG_CALLBACK (FMOD.DEBUG_FLAGS,intptr,int,intptr,intptr) (at Assets/Plugins/FMOD/src/RuntimeManager.cs:104)

Some details:

  • Unity version: 2022.3.44f1

  • Target platforms: iOS + Android (but issue reproduces on macOS Editor/Build only).

  • We tested with a clean project: removing all effects/sounds and leaving only a blank master bus makes the error disappear. Adding events back sometimes triggers the assertion.

  • The error often appears in batches (hundreds of lines) immediately after starting an event.

  • We also see related warnings like events waiting for sample data (EventInstance::updateForStart waited XXX ms).

Questions:

  1. What does this specific assertion (previousPoint != NULL) mean inside FMOD?

  2. Is it related to migrated curves/automation (e.g. distance attenuation, automation points not starting at 0)?

  3. Why does it reproduce only on macOS and not Windows?

  4. Are there recommended steps to debug which event/parameter curve is causing the assertion?

We already tried:

  • Rebuilding all banks.

  • Removing/adding events one by one.

  • Checking automation curves for duplicated or missing first point.

Any advice or confirmation if this is a known regression in 2.03.x would be really helpful.

Thanks!

1 Like
2

Hi,

Thanks for the information.

It maybe linked to a race condition with regarding snapshots.

For question 2 - 4 I don’t have answers at this point, hopefully we will resolve them with some more investigation.

Would it be possible to uploads the built banks to your profile so I can test them on my side?

Thank you for bringing this to our attention.

3

Done it

1 Like
4

Thanks you for the banks.

I have been able to reproduce the issue.

This assert is warning of a thread issue. Nothing wrong that you have done something that we will fix.

I have passed on the issue to our development team to investigate further. I do not have a workaround at the moment.

Thank you for bringing this to our attention.

5

Hello, are there any updates?

6

This has been fixed for our next release (2.03.11) which should be out in a couple of weeks.

7

Great news, thank you!