Author Topic: Murderer's Row Frame 2 Score  (Read 333 times)

Offline Baumer

  • Silver Member
  • ****
  • Posts: 1739
      • 332nd Flying Mongrels
Murderer's Row Frame 2 Score
« on: July 26, 2009, 05:16:31 PM »
Here are the results from frame 2



There were several issues in this frame that needed to be addressed with penalty's

The axis were penalized for not hitting the following targets by the T+60 Rule; C25, C27, C36 (complete loss of points). In addition, the axis were also penalized 10% of their A2A points for not meeting the minimum D3A-1 requirement (2 out of 12).

The allied side was also penalized 10% of their A2A points for not meeting the minimum TBM-3 requirement (30 out of 36).


CiC's remember, sending in 1 or 2 pilots to "get some bullets on target" is not in the spirit of FSO (or the rules) and is not acceptable.

With the way I do scoring each frame raw score is reduced to a percentage of 33.33% so that all three frames are of equal value, even if the raw point potential is different from frame to frame.

So the final result of frame 2 reduces to-
  • USN- 16.27
  • IJN- 17.06

Frame 1 Scores
  • USN- 25.77
  • IJN- 7.56

Cumulative score after 2 frames
  • USN- 42.04
  • IJN- 24.62
HTC Please show the blue planes some love!
F4F-4, FM2, SBD-5, TBM-3

Offline Saxman

  • Plutonium Member
  • *******
  • Posts: 9155
Re: Murderer's Row Frame 2 Score
« Reply #1 on: July 26, 2009, 05:32:24 PM »
What time did the Axis strikes actually hit those three TG's? My squad was defending this frame, but I've been on missions where the strike was in the attack area, but the boat just plain couldn't be FOUND until after T+60 (this happened to us in North Sea).
Ron White says you can't fix stupid. I beg to differ. Stupid will usually sort itself out, it's just a matter of making sure you're not close enough to become collateral damage.

Offline ImADot

  • Platinum Member
  • ******
  • Posts: 6215
Re: Murderer's Row Frame 2 Score
« Reply #2 on: July 26, 2009, 06:43:05 PM »
The 325th decimated the attack force half a sector from CV25 before T+60 -- they never even got close...until T+117 in their 2nd life planes, while we were trying to land.
My Current Rig:
GigaByte GA-X99-UD4 Mobo w/ 16Gb RAM
Intel i7 5820k, Win7 64-bit
NVidia GTX 970 4Gb ACX 2.0
Track IR, CH Fighterstick, CH Pro Throttle, CH Pro Pedals

Offline Dustoff2

  • Zinc Member
  • *
  • Posts: 98
Re: Murderer's Row Frame 2 Score
« Reply #3 on: July 26, 2009, 07:25:46 PM »
The 325th decimated the attack force half a sector from CV25 before T+60 -- they never even got close...until T+117 in their 2nd life planes, while we were trying to land.

correct, so why the penalty? we made an attempt.
« Last Edit: July 26, 2009, 07:29:42 PM by Dustoff2 »
AKDust
Arabian Knights

Offline Baumer

  • Silver Member
  • ****
  • Posts: 1739
      • 332nd Flying Mongrels
Re: Murderer's Row Frame 2 Score
« Reply #4 on: July 26, 2009, 08:26:19 PM »
All of the factors such as proximity and timing were considered by me, and reviewed with the rest of the CM team. The primary reason that the penalty was enforced was due to the fact the orders, as written by the Axis CiC, were not in keeping with the T+60 rule.

After several flight tests, with zero time to actually search for and attack the CV groups, it is impossible to fly the attack routes as ordered to targets number 2,3, and 5 within 60 minutes.



HTC Please show the blue planes some love!
F4F-4, FM2, SBD-5, TBM-3