I’ve got a project created in 4.15 that has a few blueprints that don’t compile when ran as non-editor, but work just fine with PIE. I’m seeing things such as:
[2017.08.12-06.26.35:675][ 0]LogBlueprint:Warning: [BoxDropoff] 'Cylinder2' variable not found. Base class was probably changed.
[2017.08.12-06.26.35:678][ 0]LogBlueprint:Warning: [Compiler BoxDropoff] Warning Could not find a variable named "Cylinder2" in 'BoxDropoff_C'.
Make sure 'BoxDropoff_C' has been compiled for Get Cylinder2
[2017.08.12-06.27.00:571][ 0]LogStats: FPlatformStackWalk::StackWalkAndDump - 24.891 s
[2017.08.12-06.27.00:571][ 0]LogOutputDevice:Error: === Handled ensure: ===
[2017.08.12-06.27.00:571][ 0]LogOutputDevice:Error:
[2017.08.12-06.27.00:571][ 0]LogOutputDevice:Error: Ensure condition failed: pContextTerm != nullptr [File:D:\Build\++UE4+Release-4.15+Compile\Sync\Engine\Source\Editor\BlueprintGraph\Private\CallFunctionHandler.cpp] [Line: 384]
[2017.08.12-06.27.00:571][ 0]LogOutputDevice:Error: '/Game/Boxes/BoxDropoff.BoxDropoff:EdGraph_4.K2Node_CallFunction_7' is missing a target input - if this is a server build, the input may be a cosmetic only property which was discarded (if this is the case, and this is expecting component variable try resaving.)
[2017.08.12-06.27.00:571][ 0]LogOutputDevice:Error: Stack:
and
[2017.08.12-06.15.22:509][ 0]LogBlueprint:Warning: [BoxSpawn] 'DefaultSceneRoot' variable not found. Base class was probably changed.
[2017.08.12-06.15.22:522][ 0]LogBlueprint:Warning: [Compiler BoxSpawn] Warning Could not find a variable named "DefaultSceneRoot" in 'BoxSpawn_C'.
Make sure 'BoxSpawn_C' has been compiled for Get DefaultSceneRoot
I can’t see why these can’t be found. View from editor:
Renaming the components doesn’t have any effect, same with refreshing all nodes.
I’ve migrated one such problem blueprint in a new blank project and pushed to a repo here: https://github.com/AHelper/dbg_bp_errors
I’ve included logs for this project and the full one in the root of the repo. Why is this happening? Is there some way to fix this besides recreating these from scratch?
I’ll try opening these in 4.17 and update what happens. I’ll keep an eye out for reproduction steps.
Edit 1: After migrating to 4.17 and resaving the blueprint, I was able to run it just fine. Still a bit concerning, but that should keep me moving forward.