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 ..\<your fmod folder>\<your fmod project>.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
- some folder
- unity project
The problem with that is that this issue 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.