When cooking world partition maps, it automatically writes out several maps in a "Generated" folder below the location of the map in the editor. In the repro above, this will create maps such as /Game/Maps/NewMap/Generated/258CF4B3C3EQ3YYV8GYMXMRA0. These are temporary maps that should never be loaded directly. However, because they are inside the same folder as the editor map, the AssetManager will scan and try to register them as PrimaryAssets. The Lyra repro works because it is already set up to scan /Game/Maps for primary assets.
Prior to 5.4 this would register those maps as primary assets which wasted memory and confused the asset manager. They could not be loaded properly. In 5.4 (CL 29430228 on Main) the generated maps were changed to not register as primary assets which fixed the problem. However, if they are set up to scan in those folders it will cause a warning in cooked builds as described in the repro steps.
Expected behavior:
No warnings starting with LogAssetManager (ignore any other warnings as they are irrelevant)
Broken behavior:
If this is still broken you will see several warnings in the log similar to this:
LogAssetManager: Warning: Ignoring primary asset NewMap - PrimaryAssetType Map - invalid primary asset ID LogAssetManager: Warning: Ignoring primary asset NewMap - PrimaryAssetType Map - invalid primary asset ID LogAssetManager: Warning: Ignoring primary asset NewMap - PrimaryAssetType Map - invalid primary asset ID
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-216073 in the post.
0 |
Component | UE - Foundation - Core - Cooker |
---|---|
Affects Versions | 5.4, 5.5 |
Target Fix | 5.5 |
Fix Commit | 34573294 |
---|
Created | May 29, 2024 |
---|---|
Resolved | Jun 21, 2024 |
Updated | Jul 20, 2024 |