OnBeginCursorOver and OnEndCursorOver not working properly

[Mr.isometric]

Its Triggering with an Offset from a Cursor I don’t know why?

[Everynone]

• ShowFlag.Collision 1 → what do you see?
• the collider might be much larger than the mesh → open the asset and show collision there, too.
• are we sure it’s not printed by another component hiding elsewhere in the graph?

[Mr.isometric]

after running command.

Its a Box Mesh added in Unreal.

whole Blueprint Nothing else is Triggering it.

[Mr.isometric]

@Everynone

ShowFlag.Collision 1

Weird Thing I Noticed just right now When i Do Shift+F1 for showing Cursor It Works but With Locked Cursor it Dont Work!

So whats happening to Mouse Pointer Position when Game is Played in Editor?
is Cursor Not Centered when in First Person Template?

[Everynone]

@Mr.isometric

So whats happening to Mouse Pointer Position when Game is Played in Editor?
is Cursor Not Centered when in First Person Template?

But… there seems to some kind of confusion here. Are you trying to use a hidden / inactive cursor to detect OnBeginCursorOver while not actively using a pointing device to control it?! Because that kind of interaction is done with camera traces + interface. Using cursor for this will be unreliable and inconsistent at best.

You could probably set cursor location to screen centre but… that’s just not the right tool to do it. The traditional method would be close to this:

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…

The above has a redundant extras bit for detecting interactives in proximity. The gist - we trace along a camera vector, send interface messages to the hit components, the components can respond if they so wish.

Here’s another example:

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:

Note this has nothing to do with the mouse cursor.

[Mr.isometric]

Thank You I think I Got it , I will Look More into Interfaces Topic