LogLinker:Warning: Can't find file

Hi there!
I’m seeing the following warnings when starting up my project:

[…]
SourceControl: Info Source control is disabled
LogLinker:Warning: Can’t find file ‘/Game/TopDownBP/TopDownOverview’
LogLinker:Warning: Can’t find file ‘/Game/TopDownBP/TopDownOverview’
LogUObjectGlobals:Warning: Failed to find object ‘Class /Game/TopDownBP/TopDownOverview.TopDownOverview_C’
LogEngine: Initializing Engine…
[…]

I had that asset in my project before and deleted it at some point. I guess I could resolve this warning by re-adding and re-removing it, but what I’m interested in is…

How do you debug such a warning? Since the log doesn’t tell me anything about what component tried to access this asset, I have no idea where to even start looking. Checking every single BP’s Reference Viewer in my project to see if it holds a reference to it just isn’t viable.

Is there any feature to verify all assets used in the project and get detailed info if problems are found?

1 Like

No-one?
Maybe this would be a candidate for a feature request, then

I have exactly the same issue, where can I delete reference to TopDownOverview? I know that it’s the tutorial popup, but where can i remove references after it’s deleted?

Maybe try cleaning up re directors in the content folder?

It might be unrelated but its worth a shot.

I’m having the same issue. I migrated my levels and files to an empty project to clean up some corrupt plugin data, which worked beautifully. However, now I’m getting warnings from files that existed in the old project but were deleted before migrating and I’m not sure where they’re being referenced:

UATHelper: Packaging (Windows (64-bit)):   LogCook: Display: Cooking /Game/Neurorama/Core/Player/TestingVR/BP_VR_Flypawn -> C:/Users/me/Documents/GitHub/Neurorama/Saved/Cooked/WindowsNoEditor/Neurorama/Content/Neurorama/Core/Player/TestingVR/BP_VR_Flypawn.uasset
UATHelper: Packaging (Windows (64-bit)):   LogSavePackage: Display: Finished SavePackage C:/Users/me/Documents/GitHub/Neurorama/Saved/Cooked/WindowsNoEditor/Neurorama/Content/Neurorama/Core/Player/TestingVR/BP_VR_Flypawn.uasset
UATHelper: Packaging (Windows (64-bit)):   LogLinker: Warning: Can't find file '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive'
PackagingResults: Warning: Can't find file '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive'
UATHelper: Packaging (Windows (64-bit)):   LogUObjectGlobals: Warning: Failed to load '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive': Can't find file '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive'
PackagingResults: Warning: Failed to load '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive': Can't find file '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive'
UATHelper: Packaging (Windows (64-bit)):   LogLinker: Warning: Can't find file for asset '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive' while loading C:/Users/me/Documents/GitHub/Neurorama/Content/Neurorama/Core/Player/TestingVR/BP_Flypawn_VR.uasset.
PackagingResults: Warning: Can't find file for asset '/Game/Neurorama/MaterialLibrary/M_TextMaterial_Emissive' while loading C:/Users/me/Documents/GitHub/Neurorama/Content/Neurorama/Core/Player/TestingVR/BP_Flypawn_VR.uasset.

…etc

Found solution.

It’s done by deleting content (Boot.dcc) in …\AppData\Local\UnrealEngine\4.19\DerivedDataCache

And maybe in other DataCache folders :stuck_out_tongue:

Worked for me:

  • Go to Engine directory (C:\Users\Username\AppData\Local\UnrealEngine…)
  • Find “EditorSettings.ini”
  • Open it and search for the missing tutorial name.
  • Delete this line and save the file
2 Likes

this work !! thank you for save my time :slight_smile:

I had this problem, it just suddenly appeared on all versions of my project from different dates. I tried everything, deleting all cache folders for UE4 and VS, deleting the .vs files, reinstalling ue4 source build, turning off plugins.

What solved it in the end for me, was deleting the config folder! So if you get a lot of loglinker errors suddenly and c++ classes not getting found, try that!

thank you!