I’m encountering a strange problem and couldn’t yet find a solution, albeit googling for hours.
Please have a look and try your best
The plan here is as follows:
When opening the world map (not included here) you can place “markers” and remove them.
The InputAction is correctly set up, the marker actor that is placed is, too.
Now the problem with this is that I can click ONCE on the map, which gives me the “LMB registered” print AND places a marker… but when I click again, on a different spot, I cannot trigger the same thing with only one LMB, I have to double-click in order to get the “LMB…” print and the marker to spawn.
Same goes for the RMB for removing, btw.
The strange thing is that all this worked just fine until some hours ago.
I can’t remember what exactly it was that I’ve changed, but I’m pretty sure it wasn’t on the level BP, but rather some different BP classes.
What could be the problem here?
Thanks, in advance,
Abaris
EDIT:
The InputActions DO consume input, DO execute when paused and DO override parent bindings.
All of these values have been changed in a trial and error manner, already.
The map is not a widget but replacing the player’s camera with a “map camera”; the linetraces from this BP hit the ground - this worked everytime before.
I’m having a similar problem. I have a simple LeftMouseButton event wired to a Print node in my player controller. I launch in editor and my first click prints “Hello” as it should but after the first click I have to double-click to get the same result.
If I wire the Print node to a keyboard input it works fine, this seems to be just happening with mouse clicks whether its a bound input event or just a simple LeftMouseButton event.
I’m using 4.11.2. I’m wondering if this is a bug or if I changed a setting somewhere without realizing.
One more thing. This is also happening when using an actors OnClicked Event. I have Show Mouse Cursor and Enable Click Events turned on in my player controller. This suggests it has nothing to do with how I’m handling mouse input.
WOW geez thanks for following up on this because I was goin nuts trying to fix this. Previously when exiting a UI, I used the node “set to game mode only” but switching this node to game mode and UI fixed this immediately.
Hi, I have the same problem, but I dont understand what you mean with “forced “Set Input Mode to Game and UI” on all necessary points in all BPs that involve a click”. Can you explain this?
Is this a bug or what is the problem? In a new Blank-Project is nothing of this Problem but if i copy my existing project in the new Blank there is the same problem.
Hi all, I was also experiencing this issue but had no idea what “Setting Input Mode to Game and UI on all necessary points” meant, but was able to google a solution in Project Settings → Default Viewport Mouse Capture Mode → select “Capture Permanently Including Initial Mouse Down” instead of “Capture Permanently”.