Description

The following can be observed in the output log for the various BuiltData.uassets:

Cmd: OBJ SAVEPACKAGE PACKAGE="/Game/Maps/Highrise_Audio_BuiltData" FILE="../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset" SILENT=true
LogSavePackage: Save=1.42ms
LogSavePackage: Moving '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Saved/Highrise_Audio_BuiltData92274ABC41CAFBE251932382F832725C.tmp' to '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset'
LogFileManager: Warning: DeleteFile was unable to delete '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset', retrying in .5s...
LogFileManager: Error: Error deleting file '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset'.
LogSavePackage: Error: Error saving '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset'
LogSavePackage: Display: Finished SavePackage ../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset
EditorErrors: New page: Save Output
EditorErrors: Warning: Error saving '../../../../../Builds/Release-4.17/Samples/Games/ShooterGame 4.17/Content/Maps/Highrise_Audio_BuiltData.uasset'
LogSavePackage: Save=640.07ms
Steps to Reproduce

Repro:

  1. Open QAGame in the editor.
  2. PIE - Standalone Game

Result:
Pop up messages for various *_BuiltData.uasset fail to save. Standalone window opens after skipping all of them.

Expected:
All of the various BuiltData.uassets successfully save.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-47068 in the post.

0
Login to Vote

Fixed
ComponentTools
Affects Versions4.17
Target Fix4.17
Fix Commit3534700
Main Commit3555226
Release Commit3534700
CreatedJul 10, 2017
ResolvedJul 12, 2017
UpdatedApr 27, 2018
View Jira Issue