Transceiver Effect working in Unity Editor but not build

Unity
1

Hello! I’m using a transceiver effect to play 2 different layers of a track in different locations. I have the main event set up with 3 tracks (one playing at all times) and I have a pre-fader transceiver set up on 2 of the tracks on channel 0 and 1 which get received by 2 “child” events that are set in their own emitters at the desired locations. Works great in editor but I get no sound from the “child” events. Made a dev build and there are no errors directly pertaining to the issue in the log.

Using Unity 2022.3.43f1, FMOD Studio 2.02.21, FMOD for Unity 2.02.21. Any help appreciated!

2

Hi,

What version of FMOD are you using?

Would it be possible get record a profiler session (FMOD Studio - Profiling) while connected via Live Update (FMOD Studio - Editing During Live Update.

What we will be looking for if the child events are behaving as expected, e.g. playing and producing audio. I have a hunch that they may be stopped by the Stop Outside of Max Distance (Unity Integration - Settings - Stop Events Outside Max Distance) behavior if they are spatialzied.

Would it be possible to set the following FMOD Integration settings:

LoggingLevelLog
LoggingLevelLog263×223 8.46 KB

and share the full player logs:
image
image465×314 8.64 KB

Thanks

3

Sorry for the late reply on this! As stated, we’re using Using Unity 2022.3.43f1, FMOD Studio 2.02.21, FMOD for Unity 2.02.21. Attached is a profiler session and the player log. I entered the affected area at 50 seconds. Stop Events Outside Max Distance is NOT enabled.

Profiler Session: F_ClairaudioProfiler.fspackage - Google Drive

Player Log: Player.log - Google Drive

1 Like
4

Thank you for sharing the information, and sorry for the late response.

Unfortunately, with the info provided, I have been unable to reproduce the issue on my end using a similar setup.

Would it be possible to upload your project (or a stripped down version that still demonstrates the issue) to your FMOD user profile, so I can take a closer look at what might be going wrong?

Additionally, could you please try using Studio::EventDescription::loadSampleData to see if preloading the events resolve the issue?