Thanks!

idk if I got it right . imagine we have 1 box object in world space , that box has own coordinate (x,y) but in unity we has transform.right for x axis of object itself and transform.up for y axis of itself. both are basis vector and normalized. somehow those has built-in calculate for rotation already (so we dont talk about rotation here) that's mean any number that you want (like your own coordinate value x,y aka. your imagine vector2 )split x and y and pair to basis vector from box space then multiply for each basis vector x and y axis then sum up to get local point in box space instead of world space. if you still catch up with me. now we can move the box to any position along with custom vector2 but relate to box space // p.s. my English skill is kinda suckass ´ //p.s.2 i could miss the point and out of line

Yes, I also thought that was too easy. I did it on raylib with pure vectors and the hardest part was finding out the right direction of my points direction. I'm guessing this explains how many people said 3a was harder, they must've not used transforms?

@@xhivo97 Excuse me, how/where did you learned how to get the direction vectors from the rotation?

three cats! thor, salad and toast

@@acegikmo great ! I have 2 : Henri Bourrachat and Djinny. Happy new year from Québec !

She is using Rider IDE which is a paid IDE not Notepad++

@@supertenchoo4271 thanks

Aaaaz,

i think that was probably to reflecting the direction after reach the normal surface

Not a c# user but idk how I feel about the scope being outside the if block.

@@xhivo97 I think technically the if block is only between the { } and the condition is not part of it :P

@@lievenpetersen Yes, but here's where the confusion comes for me: since most languages allow you to define new variable in for loops' (/*here*/), that variable has local scope inside that for loop only. There are other languages that have syntactic sugar to do something like this pseudo code here: if (int flag = getFlag(); flag == true) { // flag has local scope in the if } Odin does that, but I wrote it in C like syntax in the above example. But the out keyword is syntactically quite different and I'm sure there's advantages and disadvantages to having it scope outside.

To add to this, I feel like if it has local scope it's a unique feature, as it is not the same as defining it before the if statement and might lower the chances for mistakes in some cases; while the out keyword seems to me it's equivalent to declaring it on top of the if statement without the added advantage scope minimization.