AssetLookup continuously causing source control issues

FMOD Studio
#1

So i’m working with a team on a project, it seems like every time I add something from FMOD to the projects we get an issue with the “AssetLookup”

here is a screenshot.

In this instance, it says that the asset lookup is checked out by another Dev, but all they did was open the Unreal project file. Neither of these two are doing anything inside of FMOD, but it’s now causing problems for the programmers.

Any idea why this is happening?

I have Fmod connected to the perforce server as well, and it seems to be working correctly, but this is getting really frustrating as it seems that every time I do anything with the project, we have to deal with this.

#2

We previously had an issue with private integration data being regenerated every time the editor opened but this should have been resolved in 2.02.05. If you are below 2.02.05 then I suggest updating.Otherwise, can you please tell me what version of FMOD and you Unreal are using?

1 Like
#3

Hi, Jeff. We are using 2.02.06 integration with Unreal Engine 4.27 and also getting this warning.

#4

The issue persists in 2.02.07.

#5

Hi,

I was not able to recreate the issue using Unreal source control in conjunction with Git.

What source control are you using?

#6

Hey Connor,

We’ve upgraded to 2.02.08 integration with UE and we’re using Perforce. But we’re still seeing AssetLookup conflicts.

#7

We were able to reproduce the issue when using Perforce. I have passed it on to our development team. Thank you for bringing this to our attention

#8

Is there any workaround for this or commit I can backport to mitigate this issue for content creators? We’ve recently upgraded and this is plaguing us with editor friction.

Thanks!

#9

Hi,

Currently there are no workaround, and the issue is still in our list to look at. What version were you using before you updated and started experiencing this issue?

#10

When the banks on a given machine change (eg. from source control or locally built) the FMOD plugin will attempt to generate any new assets and modify any that require modification. This will occur if the editor is open or the next time it is opened. If events, buses, etc have been added or removed from the FMOD Studio project, the AssetLookup.uasset will be modified and checked out of source control (as exclusive checkout, which appears to be the default for .uasset files).

Hypothetical:

  • Sound designer builds new banks and checks them in to perforce.
  • Game designer gets latest and opens unreal project.
    (At this point the banks and generated assets are out of sync).
  • The FMOD plugin detects the difference, modifies the AssetLookup.uasset. This is now checked out in perforce/source control. (But not checked in yet.)
  • The next person attempts to get latest and open the unreal project.
  • The FMOD plugin detects the difference, now when it tries to modify the AssetLookup.uasset it is already checked out (as exclusive checkout) and UE throws a warning dialog.

Basically the AssetLookup.uasset is being checked out on one machine because the banks have changed, then other machines are trying to do the same thing and hitting a wall because the .uasset is already exclusively checked out.

Initially these files were needed in source control if you are running a build server that doesn’t open the editor (which triggers the asset generation), but now we have support for the Commandlet which can be run from command line and will generate the required assets.

We are looking into ways we can improve the workflow but for now we can recommend removing the generated assets from source control and using the commandlet if using a build server.

1 Like