GUI in 3D demo, why manipulate event data?

thimblefire · April 26, 2024, 7:56pm

Godot Version

4.2.2

Question

I’m currently going over the GUI in 3D demo as all the discussions I’ve read on the matter point to that, but I have some questions on why it’s seemingly necessary to manipulate the mouse event position, calculate the relative event distance, and track the duration since the last event.

I don’t understand why this isn’t just a simple raycast.

github.com

godotengine/godot-demo-projects/blob/3.5-9e68af3/viewport/gui_in_3d/gui_3d.gd

extends Spatial


# The size of the quad mesh itself.
var quad_mesh_size
# Used for checking if the mouse is inside the Area
var is_mouse_inside = false
# Used for checking if the mouse was pressed inside the Area
var is_mouse_held = false
# The last non-empty mouse position. Used when dragging outside of the box.
var last_mouse_pos3D = null
# The last processed input touch/mouse event. To calculate relative movement.
var last_mouse_pos2D = null

onready var node_viewport = $Viewport
onready var node_quad = $Quad
onready var node_area = $Quad/Area


func _ready():

This file has been truncated. show original

mrcdk · April 27, 2024, 2:57am

Don’t use the 3.x version of the code. Use the 4.x version here godot-demo-projects/viewport/gui_in_3d/gui_3d.gd at master · godotengine/godot-demo-projects · GitHub

It’s not manipulating the mouse input event because you need to convert the 3D coordinate system mouse event to the 2D coordinate system so the 2D part can react to it. In the 4.x version the raycast is done by the engine by enabling CollisionObject3D.input_ray_pickable and implementing the CollisionObject3D._input_event() function.

thimblefire · April 27, 2024, 3:52am

Oh yes, my mistake. I am using the 4.x version in my project, I mistakenly shared the wrong link to show the code.

Am I right in assuming event.velocity is the distance from the camera to the UI element being clicked? I ask because the issue I seem to be having is that I’m only able to click UI elements that are within the distance of the camera cone and I suspect the raycast isn’t being projected far enough.

I have Fixed Size enabled, I don’t know if that’s perhaps throwing it off.

mrcdk · April 27, 2024, 5:38am

No, InputEventMouseMotion.velocity is The mouse velocity in pixels per second. It has nothing to do with distance.

Fixed Size only affects the node visually and it does not modify the physics body. Raycasts only work with the physics system.