how to trace error w/o stack trace info | Godot Café | Page 1

bold hearth Nov 23, 2024, 6:01 PM

#

this is the error
E 0:01:06:0319 looking_at: The target vector can't be zero.
<C++ Error> Condition "p_target.is_zero_approx()" is true. Returning: Basis()
<C++ Source> core/math/basis.cpp:1044 @ looking_at()

I have one reference in all my code to Basis.LookingAt it, but commenting it out did not resolve the error. (I also tried lots of other things, commenting it out was more of a desperation step. )

All movement is done using PathFollow3D, so rotating really is something my code only cares about in some places. enemies never

I don't know where to start, and this is the last error in my logs. (Godot 4.3, C#)

tawny siren Nov 24, 2024, 1:45 AM

#

bold hearth this is the error E 0:01:06:0319 looking_at: The target vector can't be zero....

The path follow node may use the looking at method internally to orient itself
I don't know how to solve this tho

bold hearth Nov 24, 2024, 3:08 PM

#

some more notes; the times that these happen are pretty much on the second.

0:00:28:0000-0:00:28:0122 and then 0:00:29:0054-0:00:29:0139

Out of 177 errors, they all have the same number 0 after the seconds.

The number of repeats is not consistent.

bold hearth Nov 24, 2024, 3:38 PM

#

and behavior is repeatable on other systems, although the number of errors is not.

#

going to give up 🙂

harsh narwhal Dec 10, 2024, 9:26 PM

#

Did you ever solve this? My
debugger is also spammed by this, and I have multiple PathFollow3D's in my game for traffic movement.

#how to trace error w/o stack trace info