# What is "BankLookup.uasset"

**URL:** <https://qa.fmod.com/t/what-is-banklookup-uasset/19443>\
**Category:** Unreal Engine\
**Tags:** ue5\
**Created:** [October 25, 2022, 9:55am UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443 "2022-10-25T09:55:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SoundTek\_Studio](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/soundtek_studio/32/3395_2.png) [@SoundTek\_Studio](https://qa.fmod.com/u/SoundTek_Studio)\
**Post date:** [October 25, 2022, 9:55am UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/1 "2022-10-25T09:55:31Z")

</div>

I noticed that this file always “gets changed” if I start UE. At least Plastic SCM says that…  
I don’t remember that file from earlier versions. It’s UE5 and FMOD 2.02.09

Edit.: It seems like every user in the project recreates this file. So, do we need it in the synced project?

---

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [October 26, 2022, 12:47am UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/2 "2022-10-26T00:47:43Z")

</div>

We have previously had reports of this when locales have not been imported for a project. Can you please confirm if you have locales in your FMOD Studio project that they are setup correctly in your Project Settings? i.e

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/5/5a87229b48e8adea13dcad418bc1c6d19f034df9.png)  
 ![image](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/c/cd9da8b079feac36607c18a7a94556d2914d77c4.png)

---

<div class="post-metadata">

**Author:** ![SoundTek\_Studio](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/soundtek_studio/32/3395_2.png) [@SoundTek\_Studio](https://qa.fmod.com/u/SoundTek_Studio)\
**Post date:** [October 26, 2022, 9:31am UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/3 "2022-10-26T09:31:33Z")

</div>

Yes, we just noticed, that our local naming was wrong.  
We had confused about “Deutsch” and “German” (Deutsch means German in German…)

---

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [October 26, 2022, 11:32pm UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/4 "2022-10-26T23:32:14Z")

</div>

Thanks for giving that a look- I think that ought to explain it. Are you still getting this issue with the correct locale settings checked in now?

---

<div class="post-metadata">

**Author:** ![SoundTek\_Studio](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/soundtek_studio/32/3395_2.png) [@SoundTek\_Studio](https://qa.fmod.com/u/SoundTek_Studio)\
**Post date:** [October 28, 2022, 8:52am UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/5 "2022-10-28T08:52:27Z")

</div>

Yes, the issue is still there. The FMOD validation finds no problem…  
However, we had another issue which is solved with the locales correction.  
We have german and English voiceover banks, with split metadata. It loaded English meta data, with german assets - that is now solved.  
The problem with the re-writing of the BankLoopup.uasset still exists.

---

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [October 30, 2022, 10:52pm UTC](https://qa.fmod.com/t/what-is-banklookup-uasset/19443/6 "2022-10-30T22:52:52Z")

</div>

Thank you for the additional information, I have reproduced this issue now by using banks with split metadata. This appears to be a bug- I have passed this onto the Dev team to fix in a future release.  
You can leave BankLookup.uasset unsynced in your repo in the meantime- as your project grows it may take longer to generate, which is why we recommend syncing it. But since it is being regenerated constantly it would probably be better to leave it unsynced for now.
