I’m attempting to get started with UE4 to replace our Unity development. One reoccurring problem that has nagged me while attempting to learn UE4, is project corruptions. It seems to come out of nowhere. I will exit the editor with a working test or modded tutorial, and when I next load the project, it will be corrupted and must be reloaded from a backup (or just start over since all I’m doing is testing and learning the API). It doesn’t happen every time, but it’s frequently enough that it would be a showstopper if it’s a normal behavior. It is always accompanied by an error listing as below, seeming to point to the project having inappropriate pointers and paths to my stuff. I am avoiding Xcode right now and use MacVim to do my coding, and the project Compile to compile it, which seems to work fine, though I was wondering if that could be the source of the issue. Actually though, I have no idea. It has happened on the ShooterGame twice or more, on the Vehicle game once, and on my tests from building wiki tutorial projects like FPSShooter (it’s happened a couple of times on this one). I’m concerned that the Mac version of the editor is fragile, but want to find out if it’s something I’m doing.
Has anyone else, using the editor under OS X 10.10, had such issues? Can they be fixed by hacking the project configuration files? Reloading projects minus recent changes would be a significant development stumbling block.
This is an example of the type errors I get in the Crash Reporter window only many more, I didn’t want to glut the post with the entire transcript (I send the crash reports but have no idea if anyone is looking at them). It shows 4.7, but has happened several times on 4.6.