Corrupt project

My blueprints kept breaking and now project crashes on loading project.

DxDiag
Log

https://.com/file/d/0B-fF6EOFJcFFVnpQanpBLUxzZzQ/view?usp=sharing

Thank you for your report. I will begin investigation into this issue as soon as possible. If I am unable to reproduce problem, or I need more information, I or another staff member will follow up with some additional questions for you. Otherwise, I will post an ‘Answer’ once I have logged issue in our bug database or we have a solution for it.

In meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide:

Thanks!

Hey Vesros,

When you say your Blueprints were breaking, what do you mean exactly? Were nodes disconnecting? Which version of engine are you using?

It’s possible this is related to a cyclical dependencies issue that has been resolved in 4.5. If you haven’t already, make a copy of your project in 4.5 Preview and see if it will open.

I was on 4.4.3 and a binary build. in one of blueprints and suspected offender nodes were disconnecting, i tried getting an image of node disconnect but was unable to.
A specific node would be disconnected from chain but next execution pin in chain would still be white like it was plugged in.

I was calling a function where i send pawn through and immediately cast pawn to MyCharacter and that is node that would break.
I Changed set up so i wouldn’t have to send pawn through there and there doesn’t seem to be any issues anymore and everything else is exactly same.

Have not tried with 4.5 and assume i can’t using launcher for updates?

You should be able to get 4.5 Preview through Launcher if you have an active subscription. Go to Library tab in Launcher, and click the “Engines+” at top. In new Engine slot that appears, choose Preview. That should get you 4.5 Preview. Then Launch in Preview and select your project to open, and it will give you an option to Open a Copy.

project launches perfectly fine on 4.5 and disconnect issue previously described looks like it should.

Thanks!