0
0

Hello there !

We are trying to use Fmod with a friend and we want to work on the same project with two differents computers. We are using Tortoise SVN to merge our sessions but it seems to be very complicated to resolve conflits…. So, here is my question : How can we work on a fmod project with two computers at the same time ? Is it possible to work on the same .fdp at the same time ?

Thanks for your answer and sorry for my poor English !!

Pierre-jean

  • You must to post comments
0
0

We keep the Master copy on our network and a local copy on each pc, then "check in" our local copy when done. Obviously the last one to save their copy to the network overwrites any changes done by other users. If you want to work on the same project/file location at the same time with live updates/merging changes I don’t think it’s possible.

  • You must to post comments
0
0

FMOD Designer has a merge project function which allows you to import data from another project. It will import anything from the second project that does not already exist in the first one. If the data does already exist it (according to the documentation) gives preference to the master project rather than the one being imported. This means that if you want to tweak an existing event and merge in the updated settings then the only way to do it is to first delete the event from the master project.

Merge used to be a bit flakey back around 4.24… we tried using it then and had some problems with corruption. Tried it again recently on 4.32 and it seems to be reliable now. Attempting to merge projects using standard diff/merge tools is pretty futile. To much can change to quickly so you may as well just make the changes again manually in designer – its faster and less likely to break the project.

The other way of making FMOD Designer accessible for multiple concurrent users is to divide your project into more than one .fdp; one for weapons, one for ambience etc. The FMOD API will be able to load them all up and use them just fine. You can use workspaces to manage multiple projects from one instance of Designer but you have to switch between them – you can’t see them all at once like you can with WWise.

Other downsides of working this way… makes it much harder to produce and small compact and memory efficient set of banks abd you can’t share assets between projects leading to duplication. On the upside, if you do it right you can cut down your metadata usage significantly by only initialising event data you need for specific scenarios.

The lack of proper multi user support is a big issue and caused us massive bottlenecks on previous titles. Hopefully the Firelight guys have this high on their list of things to address.

  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.