Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support sample data loading #20

Open
GitGhillie opened this issue Sep 17, 2023 · 2 comments
Open

Support sample data loading #20

GitGhillie opened this issue Sep 17, 2023 · 2 comments
Labels

Comments

@GitGhillie
Copy link
Collaborator

See https://www.fmod.com/docs/2.00/api/studio-guide.html#sample-data-loading

Currently we load samples when we call Studio::EventDescription::createInstance, but we probably want to support loading all of the sounds for one level for example.

@Salzian
Copy link
Owner

Salzian commented Aug 30, 2024

I'm trying to undestand how you would like to accomplish that.

If you spawn all sound related entites on level load, you will have that behaviour. If you want to load all required sounds of a level on level load but not want to spawn all sound entities on level load... How should the library know what to load?

@GitGhillie
Copy link
Collaborator Author

I think in any case it should stay up to the user to determine when and what to load/unload.

One thing we can do to make things easier for the user is to provide a Bank component and have bevy_fmod call the FMOD bank load/unload functions automatically when the entity/component is added or destroyed.

Alternatively we can also make sure all the functions mentioned in https://www.fmod.com/docs/2.00/api/studio-guide.html#sample-data-loading are exposed and usable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants