by **Stratadrake** » 16 Aug 2012, 05:01

No, I don't think so. If I take the figures you gave in previous posts for hitbox and scatter radius determination, then let's break down the results:

1 - Python took 88% of hits from a 50% base accuracy weapon. So 38% of all shots fired (a.k.a. 76% of misses) were false hits.

2 - If Python has a hit radius of 54 and the weapon has a scatter radius of 100, then (because actual scatter is determined by a radius/angle offset from target position) we can expect 54% of misses to land inside the hitbox radius (regardless of angle) and score a false hit.

3 - Misses targetted "behind" the hitbox will impact the target en route and also score a false hit.

4 - If only 54% of misses should have hit, but 76% actually did, this is a +22% difference and it represents the number of misses that were aimed behind the hitbox.

So in total, of 400 shots fired at the Python:

- 200 (50%) were expected to hit the target (and did)

- 108 (27%) were expected to miss the target, but landed inside the hitbox and scored a hit

- 44 (11%) were expected to miss the target, but landed behind the hitbox and scored a hit en-route

- 48 (12%) actually did miss the target.

PS: Here's some trig for you to crunch on. Given a range-to-target (x), hitbox radius (r) and maximum scatter radius (s), then:

- Target radius expressed as an angle in the attacker's FOV: = arcsin(r/x) (total target diameter relative to attacker's FOV is twice this)

- Angular radius that represents an area always "behind" the target, regardless of scatter distance: = (90 - arccos(r/s) - arcsin(r/x) )

- Any scatter angle that exceeds (90 + arcsin(r/x)) is either aside or in front of the target, regardless of scatter distance

- Any scatter angle between the above two values may or may not land behind the target, depending on scatter distance

I can illustrate it in a diagram if you need it.