Description

As soon as the widget was visible on the node/display at least once all nodes/displays receive the button press and correctly increase the counter. Therefore it seems like the widgets are only initialized after they became visible on the node/display. In the attached video the button press is also programmed to change the color of the underlying plane to further illustrate the problem, that button presses or widgets interactions are only registered once the widget was visible on one of the nodes. The plane spans the whole wall such that the color should stay uniform over all nodes. Therefore it seems like the nodes get out of sync as the action(change of color) is not executed on all nodes but only on those where the widget was visible yet.

Additional Notes: In the attached video each quadrant of the wall is powered by a different node with nDisplay.

(Video is too large to attach here, it is linked in bug submission ( [Link Removed] ), if you do not have Salesforce Access let me know)

 
 

Steps to Reproduce

1) Use a setup with multiple displays using nDisplay such that one cluster node is responsible for one display
2) Create a simple UMG widget with a button and a label which acts as a counter for each button press for example
3) Place widget such that it is only visible on one display and use the widget (e.g. press the button to inc counter)
4) After using the widget on one display move it to another display
5) Use the widget on the second display
 
Results:
 
The counter is out of sync. Any button press that occurs before the widget was moved (is visible) on a different display/node will only affect the counter for the screens where the widget was visible yet. Example for 2 displays/nodes:
1) Show widget on screen 1 and press button 2 times. The counter should show 2.
2) Move the widget onto another node/display the counter shows 0 now.
3) Press button on second screen increases the counter for screen 1 from 2 to 3 but for screen 2 from 0 to 1.
 
Expected: 
 
When moving the same widget from display/node 1 to display/node 2 the counter should have the correct value.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-83468 in the post.

3
Login to Vote

Won't Fix
CreatedNov 9, 2019
ResolvedAug 27, 2021
UpdatedAug 27, 2021