Whenever I save my FMOD project, it hangs on “checking for invalid files” for a very long time before the rest of the saving process finishes rather quickly. I feel like it takes 30 seconds to a full minute every time I save. In combination with a well practiced habit for hitting ctrl+C after most things I do, this becomes a pretty significant workflow slow down.
Is this normal or expected? I am using FMOD with Unity and Perforce. I’ve noticed that Perforce makes a few operations in Unity drag on for a very long time as well.
And if this is Perforce related, is it safe to disconnect from Perforce while doing some amount of work, or even just while doing iterations that involves saving often, and reconnect to sync everything afterwards?
In Unity I sometimes work offline and then use “reconcile offline work” to sync back up when I’m doing lots of things that make Perforce spin its wheels every time. Is that a reliable workflow within FMOD? I know stuff like that can sometimes confuse Perforce and cause some issues that are pretty time consuming to fix. In Unity this is most commonly an issue when moving or renaming assets. Is working offline temporarily a bad idea?
This doesn’t sound normal to me. Could you please let us know which version of FMOD Studio you are using?
If you disconnect the project from source control, do you still run into the same long wait times when saving or performing other actions?
It is possible to work temporarily while disconnected. Once reconnected, you can use File > Source Control > Identify Local Changes… to compare the local project files against the files in Perforce and add any offline changes to a changelist.
Yes, FMOD Studio provides a workflow for this. You can find more information in our documentation here: Working Offline
Not necessarily, particularly for short periods of isolated work. However, I would be more cautious if multiple people are actively modifying the same project content, as working offline does not prevent conflicting changes.
This doesn’t sound normal to me. Could you please let us know which version of FMOD Studio you are using?
We were using 2.03.09 and have recently updated to 2.03.14. The behavior is the same.
If you disconnect the project from source control, do you still run into the same long wait times when saving or performing other actions?
The problem with this test is that doesn’t always do it even as it is now; it’s more of a most of the time thing rather than every time. Like if I have just saved and I make only one new change, it usually saves in a normal amount of time (but I think also sometimes doesn’t).
However, I would be more cautious if multiple people are actively modifying the same project content, as working offline does not prevent conflicting changes.
Maybe I’ll disconnect for a while and see how often I see it, but this is a great point that I’m glad you reminded me of. We do have multiple people using the same FMOD Studio project now, so that could be somewhat risky.
Yes, FMOD Studio provides a workflow for this. You can find more information in our documentation here: Working Offline
Awesome. I will read up on that and try to figure out the safest way to further diagnose this. I’m thinking either over a weekend or with a new separate “disposable” Perforce workspace.
I’ll report back once I have a chance to take a closer look. I really appreciate the help. Thank you.