Updated: Changing a procedural splineMesh to being a closed loop causes maps to crash on load

Okay, I’ve figured out what was causing the crashes. Changing a procedural splineMesh blueprint to being a closed loop causes maps saved before that change was made to crash on load

To reproduce:

  • Create a procedural splineMesh blueprint (I used this method): UE4 Tutorial: Add spline-meshes procedurally - YouTube
  • Create a map (I’ll call it map1) and add that procedural splineMesh blueprint in.
  • Save that map
  • Create a new map (I’ll call it map2) and add that procedural splineMesh blueprint in.
  • Edit the procedural splineMesh blueprint object to have a closed loop spline (note that map2 continues to work just fine, and can be opened and closed without issue)
  • Save everything
  • Open map1 - the editor will crash.

Sorry if this is convoluted - there’s probably a simpler way to reproduce this, but this is what works for me.


Old Post: 4.7.6 Project crashes on map open

My 4.7.6 project crashes (to the crash reporter) when I open my map.

The project worked fine until recently. Last time I was using the editor, one small test map (not the map in question) refused to save due to not being able to locate a dependency (or something similar - can’t quite remember). I quit without saving that map, since I couldn’t get the error to resolve. Next time I went to open the editor, it would crash on startup. Other posts advised to change the default map in the DefaultEngine.ini to “/Engine/Maps/Templates/Template_Default”. This change allowed me to open the engine, but if I attempt to open any other map (not the test map) a crash occurs. I can create new maps with all the same content, but not open any of the old ones.

Project details:

  • Fairly small project
  • Only blueprints, no c++
  • Using the launcher version of the editor, not github.
  • OSX 10.10.1

crash log: https://gist.github.com/hhhudson/26feb26bd4e991d39f81

Additionally, copying a backup (from a few days ago) of any map in and attempting to open produces the same result.

I’ve figured out what was causing the crash, and updated the post accordingly.

Hi SOFT SPOKEN,

Thank you for the report. I was able to reproduce the crash in 4.7.6 but this is now fixed in our latest internal build. You should see this working properly in a future update.

Cheers,

TJ

wunderbar! Thank you.