Build 1578757 - K:/TURE/Rocket_CL1578757
Specs Windows 7 Professional English, i7-3770K, 32GB RAM, GTX670 4GB driver 306.23 , UAC off
Description I can no longer open two of my blueprints. Opening them leads to an instant crash. My level also no longer opens, because it refers to these blueprints. I can not right click and delete the erroneous blueprints either as right clicking too crashes the editor.
I eventually deleted the two assets in windows explorer, and now my level opens up again but I lost my blueprint work…
I am not sure how this all happened. I don’t think I was doing particularly weird stuff in Blueprint, just basic messing around. I was doing work with functions. I saved the package at some point, and then continued working on. Five or so minutes later the editor randomly crashed (happened a few times before). Upon restarting it, I could no longer access some of the blueprints I had open before the crash.
Repro Open my package Htest2 and try to access or right click the MyGameInfo or MyHud. The others work.
Results Crash
Expected To not crash.
[download package with crashing content][1]
[1]: camactortest2.zip (30 KB)
Possibly related to enabling Pure on a function. That crashes it every time for me when I try to play the game, though it doesn’t corrupt my stuff.
Hello!
We’re looking through your submitted files now to track down the origin of the crash(es) you’re getting. In the meantime, if you need to get back into your Blueprints or Level Blueprint, try the following:
-
Navigate to your \Engine\Config\ folder
-
Open BaseEngine.ini in your text editor of choice.
-
Look/Search for the following sections within that file:
[Engine.Blueprint]
bRecompileOnLoad=true
[Engine.LevelScriptBlueprint]
bRecompileOnLoad=true
-
Set those two variables to false
-
Save these changes
-
Launch your editor
-
Try to open your Blueprints and/or Level Blueprint
You should be able to open both without crashing and be able to make any changes or recover what you were working on. Again, we’re looking into the files you attached to narrow down where the crash is originating so we can prevent it from happening in the future.
Let us know if you continue to run into this issue.
Thanks!
-Steve
This was fixed at the end of last week, so please let us know if the problem persists with the next beta! The good news is this shouldn’t have corrupted your content, so once you get the new build, everything should work as expected.