Search in

Sort by:

Everything Bug Reports

Current Space

Question Status:

All Questions With Answer With Accepted Answer

Quick results

Search help

Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both.
Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.

You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with
each other. Examples

Fatal Error while Cooking Content, w/o Reason!

0

While cooking the assets of my project, either during packaging or directly via the "Cook content for Windows" menu option, I get a fatal error from UE4. Problem is that there is no hint on why the cooking process fails, none at all (see full error trace at the bottom of this posting).

Here are some facts:

We are using the official 4.12.4 build (i.e. not the engine sources from GitHub)

It's a mixed BP and C++ project

Happens only with this project (apparently since upgrading to 4.12, but I am not sure about this)

The problem is reproducible, every time I try to cook

When I copy the whole project to another machine, then the error happens there as well

The same goes for our build server, which automatically fetches latest SVN changes

When I revert back to the last working version from our SVN server, then it works fine again

Later, when I do some modifications in one or more (BP) assets, then the error comes again

I tried to delete "Intermediate" and "Build" folders, but still the same error

What bugs me most ist that in some cases, after reverting back to a previous version from SVN that worked, I can carefully make only a small modification in one single BP asset, and then it still works (i.e. no cooking error). However, as soon as I do some more modfications, or change a couple of BP assets, then the cooking errors comes again.

We are trying to solve this issue since many days now, but without success. I am kinda desperate -- shipping date is approaching soon, but I have no clue what else I could do. Feel totally lost here :(

I am grateful for any ideas you can share.Thanks in advance for your help!

Here is the full cooking trace:(The log file mentioned in this trace is basically the same, again without reason for the error)

I also tried with "Shipping" configuration and "For distribution" flag, but still the same fatal error.

We updated to 4.12 mainly because we want to use the Sequencer for our in-game videos. And there some nice other new features, such as Actor merging and the pixel inspector. Last but not least there are also tons of new minor features and bug fixes in a new release...

Also I rather don't think that the upgrade to 4.12 is the reason for our cooking problems. Directly after the upgrade that error did not happen, only since a week or so.

Update: After some research and detective work, I found something. When I revert back from SVN to the last version that worked, I can cook fine. But when I open Visual Studio and rebuild the solution (in "Development Editor" configuration; compilation without errors or warnings), then the aforementioned cooking error happes again.

So it is definitely not related to a (change in a) BP asset, as assumed and described above. Instead, it is somehow related to compiling the project in VS. Fun fact: The code is exactly the same as from SVN, i.e. I made no changes in the code. But still, after compiling this same code (that used to work), the cooking error occurs.

I tried to delete "Build" folder and regenerate the VS solution files from the .uproject file. This is the list of files that lead to the problem. When I revert them back from SVN, then it works again.

For the records: The problem was a piece of our code, which compiled fine, but led to an error during runtime. Apparently UE4 runs the executable while cooking, but it doesn't mention anything like that at the error message. I was able to track this bug down by looking at the folder Saved/Logs/ within our project directory. There you can find mini dumps, which you can open in Visual Studio. There I started debugging and in the callstack I could find the problematic function call in our code.