On a project previously using Unity 2023.x and FMOD 2.0.2, having updated to Unity 6 and FMOD 2.0.3 is causing a few issues.
Most events play as expected, however, there are a few odd error messages in the Unity console and events that pass on parameters fail to play whatsoever. Here is an example of Play mode output after launching into the game, followed by two events that pass on 4 parameters to play footsteps as the player is walking:
Events are played through scripting by calling RuntimeManager.CreateInstance with an EventReference and released manually when needed - that said, after troubleshooting this for a while I’m starting to think that the issue is on a broader level (also reinforced by those top messages in the log).
I’m running both Unity and FMOD Studio on Fedora Linux 43, though I also have build support for Windows/Mono added to my Unity installation. I have tried to manually remove my FMOD plugin folder entirely, restart Unity, and then re-install the FMOD integration from scratch, but this does not appear to make a difference.
Would be happy to provide any more information! It might be that this is a Linux-specific issue, so I should also add that the Unity editor is running as a flatpak, and using PulseAudio. Hopefully this can be reproducible somehow!