Launch tries to load map from /Temp/Autosave/

Development Platform & Builds
, , , , ,
1

When I Launch my game in-editor (v4.1.1 on OSX 10.9) or as a Package it fails because it is trying to load from the crazy path /Temp/Autosaves/Game/Maps/UEDPCmain. My level’s source is in Content/Maps/main.umap. In-editor all the Play modes work fine. Help!

LogPlayLevel:Display: CommandUtils.Run: Run: /Users/darrin/src/ucupcake/Saved/StagedBuilds/MacNoEditor/Cupcake/Binaries/Mac/Cupcake.app/Contents/MacOS/Cupcake ../../../Cupcake/Cupcake.uproject /Temp/Autosaves/Game/Maps/UEDPCmain -stdout -abslog=/var/folders/cm/cn60gc151p992x1r0ss4k56w0000gn/T/+Users+Shared+UnrealEngine+4.1/Logs/Client.log -Messaging -nomcp -Windowed -CrashForUAT "-InstanceId=0011000F003000050025023F1858A2F5 -SessionId=0011000F003000050025023F1858D595 -SessionOwner=darrin -SessionName='Play On Device' "
LogPlayLevel:Display: Cupcake: LogInit:Warning: Invalid InstanceId on command line: 0011000F003000050025023F1858A2F5 -SessionId=0011000F003000050025023F1858D595 -SessionOwner=darrin -SessionName='Play On Device'
<...>
LogPlayLevel:Display: Cupcake: [2014.05.16-00.38.03:565][  0]LogConsoleResponse:Display: LogLinker:Warning: Can't find file '/Temp/Autosaves/Game/Maps/UEDPCmain'
LogPlayLevel:Display: Cupcake:
LogPlayLevel:Display: Cupcake: [2014.05.16-00.38.03:573][  0]LogLinker:Warning: Can't find file '/Temp/Autosaves/Game/Maps/UEDPCmain'LogUObjectGlobals:Warning: Failed to load '/Temp/Autosaves/Game/Maps/UEDPCmain': Can't find file '/Temp/Autosaves/Game/Maps/UEDPCmain'
LogPlayLevel:Display: Cupcake:
LogPlayLevel:Display: Cupcake: [2014.05.16-00.38.03:573][  0]LogUObjectGlobals:Warning: Failed to load '/Temp/Autosaves/Game/Maps/UEDPCmain': Can't find file '/Temp/Autosaves/Game/Maps/UEDPCmain'
2

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes.

If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, please submit a new report for it.

Thank you.