Cook still fails in 4.16

Development Platform & Builds
, , , , ,
1

We have previously failed to migrate to 4.16 from 4.15 due to a cooking bug: Cook fails in 4.16 preview 1 - Blueprint - Unreal Engine Forums

I have choose to make this a new report as I’m not sure how much Epic monitors old posts.

We have now tried again but the problem persist. We have removed all warnings and tried every workaround we can to get it to cook.

Here is our complete build and cooking log

It fails on:
Ensure condition failed: GetSuperClass() [File:D:\Build++UE4+Release-4.16+Compile\Sync\Engine\Source\Runtime\Engine\Private\BlueprintGeneratedClass.cpp] [Line: 1236]

To reproduce download project below:

https://valhalla-game.com/proj/valhalla-2017-07-16.rar

And just select File → Cook content for windows.

What we have tried:

We have removed every reference to datatables as there we some indication that datatables where involved but that did not help.

We tried removing the item that it currently breaks on but then another item breaks when cooking and it continues like that for every item we remove (ended up removing more than 20 assets before giving up).

There are some suggestions to the previous bug report that this is caused by Circular dependencies. But if that is the case then Epic needs to give us some way to debug this and warn for the specific type of Circular dependencies that cause this kind of bugs.

If you want to get quickly in contact with me then send a message on discord: PhroZen#4745

Best Regards

2

I’m afraid not. We are still at 4.15 and our solution right now is to rewrite everything in c++. Massive work but bugs like this makes us think that it is worth it (as we think this is a blueprint issue).

3

Did you ever figure out the cause of this? We are currently experiencing the same thing when upgrading to 4.16 from 4.15.

I can fix some by checking the asset in reference viewer and cleaning up any strange references, but a new one always fails with the same error on the next cook I’m stuck on one now that reference viewer claims has a reference to another blueprint, but I can’t find any node or property that actually has the reference.

4

I was afraid of that, we’ll lose about a week’s worth of work if we have to go back to 4.15 at this point, ugh. Good luck with your c++ conversion!

5

Looking at the log I believe that might be a problem on draggableActivatedItemIcon asset. Can you check if there is any compile error on it or on its parent class?