I want to split the project. Are there any side issues?

Hello.
I want to separate the game sound and voice project.


When the project is separated, I want to make sure that the routing is compatible without any issues.
If there is a recommended way to split a project into multiple projects, please let me know.

Thank you.

Why do you want to do this?

I ask because in many circumstances, splitting a project provides few or no benefits: Our source control integrations already support multiple users collaborating on the same project, and FMOD Studio’s dynamic loading system means that FMOD Studio is capable of handling large project sizes.

There are a small number of situations in which you might want to split an FMOD Studio project - but each of them imposes different requirements on how the split be performed: The method of splitting the project appropriate for supporting DLC and UGC is different to what you might use if you want to release some of your project’s content for educational purposes while keeping other parts private, for example, and different again to the method you’d want to use if you intend to make multiple different games using the original game’s project as a template.

I’m contacting you because there’s an issue where project settings roll back when some workers are working.
So, I wanted to separate the projects.

That’s very strange - our source control integrations are designed to prevent that.

In any case, FMOD Studio projects are not designed to be split for this purpose. It will likely be easier to determine why your workers’ project settings are being overwritten and fix that issue than it would be to split the project and deal with the inconveniences that would result.

Could you please describe in detail what project settings are being overwritten, and the workflow that leads to it occurring?