Engine crash during convert from 4.4.3 to 4.5.1

I have tried multiple times to convert a mobile based project from 4.4.3 to 4.5.1 however every time i try this, the engine crashes when it opens that project in 4.5.1. So for example, the project is currently 4.4.3. I’ll launch 4.5.1 and select the 4.4.3 project. It will prompt to copy or convert in place. I’ve tried both options. It appears to be ok during conversion, but then when the project is launched, the engine crashes. The log only states a machine id and account id. any thoughts on how to trouble shoot this?

Additional information that may help…i have tried this conversion with a different project before (PC based), and it worked fine. But i just don’t know how to troubleshoot this kind of issue for a project specific bug like this. maybe it’s mobile related?

More info: Created a new empty project in 4.5.1 and copied the assets from one of the failed converted folders into the new folder just for kicks. any attempt to open these in 4.5.1 also caused a crash.

In order to help us troubleshoot your issue, please provide your DXDIAG: (Windows Start Button>(search “dxdiag”)>Launch dxdiag>select “Save all information”>attach text file to your post.)

Also please provide the following logs:
the “UE4.log” Located: Engine\Saved\Logs\
…and the “ProjectName.log” Located: ProjectName\Saved\Logs\

Thanks

Here are the requested logs. Let me know what other information might be helpful as well. Thanks!

Logs

Hi Paradoc,

With the editor closed, create a copy of the original folder from Unreal Projects folder under your documents. You may have to copy to your desktop and drag the copied folder back into the Project Folder. Important: Keep your original 4.4.3 Folder and name the Duplicate something else.

In the duplicate project folder, right click the .uproject file and select “Switch Unreal Engine Version” and choose 4.5. Now open the launcher and launch 4.5.1. to an empty project. Now choose “Open Project” and select the project that should be highlighted as “selectable.” in the Launcher without having to convert. Does the project still crash?

Another thing you can do is create a new empty 4.5.1 project (as you have done). Close it. Open your 4.4.3 project and migrate your assets in separate blocks to the new project and see where it crashes. If you have animations, they are likely the assets causing the crash. If you find this is the case, the problem is related to a bug that is already reported and being addressed for the next build.

i tried the first approach mentioned above but the crash persisted. i did discover the following though: the assets appear to convert ok based on the second approach, and i can now open the empty project with migrated assets. however, every time i try to open any blueprint that references my game mode, the editor crashes. at this point i’m trying to pinpoint what aspect of the game mode is crashing the project, because everything works fine in 4.4.3. i’m trying to avoid re-writing my game mode, but that may be the necessary path at this point.

just found this thread which seems to be the same problem:
Thread link here

and…found the workaround!

deleted the game mode from content directory, and re-migrated it from the 4.4.3 project independently. after a lot of hard drive crunching ( i have a slow computer), it worked! but it has to be deleted from the windows directory. any attempt to delete it from within the editor will crash the editor.

word of warning to anyone that takes this approach: this will destroy all dependencies to your game mode. the result was that i had to re initialize all references to my game modes, huds and enums but this was the lesser of two evils.

Hi paradoc,

Glad to hear you were able to find a work around. With the information you provided as well as the link to the similar thread we were able to determine the problem is occurring at the same point between both projects. Hence, I have generated a bug report [UE-4755].

If this issue is fixed in a future build an update will be posted to this thread. Thanks for all the information you’ve provided in helping to resolve this issue!