On it 😎
It will extract the audio clips and save them separately, so they can be included in scenes and included in saved AudioMate configurations, though. Otherwise the whole bundle would become a dependency and had to be included when sharing a scene or config.
This update contains only bug fixes and optimizations.
Bug fixes:
Unload no longer throws "Collection was modified".
Destroy runs once per component.
Triggers no longer register a duplicate "value" param.
Triggers are created only when an action is added or restored.
Custom CollisionTrigger...
Is anyone having any specific wishes about which topic the next AudioMate Tutorial should cover?
Or should I just go into more detail, explain the options I haven't used in the first edition and show some more use cases for AudioMate?
Is anyone having any specific wishes about which topic the next AudioMate Tutorial should cover?
Or should I just go into more detail, explain the options I haven't used in the first edition and show some more use cases for AudioMate?
This usually would have been a pure bugfixing release. But since I already proceeded with the development of AudioMate in the meantime and didn't want to roll back much of the code, I decided to include a feature that was originally planned for the next bigger release.
It's called Collection...
I was not able to reproduce the error you're describing. I was loading the default scene, added 2 collections with clips, saved it and reloaded it. Works as expected.
Does the problem occur for you in the default scene if AudioMate is the only plugin?
If not, then its most probably some sort of...
A quick update: The hint texts seem to be cut off in the latest version. Will be fixed asap - just in case someone came here because the hints do not make any sense to them ;)