Blueprint Bug after converting to 4.4 (and then crash)

One of my blueprints, a very small one, is broken after converting from 4.3 to 4.4. I’ve attached a mockup screenshot as I can’t get back in and do a proper one as the editor now crashes (see below). The blueprint does not compile and reports an error about the “Character” input, which is a Pawn object.

It looks like some of the connections have been corrupted, as the screenshot shows. Re-connecting them does nothing, but I was able to fix this the first time by deleting the CustomEvent and Cast To BP_SpaceExplorer and re-creating them, but the problem returned when I closed and re-opened the editor and was now no longer fixable even though I re-created pretty much the whole blueprint.

The editor now crashes every time with the error code: !Id:e492b8da9a9630641fa98d3201d76118

This all happened in a fairly simple 4.3 project converted to 4.4 based on Code Flying. It initially worked (although I had to recreate the blueprint as described above). It still worked when I added blueprints for a starfield background, but then I closed the editor and compiled my C++ code after adding some simple code for moving the camera with the mouse, and now it crashes every time. Reverting all the changes does not help. Seems like the project has been corrupted.

Hope this helps to track down and fix the issues, because 4.4 looks very interesting.

Hey, Tarostar.

First things first, we need to find out what’s broken. Now, it could be the corrupted blueprint, or it could be the C++ code. I suspect the code, but let’s check the blueprint first. On your computer, go to C:\Users[Username]\Documents\Unreal Projects[ProjectName]\Content\Blueprints . From there, you can move the suspected blueprint elsewhere on your computer. If taking it out of that folder lets you open the project, then that means we’ve found the problem and can work on reproducing it (so we can fix it on our end!).

If that doesn’t allow you to open the project, then the problem is almost certainly in the C++ code, which would be a lot harder to diagnose.

As for getting your project working… if your main goal is just to have a working project, recreating the project in 4.4 should fix the errors. It would be great if we could narrow down the bug and find out exactly what’s causing it, though.

Thanks, I traced it down to blueprints. One of my item placeholder blueprints. Bit hard to know exactly what causes it as all the blueprints are so interconnected and the item placeholder blueprints inherit from each other, and so I can remove either the base placeholder blueprint or the laser item that inherits from it and everything is working. In other words, either blueprint loads fine on its own - and of course it all works ok in 4.3.

The only blueprint graph for these item blueprints is in the baseitemplaceholder and the scripts are really simple. I did screenshots of all of them, but the Comment button doesn’t work with screenshots uploaded.

I would like to know what the problem is and I’m sure you want to step on any bugs, so I’m happy to send anything else you might need or troubleshoot further. However, it is not urgent as I can keep working in 4.3 for now and I’m converting my HUD/Menu/Inventory from blueprints to C++ anyway.