i know there are several posts about this from before, however none provided answer in any good fashion about this problem.
We have a pure blueprint project started from an empty template.
50% of the time when working with the blueprints ex making big changes in blueprint like structs, adding new functions, rewiring etc messes up the project somehow. So, when restarting the editor the project wont load and crashes the editor at “93 or 96%”.
It then takes hours to move things out from the project folder, trying to find any culprit, trial and error. Eventually it gives in and can open.
Is there a way to avoid these things or even better, a better error report upon editor crash, that you can understand what goes wrong beforehand, or catch it upon exiting etc…
thanks for any answer, its extremely annoying and a real showstopper.
Its like you wirte a piece of code and the next time you open visual studio each and every letter is gone.
after some hour moving files out from the folder, restarting etc its solved…
I would however want to know how to avoid these things in the fuiture because its quite time/energy consuming and very dangerous for the project / Highrisk if sometime it cant be fixed by hacking anymore.
2 - Well the issue is… Often after extensive work with blueprints the project wont load after editor restart. I then have to move blueprints around on the disk until it opens, try to recompile some variables referencing structs, move files back and then hope for the best and keep doing that until its solved.
I would be more than happy to take a look at your project if you would like to provide it. You can zip in down and send it to me in your next post. This can be down with google drive or dropbox. I hope this helps.
I have narrowed it down to your gamestate. “dd_gamestate”, and I believe that you will need to replace this blueprint. You can simply delete the blueprint before opening the project and this will keep the project from crashing. If you would like to be able to view the blueprint so that it will be easier to rebuild, you can copy and past it into a clean project’s content folder. The references will be broken but you will still be able to see the logic. This way it’s a simple matter of rebuilding that one blueprint. From what I could gather, this blueprint had a broken/bad reference in it. I hope this helps.
yes ill rebuild that and se where it gets me.
thanks for your valueable time and for looking at it, it did indeed start more consistent without it. State and Mode blueprints are problaby the oldest ones.
im also considering starting the project from scratch wich probably will get me more stable blueprints since they are a mix from previous versions converted up to 4.7.2.