Spit16 takes tater in wing near root, shrugs it off

[moot]

The 30mm "dud" has to be isolated for the evidence to be solid..

[Scotch]

Happens to me all the time now. Obvious 30mm fireball, whether it be on a wing or tail etc. I'm sure I have half a dozen films of this. Just have to find them.

[SouthLanda]

Here is my evidence that something is not set correctly regarding 30mm. I dont know what it might be, it could be as simple as a damage value needing to be higher in the 30mm or lower in the target. My expectation is that hits in certain areas should do enough damage to destroy the structural integredy of the airframe. 30mm fired from a Me-262.













Here is the film, in a .zip file. Action is at 20 minutes.
http://www.mediafire.com/?tjzmzh3tzg5

[Anaxogoras]

Here is the film, in a .zip file. Action is at 20 minutes.
http://www.mediafire.com/?tjzmzh3tzg5

Edit your film to only include the action sequence.  I know I sound lazy, but doing us that favor is so easy it's actually you that is lazy.

[Rebel]

I highly doubt the issue is duds included in the modeling. 

I rather think it's a specific angle/speed/range combination that returns a variable damage number that doesn't induce damage. 

Call it a fluke and move on. 

If anyone is willing, I'll gladly go to the DA to research and send an email to HiTech saying "Hey Dale, check this out- if you're attacking a spitfire 16, doing 250mph, he's doing 200, and you hit him with a tater in the wing root at an AOT of 45, with his wings rolled 90 degrees, damage that should be happening is not."

That's really the ONLY way we're EVER gonna isolate this.  The data is being sent and received just fine.  It's the math in the middle yielding a weird result (my personal bet would be a neverending whole rather then a decimal figure) that throws the DM for a loop, and says "You scratched his paint, nothing more."