# AssetLookup continuously causing source control issues **URL:** \ **Category:** FMOD Studio\ **Created:** [June 15, 2022, 1:17am UTC](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894 "2022-06-15T01:17:25Z")\ **Posts on this page:** 4\ **Page:** 2
**Author:** ![Mordi](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mordi/32/5156_2.png) [@Mordi](https://qa.fmod.com/u/Mordi)\ **Post date:** [August 9, 2023, 6:49pm UTC](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894/21 "2023-08-09T18:49:04Z")
We’re typically opening the project using Unreal Game Sync, which I assume opens the .uproject file. We are indeed using the built-in source control in UE. Sometimes we open the Helix Perforce client directly and revert/commit, etc there. ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [August 10, 2023, 12:27am UTC](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894/22 "2023-08-10T00:27:04Z")
Hi, thank you for the information. For the `AssetLookup` and `BankLookup` an option is to ignore the files from Source Control: [Unreal Integration | User Guide - Generated Assets](https://fmod.com/docs/2.02/unreal/user-guide.html#generated-assets). Let me know if that solution works for you. ---
**Author:** ![Mordi](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mordi/32/5156_2.png) [@Mordi](https://qa.fmod.com/u/Mordi)\ **Post date:** [August 15, 2023, 5:34pm UTC](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894/23 "2023-08-15T17:34:43Z")
Hey Connor. We ended up fixing this issue, and some related issues by excluding all generated files from source control, as your documentation states. We had some trouble doing so at first. We initially assumed that Perforce’s .p4ignore files are equivalent to .gitignore files in git. This turned out to be false. A .p4ignore file is only applied if the P4IGNORE environment variable is set, and this has to be set up on a per-user basis. It doesn’t apply for all users, like a gitignore file would. What we ended up doing to fix this, was to set up our Perforce server’s file permissions to not allow anyone to open/modify any generated files in the Content/FMOD folder. This has to be done by an admin, but once it’s done, generated assets are effectively excluded from source control. We’ve only been verifying that this works for a few days, but seemingly everything works nicely now. As an aside, in the link you posted there is a screenshot showing the FMOD folder, with a red square saying “Generated assets”. I found this to be a bit confusing, as the image also shows subfolders named “Desktop” and “Mobile”, which I assume contain .bank files which should not be excluded from source control. ---
**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\ **Post date:** [August 15, 2023, 11:37pm UTC](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894/24 "2023-08-15T23:37:30Z")
Hi, Good to hear it is working and thank you for the detailed solution. > [@Mordi](#): > > As an aside, in the link you posted there is a screenshot showing the FMOD folder, with a red square saying “Generated assets”. I found this to be a bit confusing, as the image also shows subfolders named “Desktop” and “Mobile”, which I assume contain .bank files which should not be excluded from source control. You are correct, there is a task to fix this. Thank you for letting us know. [Previous page](https://qa.fmod.com/t/assetlookup-continuously-causing-source-control-issues/18894.md?page=1)