SVN not connecting in FMOD Studio 2.00.03

Heylo FMOD Forums -

We just upgraded our Unity project from FMOD version 1.XXXX to 2.XXXX and also updated FMOD Studio to 2.00.03. With the upgrade to FMOD Studio to 2.00.03, we are now seeing SVN issues when attempting to connect within FMOD Studio. All SVN settings, project info, etc are properly input but FMOD Studio is continually considered offline. How do we go about resolving the offline issue?

Any information or direction would be appreciated.

Our SVN integration appears to be working correctly when we test it here, so there must be some difference in configuration between our test machines and the machines you’re running it on. Are you sure all the SVN settings are configured correctly? Do any of the machines you’re using feature a firewall or other piece of software that might be blocking FMOD or SVN from accessing the network?

Yup - all SVN settings are configured correctly. In FMOD Studio 1.XXXXX SVN worked and connected properly. But since the update to 2.XXXX, FMOD Studio has issues connecting to SVN. No Firewall or blocking software and running OSX. All SVN clients are connecting properly too.

The only special thing setup on SVN is “access” of the repo being checked against a security group membership in active directory (prompt for password when accessing repo path).

If those credentials are cached then authentication should be all set for that group.

We are getting an error when attempting to save as well:
"The project’s path “#PROJECTPATH”, could not be mapped to any location in the depot/repository.

Again, this is only an issue with 2.XXXX. 1.XXXX works fine.

That error message should normally only appear if the connection settings for the project aren’t correct. However, as you’ve said your connection settings are correct, I’m not sure why it’s appearing for you.

Are you able to send us the log file for an FMOD Studio session in which the connection error occurs? It may reveal information that would help us diagnose the issue. You can find the log files in the “Library/Application Support/FMOD Studio/Logs” subdirectory of your MacOS user folder. (You may need to unhide the “Library” folder.)

