Hidden Dependencies, ModifyCook

Development Platform & Builds
, ,
21

IKRetarger: Fixed by CL 44939486 aka github commit https://github.com/EpicGames/UnrealEngine/commit/cab7792da74cdac4d23fdebb9b8e476977fd0f57\.

Automatic Serialize upgrades of old UPROPERTY TSoftObjectPtr to a UObject* do a LoadPackage, need to mark the LoadPackage as expected.

Water: Fixed by CL 45414753 aka github commit https://github.com/EpicGames/UnrealEngine/commit/b3551a40ab2c64cdc6af452d1630fde5d81e3337

WaterBodyComponent Serialize changes nullptr into a default object, need to mark the default object as a UsedInGame load.

Clouds: The callstack shows the LoadPackage comes from the AsyncLoader, when WorldPartition is loading an external actor for a map, which based on our experience with the previous error indicates a bug in the instancing code. The log message indicates it was loaded by /Game/SeventhCurse/Maps/PostProcessing/LI_BaseOverworldLight. What kind of asset is LI_BaseOverworldLight?

Mesh: The callstack shows the LoadPackage call comes from the cooker’s load of an independent asset, but this does not match the log message, which indicates it was loaded from a generated package; a generated package does not call LoadPackage during that callstack. Is it possible the callstack was captured from a different asset that also loaded hp_d_1x2a_SM, rather than being captured during the save of /Game/SeventhCurseBP/Maps/VS1/VS1_House3?

22

LI_BaseOverworldLight is a level instance

Looks like this material is part of the new day sequence system, referenced by the day sequence actor

[Image Removed]

I’ll try to follow up on the last one again asap.

23

DaySequenceActor: thanks, I should have thought to search for m_SimpleVolumetricCloud_Inst in code.

It is loaded by the constructor for ACelestialVaultDaySequenceActor::ACelestialVaultDaySequenceActor.

We will need to move that out of the constructor into an initialization hook that only gets called if the loaded VolumetricCloudComponent does not override the property. I’ll get a fix.

I also need to investigate why the callstack didn’t mention the ACelestialVaultDaySequenceActor constructor.