Answered
0
0

The strange thing is that all of these events work just fine in the build. That said, all of these errors seem to be from events where I’ve either changed the name, or replaced the event with another event. All of these events get loaded from the .bank files as temporary Uassets. Does anyone know why these errors are showing up and how to get rid of them?

It’s making it impossible to read our log because I’m getting hundreds of these…

“01-Dec-2016 13:56:41 UE4Editor-Cmd: [2016.12.01-21.56.41:809][ 0]LogInit:Display: LogCook:warning: Unable to find cached package name for package /Game/FMOD/Events/Music/Music_Player
01-Dec-2016 13:56:41 UE4Editor-Cmd: [2016.12.01-21.56.41:810][ 0]LogInit:Display: LogCook:warning: Unable to find cached package name for package /Game/FMOD/Events/Crowd/SML_Test/AMB_CLAP_SML
01-Dec-2016 13:56:41 UE4Editor-Cmd: [2016.12.01-21.56.41:810][ 0]LogInit:Display: LogCook:warning: Unable to find cached package name for package /Game/FMOD/Events/Vehicle_Engines/MX_Test_Engine”

  • You must to post comments
Best Answer
0
0

While this warning is annoying, it is benign and can be ignored.

To work around this you will have to modify Unreal Engine code:

PackageName.cpp

 bool FPackageName::IsScriptPackage(const FString& InPackageName)
 {
      if (InPackageName.StartsWith(FLongPackagePathsSingleton::Get().ScriptRootPath) || InPackageName.Contains(TEXT("FMOD/")))
           return true;
      return false;
 }

This has been brought up with Epic and they agree it is a bug https://issues.unrealengine.com/issue/UE-41012

  • You must to post comments
0
0

From what I can see, the uasset sometimes doesn’t seem to update properly and keeps a reference to the old event (in among the gibberish). I am unsure of a fix for this but I will continue looking into it.

  • JB
    • JB
    • 8 months ago

    Thanks! I can’t seem to find these elusive uassets either.. Let me know if you come across something.

  • You must to post comments
0
0

We’re having the same issue since upgrading to 4.13. We have a cached package warning for every event created before the upgrade.

  • Cameron Baron

    Just for clarity, is that upgrading from 4.12 to 4.13?

  • Alec Brady

    We went from 4.11 to 4.13

  • JB
    • JB
    • 8 months ago

    In my case, we’ve gone from 4.11, 4.12 and to 4.13 with these events.

  • Cameron Baron

    Just to let you know, I am still looking into this.
    It looks like this is happening for all cooked builds, not just migrated from an earlier engine version.

  • You must to post comments
Showing 3 results
Your Answer

Please first to submit.