# FMODStudioSettings.asset sourceProjectPath setting saved per machine **URL:** \ **Category:** Unity\ **Created:** [June 17, 2019, 4:30am UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775 "2019-06-17T04:30:31Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![buzzrick](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/buzzrick/32/473_2.png) [@buzzrick](https://qa.fmod.com/u/buzzrick)\ **Post date:** [June 17, 2019, 4:30am UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/1 "2019-06-17T04:30:31Z")
We’re having some frustration with the Unity integration of FMOD studio. The FMODStudioSettings.asset file has a “sourceProjectPath” setting in it, which is machine specific. Everyone in our team has a different project folder path (usually within their home folder), and as a result every keeps touching the settings file, and checking it into source control. Can we make that setting NonSerialised so that it doesn’t keep getting changed by every different user? ---
**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\ **Post date:** [June 20, 2019, 5:21am UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/2 "2019-06-20T05:21:30Z")
The sourceProjectPath should only be updated when the path in the FMOD Settings is changed, after the first time it is set that path will be used to get the correct directory for the current platform. What version of FMOD are you using? ---
**Author:** ![buzzrick](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/buzzrick/32/473_2.png) [@buzzrick](https://qa.fmod.com/u/buzzrick)\ **Post date:** [June 24, 2019, 11:26pm UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/3 "2019-06-24T23:26:34Z")
I’m using the new 2.00 of FMOD Studio. The frustration that I’m having (which I probably haven’t explained very well) is that whenever we pull the unity project, we need to re-point the FMOD project location, which then updates the sourceProjectPath setting. Then every time we check our project changes into source control, we need to remove that change from the commit, and often this step is forgotten. Then whenever everyone else in the team pulls the latest updates, they will again need to re-point the FMOD project location. The problem here is that the sourceProjectPath value is a machine specific value, that gets pushed into a shared source control system. ---
**Author:** ![csumsky3](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/csumsky3/32/494_2.png) [@csumsky3](https://qa.fmod.com/u/csumsky3)\ **Post date:** [June 27, 2019, 9:41pm UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/4 "2019-06-27T21:41:26Z")
Yea this is happening to us too since we updated to FMOD 2.0. Wasn’t happening previously. But now just like @buzzrick is saying, each individual has to re-point to the project every time they pull a change to the settings. ---
**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\ **Post date:** [June 28, 2019, 12:20am UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/5 "2019-06-28T00:20:47Z")
We are currently looking into this and will hopefully have a fix in the next release. ---
**Author:** ![sleepily](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/sleepily/32/523_2.png) [@sleepily](https://qa.fmod.com/u/sleepily)\ **Post date:** [July 5, 2019, 1:37pm UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/6 "2019-07-05T13:37:19Z")
Hi @buzzrick , I saw this and a solution might be using a relative project path. So instead of having the full system specific path, you could use `..\\.fspro`. Where the `..\` indicates that fmod should look one level higher in the folder hierarchy relative to the contents of the unity project. So you can use that if your project structure is like this: - Project root - fmod folder - unity project folder Should the fmod folder be inside your Unity project, you can do this: `some folder\fmod folder\fmod project.fspro` for - Project root - unity project - some folder - fmod folder The problem with that is that [this issue](https://qa.fmod.com/t/streamingassets-fail-to-copy-due-to-invalid-path-name-in-eventmanager-cs-upgrade-to-2-00-00-integration/14479/8) arises, since the full path is not correctly calculated from the relative one. As soon as this is fixed, you should be good to go. ---
**Author:** ![sleepily](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/sleepily/32/523_2.png) [@sleepily](https://qa.fmod.com/u/sleepily)\ **Post date:** [July 5, 2019, 4:22pm UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/7 "2019-07-05T16:22:11Z")
Hello again, I fixed the error. When using relative paths, FMOD did not account for getting file names from that. So I guess, since the file cannot be found in the system, it cannot correctly get the file name from the bankRef path, which in turn saves a path inside bankRef.name I fixed it inside the EventManager, but I guess you should go ahead and fix it where the relative paths aren’t accounted for in the first place. This is on version 2.00.02 by the way. Here’s the fix: ![GitHubDesktop_NoQRcs8RNZ](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/1X/54c9f0379011bca1cad6aadb894ab8d4b9b13074.png) I hope this helps in the fixing process, too. @cameron-fmod ---
**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\ **Post date:** [July 11, 2019, 10:30pm UTC](https://qa.fmod.com/t/fmodstudiosettings-asset-sourceprojectpath-setting-saved-per-machine/14775/8 "2019-07-11T22:30:26Z")
Thanks for the info, very helpful. We are aiming to have this fixed for the next release.