We do a lot of sharing of projects between sound designers here. We frequently run into a bug where after a build, the events will play the wrong wav’s. It’s like the fev and the fsb indices are out of sync or something. Whenever we get this a clean, full rebuild always fixes the problem.
It appears that the repro is somthing like: designer A builds project X (including all or some of the fsbs). Then, designer B builds project X (including all or some of the fsbs). Later, designer A builds X again, but only selects a few banks from projectt X.
Has anyone else run into this? Is the fix for designers to always have all banks checked? Will FMOD Designer be smart about not rebuilding banks unnecessarily? We currently check in fdp, fev, and fsb files (not .seq or .cache files). Should we be checking in .seq files? Is there another fix/workaround?
- audiodev asked 9 years ago
Ahh, that’s a real bummer. It’s hard for our designers to keep track of which banks other people have changed, so your suggestion basically means that they’ll just rebuild all projects all the time (just to be safe), which is a big time sink, and it kind of negates all of the awesome caching work that you guys do.
We’re in the process of doing our offical audio builds on our build machine anyway, which will hopefully work around the problem. Still, it’s a shame that the projects aren’t more amenable to being shared between multiple developers.
I wonder if having some sort of client-local "last build settings" file would help this issue (similar to Visual Studio’s .suo file). Come to think of it, there’s a lot of data that’s stored in the project that really is user specific (like which platform you last had selected or what the open state of various folders is).
Please login first to submit.