At 200m, 1/2 degree missed by 1.75m, about 5' 9".
Not far enough? The calculations are in radians anyway. 1 radian is a bit over 57 degrees so in the math even a rookie would get a couple-three places and be missing.
I mention doing it this way because it calculates quicker than figuring actual degree to miss by, requires less changes to the existing code and once in a while even a rookie gets lucky.
But what do I know? I only paid my rent and bills by writing/developing code for many years in many languages. I've done a good bit of shooting too, including with automatic weapons though not from a moving plane. They are still so much easier to hit targets with than single-shots it's funny, especially at ranges I wouldn't even try single-shots.
That algorithm can adjust for conditions too, like when the plane the gunner is in is turning, though IMO under some conditions it should be impossible to shoot and one the plane is going down the gunner should be bailing out, not sniping. masking a few bits in an IEEE floating point number takes only a few cycles, especially when the mask is in a pre-set variable.
What can I say? I learned to code on old, slow, 8-bit micros without FPU's and still make the programs seem fast. I do know what I'm writing about.
|