PrintString/Text called from UMG event in PIE reporting Client -2

[tmek]

Issue: Normally calling a PrintString node from a client window when in PIE will display “Client N: [string]” Where N is the client window number. However i’ve found that if you call PrintString from within a widget event it will always say “Client -2: [string]” (client negative two) no matter what client window it’s run on.

To replicate

• make a widget with a button
• add event on button click that calls node PrintString “hello from widget event”
• add CreateWidget and AddToViewPort nodes to display widget from level blueprint’s OnBeginPlay, also call PrintString “hello from blueprint” from the level blueprint
• run multiple client windows in PIE
• click button from any client window.

You should see this in the console after clicking the button…

[anonymous_user_e729f54e]

Hello tmek,

I was able to reproduce this issue on our end. I have written up a report (UE-32781) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.

Make it a great day

[JonathanArmstrong]

@EpicGames Please look back into this bug. It has previously been closed as “won’t fix”. I’m not getting it for a UMG, but it is intermittently breaking the OVRLipSync plugin. The visemes output only register properly when the client output is consistently Client -2 (not a split Client 0/Client -2).