I’m having a weird problem getting mouse events to register when using blueprints.
To show the problem I have created the simplest possible set up – on MouseDown, MouseUp and MouseDoubleClick I have set it up to log to the screen ‘Mouse Up’, ‘Mouse Down’, ‘Double Click’ respectively:
Couldn’t be simpler. And yet, what happens is that when I start the PIE, the first click registers and logs the message ‘Mouse Down’, but does not log ‘Mouse Up’ when released, no matter how long I hold the button for. And after the first click, no other clicks seem to be registered, nor messages logged. The double click works fine, however, just not single clicks.
If I then press Shift+F1 to get the cursor back, and then click again, it registers another click and logs the ‘Mouse Down’ message.
The only way I can even get it to register a MouseUp is if I click and hold, the press Shift+F1, and then release the mouse button.
Note that this is the same whether I create general override functions or create specific bindings to something like a border object.
I’m trying to build some pretty basic functionality around being able to click on the screen, but it’s not possible since it doesn’t even seem to be registering clicks properly and creating the corresponding events.
The fact that your cursor is disappearing is strange. I’m working on a project that exclusively uses the mouse and we’ve had no problems with any of the mouse events. What context are you using the mouse cursor events in? Is the cursor only supposed to be on screen at certain times or all the time? Is this in conjunction with a UMG widget? What does the mouse interface section in your player controller look like? Here’s mine:
&stc=1
Mine is a completely mouse driven game though.
It isn’t too hard to turn these guys on and off though in blueprint, if you need to. If you are using a UMG widget you will need to make sure you are setting the input mode as well.
I’m still not quite sure what exactly you are trying to do. Why can’t you just detect the mouse down and up with the “pressed” and “released” outputs on the mouse event you use?
I have a similar problem. The Mouse up and down event register and the string prints as per the blueprint. However the cursors do not change
a) for mouse down after the second click
b) for mouse up unless the mouse is moved
In case anyone gets the same problem and searches for it, I had the same problem but it seemed to be because I changed the input mode to Game only instead of Game and UI. So after changing the input mode to Game and UI it magically worked again