Inherited Blueprints cause fatal error when launching packaged .exe

Hi there,

I am working on a Third person action game that has a wide range of weapons that the player can use. I created a basic inheritance chain for the weapon system that uses a ‘master’ weapon class that is then inherited by all subsequent weapons e.g. spear, sword. These classes have been implemented entirely through blueprint.

This inheritance hierarchy works in 4.1.1 but upon upgrading to 4.2 any windows packages made crash with the following fatal error:

If I remove the sub-classes spear and sword from the scene but place an instance of the master weapon class in the scene the package runs with no issues.

Also, I can no longer ‘play’ our build using a stand alone game option with or without the weapons in the scene, it it reports a crash has occurred at: C://Program with the following error:

Assertion failed: Blueprint->SkeletonGeneratedClass != NULL [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.2\Engine\Source\Editor\UnrealEd\Private\Kismet2\BlueprintEditorUtils.cpp] [Line: 2906]

along with a long list of filename not found lines regarding dlls such as:
Address = 0xe2a9d275 (filename not found) [in C:\Program Files\Unreal Engine\4.2\Engine\Binaries\Win64\UE4Editor-Core.dll]

I will attach the assets for these blueprints as a zip at the end of this post. This weapon inheritance is crucial to our project and any help regarding this issue would be greatly appreciated :slight_smile:

Cheers,
B

[link text][2]

Hi MurdoNZ,

We recently fixed an issue related to Blueprints with references to each other crashing the Editor. The fix is currently up on GitHub in the 4.2.1 preview version. 4.2.1 will be available as a release version soon, but you can get it now if you are using a version of the Editor built from source.

If this does not fix the issue you are seeing, please let us know.

Fantastic! Thanks for the update!

Hi MurdoNZ,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.