Unknown cook failure

Development Platform & Builds
, , , , ,
1

link text

the output log for the packaging was a whopping 35mb so I took out a chunk from the middle which alternated mostly between these two kinds of logs

OCULUS: Info: 01/14/16 23:05:13: [From Service] 01/14/16 23:05:13: OVR::SensorDevice - Closed ‘\?\hid#vid_2833&pid_0021#7&7b55afd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
OCULUS: Info: 01/14/16 23:05:13: [From Service] 01/14/16 23:05:13: OVR::Win32::HIDDevice - Closed ‘\?\hid#vid_2833&pid_0021#7&7b55afd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’
OCULUS: Info: 01/14/16 23:05:13: [From Service] 01/14/16 23:05:13: OVR::Win32::HIDDevice - Opened ‘\?\hid#vid_2833&pid_0021#7&7b55afd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’

and

MainFrameActions: Cooking (Windows): UE4Editor-Cmd: [2016.01.14-23.08.39:879][ 0]LogCook:Display: Cooking /Game/FirstPersonBP/GRASSL~1_Mat → xxx.ussat

This is a larger architectural visualization project for a residential house, and the amount of detail in the meshes along with the number of spotlights for every fixture in the house makes it a big file as well. This is my first project using ue4 and with a lot of tweaking with the meshes and watching out for overlapping lights I can get a faster and higher quality file, but I hope this doesn’t affect the abilty to package the product to use/edit on a different machine. I’m currently using windows 8 through bootcamp, packaging for windows x64.

Additionally, the vr preview is greyed out, not sure what the issue is here either. any help is appreciated, thanks!

2

Hello hkameda,

From looking at your logs, the errors that standout seem to be related to some blueprint assets having some issues.

LogBlueprint:Error: [compiler 333_D_WOOD_object_61] Error The property associated with Origin Door 2 could not be found
LogBlueprint:Error: [compiler 333_D_WOOD_object_61] Error The property associated with Open could not be found

It seems that there are some null references being found. Could you check these blueprints to see if they may be problem? If you cannot find an error yourself, you could try migrating those assets in question to another project and deleting them from the current project to see if the packaging will succeed. They can always be brought back from the other project.

3

We haven’t heard from you in a while, hkameda. Are you still having packaging problems? If so, have you been able to try the suggestion from my previous comment? In the meantime, I’ll be marking this issue as resolved for tracking purposes.