We ran into a problem when a sound definition in one soundbank had the same name as a sound definition in another bank. An event designed to use a sound definition from a specific sound bank was at runtime erroneously using the definition with the same name from the other bank. Since events know which bank they need, isn’t this enough for the event system to find the correct definitions? Or do all definitions need to be named uniquely? Perhaps this is a bug?
This same question applies to all elements of the event system: Projects, Groups, Events, Categories, SoundBanks, SoundDefinitions, WAVs, etc. Since Events have a namespace built from the project and group hierarchy, specific events can be disambiguated from other like-named events. But do all elements follow this philosophy? What can’t be named the same?
- DLawson asked 10 years ago
- You must login to post comments