0
0

I get a consistent crash inside the FMOD runtime using 4.0.4, 4.0.10, and 4.0.11. The test case involves two event files (FEV). Both event files load successfully. Events out of the first FEV file play successfully. On either the first loadEventData or first PlayEvent of something out in the second FEV, we get the following crash.

001B:00AC7371, FMOD::EventGroupI::getNumEvents()+19185 byte(s)

Searching through the forums, I noticed some messages about crashes with getNumGroups. As a result, I removed all of the unused groups in either of the projects, and the crash appears to be fixed.

Both FEV files contain the same heirarchy. For example:
Master
— SFX
—— Foley
—— WPN
——— M4

One FEV files contains events inside M4 and the other contains events inside Foley. We use an template project as a starting point that has the heirarchy already, but no events. It appears this causes FMOD to crash when loading multiple FEV. Changing the FEVs to contain only the heirarchy necessary for there events, fixed the issue.

Best Regards,
Michael Marks.

p.s. The address in the crash line is from FMOD 4.0.4 runtime

  • You must to post comments
0
0

Thanks Michael, I’ll check it out and see what we can do for a fix.

  • You must to post comments
0
0

I’ve got a similar crash in an fdp I’m working on. One of the events using engine designer worked fine for a while and then at one point I pressed play and it crashed. I reopened it, tried it with different drivers and it still crashed. I created and played another event within the same fdp and the new one worked fine but when using my original event and pressing play it crashes every time. Please advise. Thanks!

  • You must to post comments
0
0

Adam, I’d love see that .fdp with the failing event. If you could email it to me that’d be great.

Cheers,

  • You must to post comments
0
0

Adam, thanks for the .fdp, I’ve fixed the problem for our next release.

Cheers,

  • You must to post comments
0
0

Michael, the issue you raised at the top of this thread has been resolved for our next release. Sorry for the delay.

Cheers,

  • You must to post comments
Showing 5 results
Your Answer

Please first to submit.