Hot reload blueprint reinstancing issue

anonymous_user_c5d5991f
Thu, 15 Jun 2017 14:23:46 +0000
Blueprint

I’ve found a bug on 4.16 that seems to be a regression with relation to hot reload. These are the steps to reproduce it:

Create an empty C++ project

Create in C++ a UCLASS that extends APlayerController

Create in C++ a UCLASS that extends AGameModeBase

Compile

Create a Blueprint object that extends your C++ Game Mode class

Set the default player controller for that blueprint object as your own APlayerController subclass. Save

Create a level and set that game mode as the default game mode for that world. Save

Go back to C++, and add a UPROPERTY (can be anything) to both classes you created

Hit compile on the editor

When the code finished compiling and hot reloading, check the blueprint game mode class. The default player controller will be set to None instead of your C++ PlayerController subclass

This only happens if both the game mode and player controller changed their properties (needing to be reinstanced) in the same compilation

4 posts - 1 participant