Yep, I am using the 2DSideScroller template, and I have to minus 205.812 x, and 144.212 z to even get the correct hit location of where it is REALLY hitting, might be just a bug with the template.
Here’s what I found: The numbers/angles of shooting you are getting make sense, but are still a bit confusing. I am comparing the red number to the yellow number in this calculator: https://www.easycalculation.com/algebra/3dvector-angle.php
I’m not completely sure what the relation mathematically is, or the pattern; I suggest you try swapping a variety of the rotation variables, for example: use pitch in place of yaw and yaw in place of pitch(break rot from the get rotation node). See what combination gets your projectiles more accurate(if any). If this doesn’t work, I suggest you do what I do, place an item at 0,0,0. And trace to it, make sure that your printed location string matches 0,0,0. If you click on 0,0,0 and get some trace like -50, 18.2, 9. Then subtract those numbers from your location return node on break hit result so that they = 0. This is what I had to do. If you have any luck, let me know. Hope I helped!