Hi, we’ve been seeing an issue for a while. We have FMOD hosted in perforce, and our UE4 project hosted in Github. We can set the build output directory (via UE4 validate fmod) and this works just fine, but when we try to commit changes to perforce, we get the following error:
13:12:24 runP4: error running command: -z tag -r0 -vnet.maxwait=10 -p ip:port -C none -u myusn -P mypwd -c myworkspace edit pathToUe4bank.bank
13:12:24 runP4: Path ‘pathToUe4bank.bank’ is not under client’s root ‘pathtofmod’.
I just noticed in the log that we’re spamming this error for pretty much every bank in the project when we build too (not just when we commit changes).
For committing, the work-around has been to first remove the build path, then commit.
I don’t quite understand why the build-path of FMOD should affect perforce’s path is not under client’s root error?