[Bug] Mouse input don't work in 3d Widget components?

Development Programming & Scripting
1

Hi, I trying to create a 3D UI with Widget Components, but the mouse input don’t work. I find two question same with mine.

  1. https://answers.unrealengine.com/questions/169013/editabletextbox-not-working-in-umg-3d-widget.html
  2. https://answers.unrealengine.com/questions/199544/how-to-make-mouse-input-work-with-3d-widgets-compo.html
2

Hello ,

This is a known issue (UE-20777) it has been sent to the developers for further consideration. Thank you for your time and information.

Make it a great day

3

I have fixed bug, can I commit it?

4

Hello ,

You will need to submit a pull request on github for consideration. I have provided a link below. I hope this helps.

Link: https://github.com/EpicGames/UnrealEngine/compare

Make it a great day

5

I had submit a pull request.
Link: https://github.com/EpicGames/UnrealEngine/pull/1542

6

Hello ,

Thank you for your submission you will be able to find updates on your pull request on github

Make it a great day

7

Months later still broke…

8

So how comes that this feature was available in unreal engine 3 and in unreal engine 4 its still experimental and broke…

9

Hello C0dR,

I went ahead and double checked on this issue for you. I ran through the reproduction steps for this issue in 4.11 and could not reproduce the issue. I would like to make sure that you are experiencing the same issue.

Quick questions:

  1. Can you reproduce this issue in a clean project?
  2. If so, can you reproduce this issue in a 4.11 project?
  3. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  4. Could you provide screen shots of any blueprints and/or widget setup that may be involved with this issue?
10

Hello,

thank you for your reply. It seems like the problem doesn’t occure anymore in 4.11. Is it possible to get a solution for 4.9, since we are still using visual studio 2013 and I would like to avoid compiling the engine for every coworker. Otherwise it seems like we have to wait for a stable 4.11 release and switch to a newer visual studio :slight_smile:

11

I do not have a specific change list for the solution to this issue. This means that I will not be able to provide a specific commit that can be cherry picked from github.