5.6 project launcher always appends -unversionedcookedcontent

Development Pipeline & Plugins
, ,
1

Hi, it seems the new project launcher introduced in 5.6 always seems to append -unversionedcookedcontent, even when iteratively cooking (which, in the previous project launcher, displayed a warning letting the user know that versioning is required for iterative cooking). This allows you to get a local cook into a bad state with cryptic runtime crashes on null FProperty (de)serialization of blueprint class default objects immediately after engine startup (when it begins to load assets). It’s necessary to delete all cooked data that the editor previously generated for the target platform in order to get out of the bad state.

Digging deeper, it appears that IsCookingUnversioned() returns CookUnversioned which is true by default and is supposed to be overridden, but that doesn’t seem to be occurring anymore for some reason. Since we always want to cook versioned assets for our project, we can hack around this simply by returning “false” instead for now. That said, this is obviously not the real fix for the problem which is why we wanted to bring this to your attention, but hopefully the core problem isn’t too hard to resolve.

Thanks.

2

Hi Andrew!

Based on my conversation with the dev team, it seems the solution you found is essentially very close to the expectation. In short, unversionedcookedcontent is orthogonal to iterative cooking, and is controlled by a checkbox. In other words, CookUnversioned will not be overriden by iterative cooking, and has to be toggled off via the checkbox.

Hope this helps.

3

Ok, so the expected behavior is that there should be a user-facing checkbox then? Here’s a screenshot of the options available (note that the checkbox is not one of them):

[Image Removed]

4

Hello,

This is a bug with the new launcher. I filed an internal report so the dev team can add support for iterative cooking.

Regards,

Martin