well it's not really performance heavy but if you run it 140 times per second, it will eat some cpu usage^^
Ah, but do you ever do that?
I think I'm gonna work with stopwatches, which means it will only check for the vector stuff once every 250ms or something
Kinda feel like that should not be required :/c
and as soon as it gets closer it will check for it constantly
ofc I need to compare vectors
This is where my knowledge is SEVEARLY limited.
A 3D game takes place in a three dimensional world
which means you're working with vectors because each object has a x,y,z value
and the same goes for positions. I need to compare a set place in the matrix with Asterix' current position
i havent heard the term "vector" in a long time 👴
*flashbacks of rac3 dev commentary*
Had a fear of the word "vector" when I was younger
because our teachers were too dumb to actually explain how to work with them
like we never actually learned what they were
The school system is kinda scuffed in Switzerland (like in Germany...)
I think I already knew vectors even before I learned them in school, when looking up game dev tutorials 😄