3D widget mouse event area incorrect

Development Programming & Scripting UI
, , ,
1

Hi,

I’ve encountered a 3d widget interaction problem in UE 4.9.

As in following picture, widget accepts mouse events in incorrect positions.

57110-3dui1.png
57110-3dui1.png1218×663 497 KB

I created this new blank project for testing. (I encountered this problem in my current project also.)

When the first time I created this new project and the widget in the scene, it works properly.

Widget can detects mouse events normal.

But after I closed the testing project and opened it again, it’s all gone wrong, UI mouse detection became weird and I don’t know why.

Here’s the link of my testing project: Dropbox - UITest.zip - Simplify your life

Open the project and it should loads test scene directly, press play and move mouse around and you should see the problem.

I’m not sure if it’s a bug or something I didn’t set correctly.

Can you help me with this issue? Thank you.

2

P.S. Change widget pivot to 0,0 in component setting won’t work, it would cause UI rendering occlusion issue.

3

Hello CrispyVitamin,

I was able to reproduce this issue on our end. I have written up a report ( UE-20777) 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

4

It seems the hit boxes compared the the actual widgets being shown are rotated 90 degrees. So if I have three buttons stacked on top of eachother I have to move from the lower right to the lower left to highlight them.

5

Still doesnt work in 4.10 and now the pivot workaround is gone too. I would give anything to have started my VR project in Unity.

6

I had the same issue on 4.10 in standalone game. I made new blueprint with widget and it worked fine. I had pivot in 0.5 0.5 and rescaled it and it worked too.

7

having the same problem in 4.9 right now.
Changing the coordinate space from “world” to “screen” on the actor’s widget component works nice. So i think it might be a problem with the screenToWorld/worldToScreen projection of either the input or the event area of the widgets.