I’ve encountered a very strange bug: I have one big timeline event for dynamic level music in my game. One event per level, and we transition to different parts of that timeline as you progress through the level.
Twice, we have now noticed that transitioning to a marker causes the clip at that marker to not play the first time it is transitioned to. Once the end of the loop region is reached and it comes back around, the audio in question then plays properly.
We were only able to fix it by deleting clips and re-adding them. We have encountered this problem twice now since we upgraded to FMOD 2.03 and I was starting to suspect that this problem was introduced in 2.03 so just now I replaced all of the occurrences of serializationModel=“Studio.02.03.00” with serializationModel=“Studio.02.02.00”in our project files and opened the project in FMOD Studio 2.02.
Lo and behold, the exact same project files no longer produce the problem I described. I then discarded my changes in the in the project files, and opened them in FMOD Studio 2.03 again, and the problem came back.
So this is definitely a bug introduced in FMOD Studio 2.03
We will downgrade for now. In the mean time, could you let us know what you need from us to be able to understand/reproduce/fix the problem?
I can think of a couple of possible causes for the behavior you describe.
There is a known bug introduced in FMOD Studio version 2.03.09 that results in instruments not playing when they are triggered exactly at the destination of a transition timeline, provided that transition timeline has no destination region. Does the event make use of a transition timeline when you transition to a new music section, but not at the end of a loop region? If so, there’s no need to give us more information; we’ve already created a fix for the bug and included it in FMOD Studio version 2.03.13, which we’ll release soon. You should be able to test this by seeing whether this issue can be reproduced in FMOD Studio version 2.03.08 or earlier, which should not exhibit it.
On the other hand, if the behavior you’re experiencing doesn’t require the existence of transition timelines, then it is likely a previously-undiscovered issue. If that’s the case, please upload a project containing an event that exhibits the issue, so that we can investigate its exact cause and reproduction conditions. Given that it only occurs the first time an asset plays and is affecting music assets, it may be caused by the asset’s sampledata not having loaded or buffered at the time it’s supposed to start playing - but without knowing more about how the event is structured, I can’t say for sure; we’ll need to examine a project that exhibits the issue to learn more.
The problem area in question uses a Transition Timeline
The problem area uses a Destination Marker, not a Destination Region
The instrument starts exactly at the Destination Marker
So from the sound of it, this is exactly the use case you describe. As mentioned in my original post, the earlier version of FMOD that I tried does not exhibit this problem (version 2.02.12) so it sounds like it is the bug you think it is.
Then we will stick with this FMOD version for now, and once the new version with the fix is out, we can upgrade again.
