Oddly Slow Funcitons

Szling

I started working on aiming in an isometric game yesterday and I did manage to create functions that select a target point based on the cursor position in the active viewport, one using a raycast 3D and one using an intersect_ray() call to a PhysicsDirectSpaceState3D.

To test them I just used a node 3D named Visref2 with a box mesh as it's child and then set the global position of Visref2 to the position that my targeting functions return. When I place the cursor in a location and then call the function the mesh moves to the appropriate location perfectly. HOWEVER If I'm moving the mouse while I press the input to call the function or if I call the targeting functions from inside a _physics_process(): and set the position of Visref2 in _process(): or _physics_process() at the same time, then Visref2 will lag behind the mouse position. The faster I'm moving the mouse the farther it lags and It will catch up to the right spot if I stop moving the mouse.

So it seems to me that there is either a delay between cursor movement and target-point calculation or between the target-point calculation and assigning a position to Visref2 (or both). But I have no clue how to track it down.

Any ideas would be appreciated. I'm pretty new to this, only started using Redot and learning to code about 3 months ago.

Here is a link to some recordings of the issue, one of which is just part of another but slowed down to make it easier so see.

https://drive.google.com/drive/folders/1o97T6Xi_gPgEt4OuGN6WGMZlkGHyJT8Q?usp=sharing

Zeftax

I tried to replicate this in my inventory where the held item follows the cursor and found out it happens to me too! (even though I did not notice this before :D)
I then found this issue on the godot github, where someone recommended turning V-Sync off, so I tried it and now the lag is no longer present.
I recommend reading through the github thread for more options, it seems that the only way to get rid of the lag completely, reliably, and without turning off v-sync or capping framerates is to change the hardware cursor sprite to the object, which is probably not applicable in your 3D use case though.

Szling

Zeftax
Thank you, this helped Immensely. So much so that I thought the problem was completely fixed, when I viewed the new recording frame-by-frame I did see that there is still a slight delay. It is enough less now that I can't see any difference by eye even when whipping the mouse all the way across the screen faster than I can imagine doing in actual gameplay so I'm going to consider it good enough.