0
0

We seem to get a lot of errors when building projects, whos events have the same GUID’s. This has never been an issue before (and I don’t even know why they have the same GUID’s).

Are they used internally in FMOD, or is it something we should fix? If it’s not an issue, could we have an option in fmod designer CL, to skip this error.

Thanks

  • You must to post comments
0
0

Apologies, the GUID conflict error was supposed to be downgraded to a warning before Designer 4.23.00 was released. This is fixed in Designer 4.23.01, which is out now.

This message is only relevant if you want to use EventSystem::getEventByGUID. If you don’t want to use that, pass FMOD_EVENT_INIT_NO_GUIDTABLE to EventSystem::init so you don’t get FMOD_ERR_EVENT_GUIDCONFLICT when loading your FEVs.

By the way, your events most likely have the same GUIDs because you’re using templates – there was a bug (now fixed) where the "Apply Templates" command would overwrite template users’ GUIDs with the template’s GUID. You can use the "Regenerate GUIDs" command (right-click in the event hierarchy with events selected) to resolve GUID conflicts.

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.