Where would you like this log sent? The log contains a lot of personal information - including svn passwords, logins, etc… (this personal information should be *'d out of logs to avoid credential leaks, etc).

[Scripting]runSVN: error running command: --non-interactive --username #USERNAME# --password #PASSWORD# unlock #PROJECTPATH# /Audio.fspro

[Scripting]runSVN: svn: E195013: ‘#PROJECTPATH# /Audio.fspro’ is not locked in this working copy

The easiest way to send us your logs is to select “Help > Contact…” This will pop up a dialog; if you put a link to this forum thread in that dialog and click “send,” our triage team will know that it’s connected to this.

Email sent.

We have received your e-mail, but the log was not attached. To attach your recent log files to an e-mail sent through the “contact” dialog, make sure the “Attach application log” checkbox is checked before clicking “Send.”

Could you please try running these two commands in Terminal, and tell us what the output of each of them is? (You’ll have to substitute in your own username, password, and project path and filename.)

svn --non-interactive --username USERNAME --password PASSWORD info "/Users/USERNAME/Desktop/Projects/PROJECTNAME_FMOD/PROJECTNAMEAudio/PROJECTNAMEAudio.fspro"

svn --non-interactive --username USERNAME --password PASSWORD status "/Users/USERNAME/Desktop/Projects/PROJECTNAME_FMOD/PROJECTNAMEAudio/PROJECTNAMEAudio.fspro"

Path: Desktop/Projects/PROJECTNAME/FMOD/FeralAudiPROJECTNAMEalAudio.fspro
Name: PROJECTNAMEAudio.fspro
Working Copy Root Path: /Users/USERNAME/Desktop/Projects/PROJECTNAME_Mac
Relative URL: ^/Project_Main/FMOD/PROJECTNAMEAudio/PROJECTNAMEAudio.fspro
Repository Root: https://USERNAME@REPOURL/svn/PROJECTNAME
Repository UUID: f8cd5034-e6b2-48b7-acef-232aa520313b
Revision: 11400
Node Kind: file
Schedule: normal
Last Changed Rev: 2231
Last Changed Date: 2018-10-30 11:24:39 -0600 (Tue, 30 Oct 2018)
Text Last Updated: 2019-04-10 09:28:51 -0600 (Wed, 10 Apr 2019)
Checksum: 1759935512f38860b6921ddd982e3479d5a29f82

Nothing was returned for the status output.

Hmm, there’s nothing in there that’s obviously problematic…

Does your user name or project name contain any non-ASCII characters? If so, those might be the cause of the problem.

Can you double-check that the paths on disk match the casing of those given in the info output?

Nope. All ASCII characters for the project name and the project matches the output.

From what you’ve said, the SVN integration should be working. Unfortunately, we have still not been able to reproduce the issue here. As a result, we are unable to identify its cause or solution.

There must be some detail of your setup that differs from our test environments; if you can think of anything that might be relevant, please let us know.

Still an ongoing battle. Everything worked great in FMOD Studio 1.0. FMOD Studio 2.0+ and SVN no longer works within FMOD Studio. Is there a list of changes to look at that are SVN related to see if we can catch anything that may be the issue?

Recent svn error logs from FMOD Studio:

  • 13:40:20 [Scripting]runSVN: error running command: --non-interactive --username #USERNAME --password #PASSWORD unlock /Users/#USERNAME/Desktop/Projects/#PROJECTNAME_FMOD/#PROJECTNAME/#PROJECTNAME.fspro
  • 13:40:20 [Scripting]runSVN: svn: E195013: ‘/Users/#USERNAME/Desktop/Projects/#PROJECTNAME_FMOD/#PROJECTNAME/#PROJECTNAME.fspro’ is not locked in this working copy

Our detailed revision history lists every significant change and new feature added to FMOD Studio since its initial public release.

The “not locked in this working copy” error is benign, and so is probably not related to the issues you’re having using the SVN integration.

Found somewhat of the issue…

If you have the FMOD Studio project in SVN and update SVN to get the FMOD project (outside of FMOD Studio - in SVN only), you won’t be able to access SVN within FMOD Studio as it gives the error “The project’s path “#PROJECTPATH”, could not be mapped to any location in the depot/repository.”

If you access FMOD Studio in SVN fresh by using FMOD Studio toolbar: File/SourceControl/Browse for Project - it allows connection to SVN after the project is downloaded and mostly works. However… following multiple commits, updates, etc from multiple people - eventually lock issues, out of date banks, and other issues ensue.

Per FMOD Studio/Unity setup documentation, we should be able to access the project by downloading it from SVN (outside of FMOD) but this is not the case for FMOD Studio 2.0+. This was possible in 1.0+.

Another issue to mention - the documentation for implementation to Unity contradicts itself with requiring or not requiring the full development team access to the FMOD Project. Atop the documentation, it is not required. When reading further into the documentation it is mentioned that it is required for the full team to have access to the project. Possible to get some clarification on this?


When you get the FMOD Studio project outside of FMOD Studio using your SVN client, does it update the .cache, .user, and .unsaved subfolders? As described in the Troubleshooting section of the FMOD Studio User Manual, these files are user-specific, and so should not be included in source control; updating them from source control may be overwriting your local user source control settings, potentially explaining the issues you have been experiencing.

On that note, when you load your FMOD Studio project in FMOD Studio, do you select “File > Source Control > Browse for Project…” or “File > Open…”? I ask because the former is for creating a local copy of a project that you do not yet have a local copy of, while the latter is for loading an existing local copy of a project. Using the former in place of the latter when you already have a local copy of a project can cause source control problems in some situations.

On the topic of which members of your team require access to the FMOD Studio project:

  • Any member of your team who needs to be able to edit or view your game’s FMOD Studio project, perhaps so that they can create or edit events or profile your game’s audio performace, needs access to your FMOD Studio project.
  • Any member of your team that needs to be able to hear audio in your game, for any purpose, needs access to your FMOD Studio project’s built banks.

The .cache, .user.and .unsaved do get created. They are not under version control.

When getting FMOD Studio project outside of FMOD Studio using SVN (issues per above thread):
We update SVN. After updating, we use File > Open. However - SVN does not connect within FMOD Studio when downloading the project from SVN (credentials, etc are correct).

When getting FMOD Studio Project inside of FMOD Studio:
We first use File > Source Controls > Browse for Project. When the project is found and after it has been successfully downloaded, we use File > Open. This allows SVN to connect within FMOD Studio (progress!). However - after multiple people have committed, updated, etc - eventually we see locking issues, out of date banks, and other issues.

Thank you for the clarifications.

We have not yet been able to reproduce these issues with out internal tests, but we’ll keep investigating.

1 Like