I suspect that your event handle is getting stolen.
There will only be a number of valid instances of a given event equal to the ‘Max Playbacks’ property for that event set in FMOD Designer. The purpose of this feature is to give you control over maximum number of active instances of each event to control memory and CPU usage.
The other property related to this is ‘Max Playback Behaviour’. Let ‘n’ be the max playbacks value, ‘Max playbacks behaviour’ determines what happens when you call getEvent the (n+1)th time.
The possible behaviours are:
*Steal Oldest (default)
*Just Fail If Quietest
I suspect what is happening is you’re calling getEvent, then which is causing the new event to steal the oldest, which is causing you to get the FMOD_ERR_INVALIDHANDLE error on the old event.
Hope this helps,
- Guest answered 9 years ago
Please login first to submit.