TextRender component not working out of PIE mode

Development Programming & Scripting Blueprint
, , , ,
1

116028-bp.png
116028-bp.png1236×632 101 KB

In a project I’m working on, a TextRender component in the blueprint of my main character class is used a name label, shown above the characters head.

The BP is only adds some visual stuff to the C++ base class which is used for the more sophisticated stuff.

Everything works flawless in the PIE mode. However, running via Game.uproject" CMainMap -server -log yields these errors:

[2016.11.23-00.40.40:264][  0]LogBlueprint:Warning: [CCharacter_BP_2] 'NameLabel' variable not found. Base class was probably changed.
[2016.11.23-00.40.40:268][  0]LogBlueprint:Warning: [Compiler CCharacter_BP_2] Warning Could not find a variable named "NameLabel" in 'CCharacter_BP_2_C'.
Make sure 'CCharacter_BP_2_C' has been compiled for  K2Node_VariableGet_0
[2016.11.23-00.40.40:270][  0]LogBlueprint:Error: [Compiler CCharacter_BP_2] Error The property associated with  NameLabel  could not be found
[2016.11.23-00.40.40:274][  0]LogBlueprint:Warning: [Compiler CCharacter_BP_2] Warning [0011.41] Compile of CCharacter_BP_2 failed. 1 Fatal Issue(s) 1 Warning(s) [in 7 ms] (/Game/Character/CCharacter_BP_2.CCharacter_BP_2)
[2016.11.23-00.40.40:276][  0]LogBlueprint:Warning: [Compiler CCharacter_BP_2] Warning [0011.41] Compile of CCharacter_BP_2 failed. 1 Fatal Issue(s) 2 Warning(s) [in 0 ms] (/Game/Character/CCharacter_BP_2.CCharacter_BP_2)
[2016.11.23-00.40.40:277][  0]LogBlueprint:Warning: [Compiler CCharacter_BP_2] Warning [0011.41] Compile of CCharacter_BP_2 failed. 1 Fatal Issue(s) 3 Warning(s) [in 0 ms] (/Game/Character/CCharacter_BP_2.CCharacter_BP_2)

I’d appreciate some help on this.
According to Unreal Engine Issues and Bug Tracker (UE-31667) this might be a known bug, supposedly fixed in 4.14.

Please note that I’m using a source compiled version of the engine.

And the core of the base class of the character BP is pretty much copied from the 3rd Person Project Template.

2

Hello sennec,

This does seem related to that bug report as the reproduction is similar, although I’m not able to reproduce this issue using the steps provided on the bug report. Could you try recreating this in a fresh project? If so, a reproduction case would be useful.

3

I failed to reproduce this issue in a fresh project.

Might be related to the fact that, instead of creating a new 4.14 project, I migrated my old project to 4.14.

4

It may be worth a try to try migrating the content using the in-editor migration tools to a new 4.14 project, rather than converting the project itself. This usually helps with any conversion issues.

5

We haven’t heard from you in a while, sennec. Are you still experiencing this issue? Were you able to try migrating your content to a new project? What were the results? In the meantime, I’ll be marking this issue as resolved for tracking purposes.