Cook fails in 4.16 preview 1
When upgrading to 4.16 cooking our project stopped working with the following error:
[2017.04.30-00.41.46:086]UATHelper: Cooking (Windows): Cook: LogOutputDevice:Error: Ensure condition failed: GetSuperClass() [File:D:\Build\++UE4+Release-4.16+Compile\Sync\Engine\Source\Runtime\Engine\Private\BlueprintGeneratedClass.cpp] [Line: 1236]
Here is a complete cooking log:
I have not managed to reproduce this in a new project so here is our complete project split in to 10 files because it is closer to 10Gb in size:
To reproduce, simply open the project and cook for windows on a 4.16 version of unreal engine.
asked Apr 30 '17 at 02:07 AM in Packaging & Deployment
Fixed it by opening a copy in 4.18.0 and fixed all warnings and errors. There was a crash when opening the project in 4.18.0 and logs revealed it was crashing on 1 generated static mesh from a skeletal mesh to start with.
Afterwards I could package my project fine. Although it could be if you package from scratch instead of incremental it could work as well. That as my next attempt if this one should have failed but luckily it worked for me at least.
Hope this helps someone!
answered Nov 02 '17 at 12:03 AM
I had this issue to and you wouldn't guess what it was, for me it was a class reference to an actor in a data table, the referenced actor was the Ensure condition, the error come from a datatable row handle reference within another actor once this reference was cleared to none the error disappeared, so this issue should be looked into because it seems to be looking at class reference to see if its valid or not and its breaking at some point.
just to add to this long post -
I originally arrived here a year ago - tried many suggestions from over the net The bug was so painful.
You could dig deeper and deeper on ue4.16 and clear a few bps and get lost. For a time I rolled back on git and compiles were fine ... then something upset my project again two days ago and this dreaded error popped up! I decided to attempt to hammer it out again -
I expect there are better debugging techniques ... but by far the best solution for me was to install 4.17 - open the project - and immediatley it showed the culprits on the compile test. I believe that the compile manager or error messaging is far better.
Follow this question
Once you sign in you will be able to subscribe for any updates here