Bug: Mouse Clicks not responding after set Input UI, then to Game
In 4.10 I didn't have any missed mouse clicks. In 4.11 I did, I would have to click 10 or 11 times to get it to register once.
In my main menu map, as the UMG is loaded I was setting the controller to InputMode UI only. When the map was launched I set the InputMode to Game Only.
The result was, keyboard would work, but mouse clicks not registering.
Removing both nodes fixed the problem, but I would have prefered there to be no game input when there was a full screen UMG widget.
This is a bug. I already have a fix, by not using the nodes. It might cause someone else a headache if they run into it so I'm reporting it.
asked Apr 22 '16 at 02:18 AM in Bug Reports
There are several known issues with set input UI. The one I think is applying in this case is UE-14476. Switching set input to either UI/Game/Game and UI consumes all controller input, which could cause errors such as the one you are seeing. I am going to update this bug report to reflect that additional developers are experiencing it.
answered Apr 26 '16 at 06:19 PM
Hi Harth Tuwist,
Thank you for submitting a bug report. I have reproduced this issue and logged a report for it here. You can track the report's status as the issue is reviewed by our development staff.
answered Oct 03 '16 at 08:19 PM
I found a solution. Disable the "Show Mouse Cursor" in the Controller and everthing works perfect. But if you have no other cursor and need someone you must create your own.
answered Feb 24 '17 at 08:28 PM
I just had the same issue in 4.12 and I seem to have fixed it by not hooking anything up to the target pin on the Set Input Mode Game Only node inside the player controller BP
answered Jun 15 '16 at 09:33 PM
I am also experiencing this bug in 4.13. I haven't checked 4.13.1 yet, but there is nothing in the patchnotes that seems to fix that problem. Google tells me that UE-14476, but it seems to me that this is not the bug OP was talking about. After switching to InputMode GameOnly, my game takes mouse down events only when I double click (resulting in the behavior described above if you are not aware of the situation and just randomly click in your window).
I have a main menu, where I set Input Mode UI only, and on PostLogin in the actual game I change the InputMode to GameOnly (I am copying MP behavior from the Shootout example). If i use tsaroths suggestion, the nodes do not seem to do anything at all.
I also tried a custom node with C++ Code [PlayerController]->SetInputMode(FInputModeGameOnly());, but that didn't work either.
Are there workarounds? Besides not using these nodes at all?
answered Oct 03 '16 at 01:13 PM
My Game is using 4.15 and this was a bug that I thought was an issue with my logic as my project relies heavily on mouse inputs and mouse click Combinations. I Ripped apart most of my logic to figure out where I messed up and after I stopped second guessing myself I decided to do a search and found this post. That will teach me lol. Once I realized it was a bug with UE4 thanks to this post I set to find a workaround. I think it was already mentioned here but I found out that just removing the Input mode nodes on my project the bug stopped and the lack of the nodes had no effect on my projects performance at all.
Attached A Screenshot for those who need a visual for this solution.
answered Feb 26 '17 at 05:07 AM
I'm also facing this issue in 4.18.1, after a few diging, I've found a quick solution. In PlayerController.h
This might be a dirty patch but for me it does the trick
answered Jan 29 '18 at 09:58 AM
I am facing the same problem in a top-down shooter I am making, with the "Set input mode game only" enabled, I have to click multiple times for the character to shoot once, and this is in 4.21.2.
answered Feb 03 '19 at 09:37 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here