Skip to main content
Madlios
Inspiring
January 26, 2026
Solved

Noesis MouseUp bug?

  • January 26, 2026
  • 5 replies
  • 170 views

It seems like Noesis MouseUp event will pass the same mouse position as the MouseDown event. And worse is that MouseMove is disabled during MouseDown. This makes it impossible to track if mouse down and up events occurred at different locations. Is there a setting or config to overcome this with Noesis? Also i dont wanna use focusedInteraction

Best answer by Madlios

Ok so after extensive testing i kinda figured out why. When interaction mode is set to "Interactive, non blocking", the Horizon controls somehow consumes all the input before it is routed to Noesis. Only when setting Noesis to "Interactive blocking" then everything works. But this makes u lose the ability to control player and camera. So right now it is not possible to easily detect mouse move while also having the Horizon Controls enabled. The only work around is to build your own Control system to be able to both controlling the player and detecting screen interactions

5 replies

gausroth
gausroth
Honored Contributor
January 26, 2026

How are you setting the events up? I was only able to get the MouseMove to fire while the mouse button was down.

EDIT: The mouse move event fires while button down is Horizon. There is no mouse/cursor detection in with Noesis in Horizon unless the button is down.

GitHub: https://github.com/Gausroth/HorizonWorldsTutorials.git Discord: https://discord.gg/hNyDQwdw4N YouTube: https://www.youtube.com/@GausRothTutorials
MadliosAuthor
Inspiring
January 26, 2026

If u run in web mode u can get mouse move from noesis. On mobile mode because it doesnt have a mouse so mouse down is triggered first. My setup is simply attaching events to the outermost Noesis page with transparent background. Weird that u got mouse move to work while mouse down. For me this only work when focused interaction is enabled as well, but i dont want that

gausroth
gausroth
Honored Contributor
January 26, 2026

The mouse has to be over the element that has the even trigger.

GitHub: https://github.com/Gausroth/HorizonWorldsTutorials.git Discord: https://discord.gg/hNyDQwdw4N YouTube: https://www.youtube.com/@GausRothTutorials
MadliosAuthorAnswer
Inspiring
January 27, 2026

Ok so after extensive testing i kinda figured out why. When interaction mode is set to "Interactive, non blocking", the Horizon controls somehow consumes all the input before it is routed to Noesis. Only when setting Noesis to "Interactive blocking" then everything works. But this makes u lose the ability to control player and camera. So right now it is not possible to easily detect mouse move while also having the Horizon Controls enabled. The only work around is to build your own Control system to be able to both controlling the player and detecting screen interactions

    Terms & ConditionsAccessibility statement