For the past months I’ve been doing all perforce operations for my FMOD project directly within the P4 client. Since I’m solo sound designer on the project, that isn’t much of a problem.
To future-proof my workflow I played around with the FMOD perforce integration.
However, the integration runs so slow, it’s absolutely unusable. As soon as I select Perforce in the preferences dialogue, even closing the preferences window takes more than a minute.
Any source control operation is also painfully slow.
I was using the ‘perforce’ not the ‘perforce (legacy)’ option.
My system is Win 11 (latest updates), I’m running on a Ryzen 7 8700F / 64 GB RAM / NVIDIA GeForce RTX 4060. All network running through ethernet cable (no wifi).
Is there anything I can do to speed up the integration?
Can you send a screenshot of your working source control settings for the Perforce integration type (i.e. not the Legacy one)?
Also, can you send us a snippet of the FMOD Studio logs from when you’re trying to connect please? Logs are at %HOMEPATH%\AppData\Local\FMOD Studio\Logs.
Hi Andrew, sure thing! Here are the working settings for the normal P4 integration.
On clicking the user or Client Workspace dropdown, it identifies all possible options straight away.
I didn’t find any logs in the path you specified (there’s no Local subfolder in AppData in my profile, just LocalLow and Roaming). I did a search for Logs including hidden files and didn’t find anything FMOD related…
I checked the console, but even when I hit Save Project (which initiates a source control operation, P4 is shown as online in the bottom bar), nothing appears and I get the dreaded slow progress bar..
I’m also keen to get some info on your Perforce server, most importantly the server version. Can you fire up the P4V app and go to the Help menu and hit “System Info” and then copy as much info as you’re allowed to and send it to us please? Feel free to email us directly at support@fmod.com if you don’t want to share this info publicly.
That’s good news. What did you do to make it connect?
As for the client version issue, that may indeed be a problem with 2.02.xx. Can you do a quick test for me and download FMOD Studio 2.03.10 and try to connect to your perforce server please? Does it work?
It must have been something with the fingerprint I passed to p4 trust. I did it again and it worked.
I quickly opened a copy of my project with 2.03 and it seems that configuring P4 is much more responsive.
I’ve been wanting to upgrade to 2.03 for some time now, and I used this argument to convince our devs to put the Unity integration update on their timeline - it should happen next week.
As soon as I’m running 2.03 I’ll do a proper test and let you know!
