click event not working properly - mouse offset ?

[zoomvp.at]

Hi,

I’m starting fresh as a newbie with a new game and trying to get a few basic things up and running.

1. I enabled click events in the level BP.
2. I created a BP actor with a static mesh and an on-click event, using a print string to see the result.

In play mode, clicking on the actor sometimes (or only in a specific area) triggers the event. In some cases, even clicking outside of the actual mesh works.

Unfortunately, this issue is also happening with the mouse-over events. I would appreciate your help.

Thanks!

[Everynone]

@zoomvp.at

I enabled click events in the level BP.

Just to clarify, in LB, on Begin Play, you enabled click / hover events of the Player Controller, right?

---

@zoomvp.at

In play mode, clicking on the actor sometimes (or only in a specific area) triggers the event. In some cases, even clicking outside of the actual mesh works.

The only thing that comes to mind is collision. Either of that cube or of something else that sits between the camera and the cube and intercepts the clicks. In the editor viewport, outside of PIE (Play in Editor), press Alt+C to visualise collision - how does it look?

[zoomvp.at]

Hi.

Thank you so much. The trick with the collision helped.
I had an other invisible object close to the clickable object. Shame on me.

It is still not working on the whole static mesh but way better then before.

Thank you!

[Everynone]

@zoomvp.at

It is still not working on the whole static mesh but way better then before.

Try this and see what it Prints when you click the mesh and it does not work.

[zoomvp.at]

Thank you for your quick and very helpful response.
Even for me, it was simple to rebuild this easy BP.

It seems that the cursor location is based on its actual position on the screen when starting the game. I tried to center the cursor as shown in this video:

How to spawn the Mouse to Center of the viewport - Unreal Engine 5

But now the cursor is at the top left of the screen, which is the same issue as mentioned in the comment under the video. So I disabled the code again.

I tried to start the game with the cursor in the middle of the crosshair. Here, I noticed that the cursor seems to move faster or slower than the viewport change/camera view, or it might be offsetting? I’m not sure about that.

The crosshair is pointing at the wooden sheets (BP to open the menu), but the click actually refers to the furniture to the left/below it.

Thank you so far.

[Everynone]

I do not understand what cursor positioning has to do with any of it. Are you trying to select / highlight elements that are in the centre of the screen? If so, using a cursor is not the way to do it. It will introduce lag and many other inconsistencies.

---

It’s a matter of a simple manual trace instead. Could you clarify? Especially the bit about the cursor / screen centre:

• is the user expected to move the cursor separately from the camera?
• or is the “cursor” merely a visual indicator of where the screen centre is and we pick items following camera’s forward vector? (like in many 1st person perspective games)

[zoomvp.at]

Yes, I try to select/highlight elements that are in the center of the screen.
The user is not supposed to move the cursor separately from the camera.

My actual goal is to build a VR game in which you can open a menu and press buttons without any input other than looking at a specific point for a certain amount of time. (“On Hovered event” with a timer?)
For demo purposes, and due to not having a working VR setup right now, I’ve set it up as a first-person-game.

I started with a click instead of hovering over for ease of use.
I already tried this great tutorial that relies on “Line Trace by Channel.”

Change Crosshair Colour For Enemy, Teammate and Neutral - Unreal Engine 4 Tutorial

It didn’t work at first, so I tried a different approach (click events and so on).
I think I need to dive deeper into this. I will follow this video again and see if it gets me to the desired solution.

Thank you so far.

[Everynone]

Do consider the standard trace + interface combo for this:

Moving an object by pointing another object at it

See if this helps with this particular bit. a standard forward camera trace: [image] You’d use an interface or inheritance if there are more types to handle, ofc. not sure how you want stuff to move, here it’s via a timeline: [image] which results in: the branches in the script prevent it from spamming since we’re tracing on Tick: Hopefully you can adapt it to your needs. It’s a setup similar to this one:

Another one:

Third person crosshair object highlight troubles

The communication in the example revolves around Inheritance + Interface - a potent combo, imho. the base class implements the interface (which children inherit) the widget uses the same interface - calls children receive can be propagated: Actor → Widget Component → Widget without casting or finding user widgets (this can be done in many ways, though) [image] the player has a collision sphere and sends an interface call to overlapped actors as we approach: [image] [image] Above, handl…

This one has an example project attached.

---

There’s, of course, tons of tut on this:

How To Select (Highlight) Other Actors/Objects By Looking At Them In Unreal Engine 5

Since this is one of the more common interactions.

---

The gist is that you trace using a camera forward vector. The crosshair is just a visual reference. You should not use a mouse cursor, especially considering the VR implementation where there is a very different pointing device.

[zoomvp.at]

Thank you.

In my game, the line tracing is also a little off…

I’m going to start fresh with a first-person template.
In this template, the line tracing works as intended.

I started with an empty game, so just importing the first-person content isn’t working properly.

Thank you very much for helping me out. Game development is completely new to me.