Aces High Bulletin Board
Special Events Forums => Scenario General => Topic started by: oneway on December 20, 2009, 10:38:07 PM
-
Allied La-7 Group Leaders,
The Kill/Death ratio of the La-7 in RSKS is an astounding figure when you consider its not predicated on pilot ability or aircraft capability, but simply the Machine driven...and this Machine Category success points directly at the leadership of the La-7 groups....congratulations commanders in effectively leading your groups....
'Well done is an understatement....
Your performance sets the bar for this event...
:salute
Oneway
Red Storm / Krupp Steel Machine Stats:
| Fighter | Sorties | Kills | Deaths | K/D | Destroyed | Field | Factory |
| La-5FN | 145 | 79 | 25 | 3.16 | 108 | 37 | 71 |
| La-7 | 250 | 241 | 51 | 4.73 | 98 | 89 | 9 |
| P-39Q | 148 | 33 | 19 | 1.74 | 164 | 56 | 108 |
| Yak-9U | 249 | 153 | 62 | 2.47 | 16 | 16 | 0 |
| Bf 109G-14 | 90 | 80 | 41 | 1.95 | 1 | 1 | 0 |
| Bf 109G-6 | 121 | 38 | 61 | 0.62 | 2 | 0 | 2 |
| Bf 109K-4 | 119 | 82 | 52 | 1.58 | 3 | 3 | 0 |
| Bf 110G-2 | 28 | 6 | 14 | 0.43 | 161 | 0 | 161 |
| Fw 190A-8 | 40 | 10 | 7 | 1.43 | 1 | 1 | 0 |
| Fw 190D-9 | 162 | 143 | 59 | 2.42 | 1 | 1 | 0 |
| Fw 190F-8 | 183 | 99 | 78 | 1.27 | 477 | 145 | 332 |
|
| Bomber |
| A-20G | 78 | 18 | 20 | 0.90 | 264 | 15 | 249 |
| B-25C | 152 | 29 | 25 | 1.16 | 1078 | 157 | 921 |
| Il-2 Type 3 | 141 | 31 | 67 | 0.46 | 166 | 163 | 3 |
| Ju 88A-4 | 91 | 9 | 60 | 0.15 | 505 | 137 | 368 |
|
| Tank |
| Sherman VC Firefly | 163 | 70 | 82 | 0.85 | 62 | 59 | 3 |
| T-34/76 | 3 | 0 | 0 | ---- | 0 | 0 | 0 |
| T-34/85 | 166 | 100 | 65 | 1.54 | 236 | 188 | 48 |
| Panzer IV H | 93 | 30 | 60 | 0.50 | 27 | 11 | 16 |
| Tiger I | 104 | 121 | 70 | 1.73 | 67 | 23 | 44 |
|
| AAA |
| Ostwind | 28 | 0 | 1 | 0.00 | 41 | 11 | 30 |
| Wirbelwind | 76 | 14 | 14 | 1.00 | 150 | 5 | 145 |
|
| Troop |
| M3 | 124 | 2 | 27 | 0.07 | 30 | 14 | 16 |
| SdKfz 251 | 106 | 1 | 37 | 0.03 | 21 | 21 | 0 |
|
| FieldGun |
| Gun Ship or Field | 157 | 14 | 0 | ---- | 12 | 12 | 0 |
|
| Gunner |
| Gunner-Observer | 93 | 8 | 2 | 4.00 | 0 | 0 | 0 |
BBS Code Generated by AcesHigh.Scenario.LogReader Class
A Scenario Planning, Management & Analysis program written by Oneway in C# .NET 3.5
Number of Auto-Generated Chars = 8953
-
Very well done.
As a B-25C pilot, I'm also shocked at the positive ratio THEY had!
Is that enemy-only, or including FF?
EDIT: I see in your other post it's got no rules applied to it yet. I suspect that may drop a little when they are.
Still, it surprises me!
-
.
-
.
-
Lol, poor Osties.
-
Go LA5 :rock
-
Go LA5 :rock
best multi-role wooot :rock
-
What is your criteria for a death?
Edit:
I am really curious now that I think about it...
Applying MA style scoring I cant count that many deaths in just one sortie of my squadron.
Strip
-
Considering that at least half the B-25s got wiped out en mass every frame, that's a lot of kills to get to counter-act the losses... *I* definitely didn't get that many kills!
Is it counting drones?
-
I highly doubt it, if it was I could account for all of those kills in one frame for one squadron.
Even not counting drones I still doubt it but will reserve total judgement until I review film.
Strip
-
After reviewing film I can account for 25 kills in less than three sorties not counting formations.
Unless its only counting pure "deaths" (were you've received a "You have been killed" message) there is something amiss.
Strip
-
Considering that at least half the B-25s got wiped out en mass every frame, that's a lot of kills to get to counter-act the losses... *I* definitely didn't get that many kills!
Is it counting drones?
Yes and no...drones shot down are counted as kills just like the logs and log summary from AH, however loss of drones is not counted as a death, just like the AH logs...
Unlike the logs however, I do match the actual drones of the bomber pilot to the kill of the Victor for purposes of tracking drones when a formation hot pads and turns in either 1 or 2 drones back to the hanger.
The logs always print the Kill for the Victor but they never print the loss of a drone to a Victim sortie...hence it is necessary to cross reference Victor.Kills and the Sortie they were achieved with the sortie of the bomber pilot with drones.
Kills are: "Shot down a XXXX flown by XXXX... or "Awarded kill as XXXX crashes". In the later case I denote the Kill.Type as KillType.Awarded, vs KillType.Earned which is the default condition as most Kills are Earned Kills.
Deaths are of type Outcome.ShotDown, Outcome.ShotDownProxy and OutCome.ShotDownCaptured...ex actly like the AH logs. Only 1 death is ever attributed to a pilot flying formations...
Every sortie has an Outcome; here is the declaration of the enumerated type that is stored in Sortie.Outcome.Type (eg: Sortie.Outcome.Type = Outcome.ShotDown)
public enum OutCome {
Landed,
ShotDown,
ShotDownCaptured,
ShotDownProxy,
Crashed,
Ditched,
Bailed,
Captured,
Vanished,
Undefined
}
Here is the code that actually assigns the values first for the Kills, followed by the Deaths, I left out the code for all of the other events that can occur and are either conclusive or interim:
// mid sortie events
case AhEventType.Kill:
//Shot down a Il-2 Type 3 flown by airbull.
data = frameEvent.Data.Substring(frameEvent.Data.IndexOf("down a") + 7);
data = data.Replace(" flown by ", ",");
data = data.Substring(0, data.Length - 1);
victimRideName = data.Substring(0, data.IndexOf(","));
victimName = data.Substring(data.IndexOf(",") + 1);
Ride victimRide = EP.Hanger.CheckOutRide(victimRideName, new Pilot(victimName));
sortie.Kills.Create(frameEvent.TimeStamp, sortie, victimRide.Pilot, victimRide);
sortie.HasEvents = true;
break;
case AhEventType.ProxyKill:
//Awarded kill as cactus crashes.
victimName = frameEvent.Data.Substring(frameEvent.Data.IndexOf("as ") + 3);
victimName = victimName.Substring(0, victimName.IndexOf(" "));
sortie.Kills.Create(frameEvent.TimeStamp, sortie, new Pilot(victimName), KillType.Awarded);
sortie.HasEvents = true;
break;
// Sortie.Outcome events
case AhEventType.ShotDown:
//Was shot down by xxxx.
sortie.Outcome = new SortieOutcome(frameEvent.TimeStamp, OutCome.ShotDown);
victorName = frameEvent.Data.Substring(frameEvent.Data.IndexOf("by ") + 3);
victorName = victorName.Substring(0, victorName.Length - 1);
if (victorName.Contains("unknown")) victorName = "UNKNOWN";
sortie.Victor = new Pilot(victorName);
sortie.HasEvents = true;
break;
case AhEventType.ShotDownCaptured:
//Was shot down by xxxx and captured.
sortie.Outcome = new SortieOutcome(frameEvent.TimeStamp, OutCome.ShotDownCaptured);
victorName = frameEvent.Data.Substring(frameEvent.Data.IndexOf("by ") + 3);
victorName = victorName.Replace(" and captured.", "");
if (victorName.Contains("unknown")) victorName = "UNKNOWN";
sortie.Victor = new Pilot(victorName);
sortie.HasEvents = true;
break;
case AhEventType.ShotDownProxy:
//Was shot down by xxxx (crashed).
sortie.Outcome = new SortieOutcome(frameEvent.TimeStamp, OutCome.ShotDownProxy);
victorName = frameEvent.Data.Substring(frameEvent.Data.IndexOf("by ") + 3);
victorName = victorName.Replace(" (crashed).", "");
if (victorName.Contains("unknown")) victorName = "UNKNOWN";
sortie.Victor = new Pilot(victorName);
sortie.HasEvents = true;
break;
Sample Sortie Log from AH:
WMLute
14:25:14 Departed from Field #42 in a La-7
14:49:03 Shot down a Fw 190F-8 flown by A8Moray.
14:55:26 Shot down a Ju 88A-4 flown by 4440.
14:55:56 Shot down a Ju 88A-4 flown by 4440.
14:57:06 Helps Banzzai shoot down KKEN.
14:57:43 Shot down a Ju 88A-4 flown by Flossy.
14:59:02 Shot down a Ju 88A-4 flown by pope14.
15:05:47 Was shot down by unknown enemy.
15:12:34 Departed from Field #42 in a La-7
15:38:18 Shot down a Ju 88A-4 flown by KKEN.
15:39:03 Shot down a Ju 88A-4 flown by pope14.
15:39:36 Shot down a Ju 88A-4 flown by pope14.
15:39:59 Helps SirNuk3 shoot down HB555.
15:40:20 Shot down a Ju 88A-4 flown by KKEN.
15:48:41 Arrived Safely at Field #42
15:49:01 Departed from Field #42 in a Gun Ship or Field
15:51:09 Arrived Safely at Field #42
15:51:17 Departed from Field #42 in a La-7
15:57:03 Arrived Safely at Field #42
15:58:06 Departed from Field #42 in a La-7
16:11:40 Helps Snefens shoot down Turner.
16:17:05 Shot down a Fw 190A-8 flown by CANUKK.
16:22:40 Shot down a Fw 190D-9 flown by horble.
16:33:17 Shot down a Bf 109K-4 flown by Twizzty.
16:34:16 Shot down a Bf 109K-4 flown by WngViper.
16:34:32 Shot down a Bf 109K-4 flown by Dibs775.
16:34:52 Shot down a Bf 109K-4 flown by HotRod1.
16:40:39 Skillfully ditched.
-
After reviewing film I can account for 25 kills in less than three sorties not counting formations.
Unless its only counting pure "deaths" (were you've received a "You have been killed" message) there is something amiss.
Strip
Nothing is ammis Strip...other than perhaps your use of "Film" to try calculate a K/D ratio for a certain machine type across 4 frames of action...comprised of 250+/- sorties
Deaths are calculated by AH only as 1 of the 3 ShotDown Outcome Types...My program will also calculate vehicle losses like Brooke's scoring method...and it will do so with excruciating accuracy...this is not that...this is just AH "Style" Deaths...
You need a computer program to do that...
:aok
I got one that does just that...
Oneway
-
Very well done.
As a B-25C pilot, I'm also shocked at the positive ratio THEY had!
Is that enemy-only, or including FF?
EDIT: I see in your other post it's got no rules applied to it yet. I suspect that may drop a little when they are.
Still, it surprises me!
FF has not been scrubbed from this, but its a simple matter to do so...However, across all 4 frames FF deaths amounted to only a handful
Here is a comprehensive listing of Friendly Fire across all 4 frames, both teams....I threw the Invalidate Friendly Fire switch :aok
=====================INVALIDATED KILLS ========================
Victor.Ride: B-25C Victor: Pilot cactus Victim.Ride: P-39Q Victim: Pilot Crum 17:13:43 Invalid Kill: Friendly Fire frame4
Victor.Ride: Sherman VC Firefly Victor: Pilot SHAGGER Victim.Ride: T-34/85 Victim: Pilot KUsh 17:14:27 Invalid Kill: Friendly Fire frame3
Victor.Ride: P-39Q Victor: Pilot 0ldgit Victim.Ride: La-5FN Victim: Pilot TexMurph 16:09:21 Invalid Kill: Friendly Fire frame3
Victor.Ride: La-5FN Victor: Pilot 100Chewi Victim.Ride: La-5FN Victim: Pilot 1olo 14:51:55 Invalid Kill: Friendly Fire frame3
Victor.Ride: T-34/85 Victor: Pilot Sethbag Victim.Ride: Sherman VC Firefly Victim: Pilot USRanger 17:24:24 Invalid Kill: Friendly Fire frame4
Victor.Ride: Il-2 Type 3 Victor: Pilot MAG1C Victim.Ride: Il-2 Type 3 Victim: Pilot Drone 16:34:01 Invalid Kill: Friendly Fire frame2
Victor.Ride: La-7 Victor: Pilot JoeJoe Victim.Ride: La-7 Victim: Pilot Dantoo 16:35:13 Invalid Kill: Friendly Fire frame1
Victor.Ride: La-7 Victor: Pilot WMLute Victim.Ride: Sherman VC Firefly Victim: Pilot jollyFE 15:57:56 Invalid Kill: Friendly Fire frame1
Victor.Ride: Ju 88A-4 Victor: Pilot pope14 Victim.Ride: Bf 109K-4 Victim: Pilot alibaba 15:35:01 Invalid Kill: Friendly Fire frame4
Victor.Ride: Fw 190D-9 Victor: Pilot Spinner Victim.Ride: Fw 190A-8 Victim: Pilot Morfiend 15:34:09 Invalid Kill: Friendly Fire frame3
Victor.Ride: Bf 109G-14 Victor: Pilot lowZX14 Victim.Ride: Bf 109G-14 Victim: Pilot Dace 14:56:49 Invalid Kill: Friendly Fire frame1
Victor.Ride: Bf 109G-14 Victor: Pilot Voudou Victim.Ride: Bf 109G-14 Victim: Pilot Bosco 16:11:23 Invalid Kill: Friendly Fire frame3
Victor.Ride: Bf 110G-2 Victor: Pilot jedi25 Victim.Ride: Bf 110G-2 Victim: Pilot Paradox 14:51:07 Invalid Kill: Friendly Fire frame3
Victor.Ride: Bf 110G-2 Victor: Pilot U29 Victim.Ride: Bf 110G-2 Victim: Pilot jedi25 14:57:34 Invalid Kill: Friendly Fire frame1
Victor.Ride: B-25C Victor: Pilot Beefcake Victim.Ride: T-34/85 Victim: Pilot Cobra45 14:45:34 Invalid Kill: Friendly Fire frame3
Victor.Ride: Gunner-Observer Victor: Pilot Beefcake Victim.Ride: B-25C Victim: Pilot A8hunter 16:10:11 Invalid Kill: Friendly Fire frame3
Victor.Ride: La-5FN Victor: Pilot Saantana Victim.Ride: La-5FN Victim: Pilot prono 16:23:56 Invalid Kill: Friendly Fire frame2
Victor.Ride: P-39Q Victor: Pilot STEALTH Victim.Ride: Il-2 Type 3 Victim: Pilot kvuo75 16:31:59 Invalid Kill: Friendly Fire frame4
invalidated kills: 18
-
Like I said if your applying K/D using normal MA standards (anything other than landed successfully) something is not right. I didn't try to establish a K/D using film, I just invalidated your results. Over four frames my squad lost more than 25 pilots alone, never mind counting the drones. Now account for the fact there were two squads and the other was hit harder than me. Unless your using an unknown k/d formula, which I would be curious to know, something is wrong.
The B-25 k/d is in error using normal k/d critera, sorry to burst your bubble...
Strip
-
MA is if you don't make it back, you're dead. Ditched, Bailed, Killed, Discoed, etc, all count as a loss. And MA counts drones.
The problem with the public logs is that they only list "landed successfully" -- not "landed successfully with 2 out of 3 drones" or something much more detailed.
-
Like I said if your applying K/D using normal MA standards (anything other than landed successfully) something is not right. I didn't try to establish a K/D using film, I just invalidated your results. Over four frames my squad lost more than 25 pilots alone, never mind counting the drones. Now account for the fact there were two squads and the other was hit harder than me. Unless your using an unknown k/d formula, which I would be curious to know, something is wrong.
The B-25 k/d is in error using normal k/d critera, sorry to burst your bubble...
Strip
Better buy a new Abacus...your math is wrong...
You would argue with God at heavens gate given a chance...your amazing in your constant attacks...
Here are all B-25C kills for ALL B-25's ALL Frames...get back to me with some real data when you run the log files...if you want all four log files let me know....
:D
Oneway
B-25C Pilot/Victor: Pilot cactus Victim: Pilot Stampf Fw 190D-9 14:56:58
B-25C Pilot/Victor: Pilot cactus Victim: Pilot Crum P-39Q 17:13:43
B-25C Pilot/Victor: Pilot GypsyB Victim: Pilot Hobo Fw 190D-9 14:54:06
B-25C Pilot/Victor: Pilot Krusty Victim: Pilot AArecon Fw 190F-8 14:47:16
B-25C Pilot/Victor: Pilot Krusty Victim: Pilot VonMessa Fw 190D-9 14:53:39
B-25C Pilot/Victor: Pilot Popsman Victim: Pilot REDX Fw 190D-9 16:51:15
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot Fencer Fw 190F-8 15:19:05
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot Marshal Ju 88A-4 15:17:30
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot Marshal Ju 88A-4 15:17:43
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot Spinner Fw 190D-9 16:01:15
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot JVnotch Fw 190D-9 16:07:53
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot Wraith Fw 190D-9 16:08:48
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot bb Fw 190D-9 16:50:08
B-25C Pilot/Victor: Pilot Soulyss Victim: Pilot JVlobo Fw 190D-9 16:58:17
B-25C Pilot/Victor: Pilot gas50 Victim: Pilot lothmog Fw 190F-8 14:38:57
B-25C Pilot/Victor: Pilot gas50 Victim: Pilot rob53 Bf 109G-14 15:46:32
B-25C Pilot/Victor: Pilot gas50 Victim: Pilot Turner Fw 190D-9 14:55:06
B-25C Pilot/Victor: Pilot Hibbie2 Victim: Pilot Magpie Bf 109G-14 15:21:38
B-25C Pilot/Victor: Pilot Strip Victim: Pilot VANDALS Bf 109G-14 15:22:58
B-25C Pilot/Victor: Pilot Strip Victim: Pilot DrDea Fw 190F-8 14:38:16
B-25C Pilot/Victor: Pilot Strip Victim: Pilot Spinner Fw 190D-9 14:58:03
B-25C Pilot/Victor: Pilot Strip Victim: Pilot Akondo Fw 190D-9 14:58:24
B-25C Pilot/Victor: Pilot Beefcake Victim: Pilot Cobra45 T-34/85 14:45:34
B-25C Pilot/Victor: Pilot Beefcake Victim: Pilot Marshal Ju 88A-4 15:17:42
B-25C Pilot/Victor: Pilot Beefcake Victim: Pilot JVnotch Fw 190D-9 16:53:57
B-25C Pilot/Victor: Pilot Beefcake Victim: Pilot Wraith Fw 190D-9 14:57:11
B-25C Pilot/Victor: Pilot Duke Victim: Pilot Fencer Fw 190F-8 14:40:19
B-25C Pilot/Victor: Pilot Duke Victim: Pilot shamus Bf 109G-14 15:49:07
B-25C Pilot/Victor: Pilot OzzyRev Victim: Pilot Morfiend Fw 190D-9 14:55:56
-
MA is if you don't make it back, you're dead. Ditched, Bailed, Killed, Discoed, etc, all count as a loss. And MA counts drones.
The problem with the public logs is that they only list "landed successfully" -- not "landed successfully with 2 out of 3 drones" or something much more detailed.
Well I have that handled...the AH logs and their summaries DO NOT COUNT
-
oneway, something is amiss on this one...
You listed 29 kills for 25 deaths across all 4 frames, in your other thread?
We lost more than 25 planes every frame, seems like!
EDIT: We had 7 pilots max in 2 squads, with 3 drones each, and more than once were wiped out entirely on one of our missions.
14 pilots, times 3 planes lost, equals 42 planes lost per frame, if fully wiped out once (not counting losses on our second lives).
Something's not adding up, loss-wise.
-
So that is every B-25 killed for the entire scenario?
Something else, Popsman, DocCH, QCareCH, HarpJ, GlennCo, and Tudza are not on this list. Tudza died four times himself to enemy fighters in two frames alone.
Yet he is not listed once.....I think you need to take a closer look at your program verses attacking people with valid points.
Strip
-
So that is every B-25 killed for the entire scenario?
Something else, Popsman, DocCH, QCareCH, HarpJ, GlennCo, and Tudza are not on this list. Tudza died four times himself to enemy fighters in two frames alone.
Yet he is not listed once.....I think you need to take a closer look at your program verses attacking people with valid points.
Strip
Yes that is because this is showing the sortie with the kill and that kill was lost at that time and the pilot had multiple kills
Let me put the victim in so it makes more sense to you
Oneway
I updated it so it makes more sense...
-
I don't want to seem like I'm picking on oneway's program, but if there is a flaw, it should be addressed.
I went over frame 1's losses alone. Any time it says "so and so died" or "bailed from damaged plane" that's only an indication of that action from the last drone, so you have to assume that's the 3rd loss in a row. Must be counted as 3, since we all took off with 3 planes per formation. I counted each bomber's death or killed notification as 3, for the above reason, and then counted how many times they were shot down by the other team, to account for losses where they still landed safely. Not a complete picture, but it counts as a bare minimum of losses.
Frame 1 alone, we had (just counting losses from the logs, does NOT show the entire picture if you lose drones, or have them damaged and later lose them after the attacker is gone, etc)
13GvBAP losses:
Cactus: -3, Gypsy -6, Krusty -3, Popsman -6, Soulyss -4, unclkurt -6
(at LEAST 28 lost there alone)
251 GvBAP losses:
Doc72ch -3, gas50 -5, hibbie2 -3, Strip -3, tudza -3
(at LEAST 17 lost there alone)
So frame 1 alone we lost 45 lost B-25s bare minimum.
I think there are issues with how it counts bomber formation losses, so far.
-
Dont worry its only me who is attacking him.....
:rolleyes:
I want to know how he arrived at only 25 kills, by any logical yard stick used measure that number is erroneous.
Edit: Part of the problem is I am talking about deaths, you are talking about kills. Can you describe how you compile deaths of bombers when it relates to k/d?
(That way people can compare results?)
Strip
-
This is how:
Frame 2:
Krusty
14:24:17 Departed from Field #12 in a B-25C
15:05:40 Destroyed a AAA factory #03
15:05:40 Destroyed a AAA factory #03
15:05:40 Destroyed a AAA factory #03
15:05:43 Destroyed a AAA factory #03
15:05:43 Destroyed a field gun at city #03
15:05:43 Destroyed a AAA factory #03
15:05:44 Destroyed a AAA factory #03
15:05:44 Destroyed a AAA factory #03
15:05:44 Destroyed a AAA factory #03
15:05:44 Destroyed a AAA factory #03
15:50:08 Arrived Safely at Field #12
15:50:24 Departed from Field #12 in a B-25C
16:28:27 Helps corsair shoot down Redtail7.
16:34:55 Destroyed a city building at city #03
16:34:56 Destroyed a city building at city #03
16:34:56 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:34:57 Destroyed a city building at city #03
16:55:34 Vanished without a trace.
If you check the "so and so killed Krusty" you will find I was killed 3 times. 2 by 190Ds, and the third time I was dogfighting them and my power blinked ("vanished without a trace") so I gave away the third kill to whoever wounded me moments before.
You'll note, however, that I was never "killed, died, bailed" or anything in my log screen.
I think the program's not currently set up to read between the lines, and count me as "died 3x"....
-
We are in agreement Krusty....
My question is directed a Oneway, applying MA standards I can account for that many deaths in one sortie.
Strip
-
I don't want to seem like I'm picking on oneway's program, but if there is a flaw, it should be addressed.
I went over frame 1's losses alone. Any time it says "so and so died" or "bailed from damaged plane" that's only an indication of that action from the last drone, so you have to assume that's the 3rd loss in a row. Must be counted as 3, since we all took off with 3 planes per formation. I counted each bomber's death or killed notification as 3, for the above reason, and then counted how many times they were shot down by the other team, to account for losses where they still landed safely. Not a complete picture, but it counts as a bare minimum of losses.
Frame 1 alone, we had (just counting losses from the logs, does NOT show the entire picture if you lose drones, or have them damaged and later lose them after the attacker is gone, etc)
13GvBAP losses:
Cactus: -3, Gypsy -6, Krusty -3, Popsman -6, Soulyss -4, unclkurt -6
(at LEAST 28 lost there alone)
251 GvBAP losses:
Doc72ch -3, gas50 -5, hibbie2 -3, Strip -3, tudza -3
(at LEAST 17 lost there alone)
So frame 1 alone we lost 45 lost B-25s bare minimum.
I think there are issues with how it counts bomber formation losses, so far.
No its not wrong at all....it does it exactley like the log does it...if you look at the deaths for your group...it exactley matches the deaths I am showing...
I am more than happy to put in the Drone losses and in fact I am prepared to do that...
Its a matter of choice...do you want the K/D to exactly reflect as AH calculates Deaths and Kills? or do you want to throw in the loss of your drones...
Here is your Drone report for all four frames...have at it....your Kill/Death ratio will fall through the floor....
B-25C Report
=========================
Sorties Count = 152
B-25C Checked Out = 456
B-25C Shot Down = 157
B-25C Lost = 34
B-25C Vanished = 2
B-25C Checked In = 263
=========================
DRONES
Drones Checked Out = 304
Drones Shot Down = 117
Drones Lost = 17
Drones Vanished = 1
Drones Checked In = 169
-
On the first sortie of frame 4 we had 12 sets of buffs to get wiped out, that's 36 B25's.
I'm not bashing Oneways system but it does seem that the scoring for bombers and their drones is messed up, and I think it's more of a logging system problem rather than Oneways code.
-
We are in agreement Krusty....
My question is directed a Oneway, applying MA standards I can account for that many deaths in one sortie.
Strip
Knock yourself out...my calculations are completely correct...if you want to add ditched, bailed, and drones to the Death total go for it...
The fact of the matter is that the LOG shows a death is different than a bail out...or a ditch
I guess what you guys want is the KILL/(Shotdown+Ditch+Bailed+Crashed + Drones Lost Ratio)...
That is not a Kill Death Ratio...
Bailing is not a death, ditching is not a death....
B-25C Report
=========================
Sorties Count = 152
B-25C Checked Out = 456
B-25C Shot Down = 157
B-25C Lost = 34
B-25C Vanished = 2
B-25C Checked In = 263
=========================
DRONES
Drones Checked Out = 304
Drones Shot Down = 117
Drones Lost = 17
Drones Vanished = 1
Drones Checked In = 169
-
On the first sortie of frame 4 we had 12 sets of buffs to get wiped out, that's 36 B25's.
I'm not bashing Oneways system but it does seem that the scoring for bombers and their drones is messed up, and I think it's more of a logging system problem rather than Oneways code.
Its not the logs either...I can add in Drones if you would like...AH doesn't...I can account what happened to every single drone ...
-
Dont worry its only me who is attacking him.....
:rolleyes:
I want to know how he arrived at only 25 kills, by any logical yard stick used measure that number is erroneous.
Edit: Part of the problem is I am talking about deaths, you are talking about kills. Can you describe how you compile deaths of bombers when it relates to k/d?
(That way people can compare results?)
Strip
It does not count the drones as a death...its that simple...nor should it...if your so inclined to think that way the B-25C K/D is 0.130, which is a completely pointless stat...
-
(Killed + Captured + Crashed) = B-25C Losses?
Correct? That number being 25....
Strip
-
Oneway, you check your AH stats in the MAs and it'll deduct every lost drone... It counts every formation you up as 3 sorties, and if you don't land 3, your K/D drops significantly.
Hence, when you say "just like the MA" -- makes me think it should do this.
It's not accurate to show it otherwise, since it's got way too many losses "slipping through the cracks" so to speak. Makes the B-25Cs look like they had a positive kill/death ratio! :D
So, to avoid confusion I think it should always take this into effect. Always.
-
(Killed + Captured + Crashed) = B-25C Losses?
Correct? That number being 25....
Strip
No...Losses are everything BUT Shotdown's and Vanished...Losses = Bailed, Ditched, Captured, Crashed...
The only thing impossible to account for in the logs (though not entirely) is planes a pilot loses in maneuvers...
The only thing you can figure out is if a pilot sortie outcome is shotdown, and yet only 1 drone was killed...it can be deduced he lost a plane in manuevers...HOWEVER...it is impossible given the log data to tell if a pilot lost aircraft to manuevers if his sortie outcome was anything BUT a shotdown type...
Thus...I have tabs on all drones...even if the pilot hotpads and turns some back in....
There isn't any stat or calculation I cannot produce...and my Data is rock solid...I have manually checked it hundreds of times against the logs...
Before you guys start questioning the output...first ask me the calculation method used. In this case it EXACTLY MATCHES the format and considerations as expressed in the Public Logs
Oneway
-
So that is the formula that you used to come up with 25 deaths in the k/d formula?
-
Oneway, you check your AH stats in the MAs and it'll deduct every lost drone... It counts every formation you up as 3 sorties, and if you don't land 3, your K/D drops significantly.
Hence, when you say "just like the MA" -- makes me think it should do this.
It's not accurate to show it otherwise, since it's got way too many losses "slipping through the cracks" so to speak. Makes the B-25Cs look like they had a positive kill/death ratio! :D
So, to avoid confusion I think it should always take this into effect. Always.
It is impossible for Kill Death Ratio to become negative...though Infinity and NaN are possible outcomes...B-25's will nearly always have a positive Kill Death Ratio
Like I said....Losing an aircraft is not a Death...not in my book, whether it is or is not in MA. The ratio simply compares how many times you killed vs how many times you died...
-
So that is the formula that you used to come up with 25 deaths in the k/d formula?
Death = ShotDown, ShotDownProxy, ShotDownCaptured....that is how AH totals it in the logs...and it seemed nobody had a problem with it until you did...
I posted the code....if its still unclear...I don't know how to explain it further
For Scenarios the ratio that would be the most appropriate is Kills/LivesLost...which would ignore the drones, and apply the rules as written...
Would that work for you guys...its a snap to change it...
Oneway
-
Well ain't I special....
Using the log summaries, killed, crashed, captured we totaled 21 "deaths" in frame 4 alone.
By the same definition we suffered 18 "deaths" in frame 3.....far above 25 for the scenario.
Strip
-
Well ain't I special....
Using the log summaries, killed, crashed, captured we totaled 21 "deaths" in frame 4 alone.
By the same definition we suffered 18 "deaths" in frame 3.....far above 25 for the scenario.
Strip
Like I said strip...those are not deaths...
And I gave you the drone report...
There are no holes in the data....
Your B-25C K/Per Machine Not Turned Back In is .13
-
So please enlighten me oh great and mighty Oneway, in non-code talk if you don't mind, how you arrived at 25 deaths.
(If its not too much trouble can you show actual numbers being applied to your process?)
You certainly haven't used any definition of "death" I have seen before. This is what the problem is, by normal MA and Scenario rules the K/D is different.
Strip
-
So please enlighten me oh great and mighty Oneway, in non-code talk if you don't mind, how you arrived at 25 deaths.
(If its not too much trouble can you show actual numbers being applied to your process?)
You certainly haven't used any definition of "death" I have seen before. This is what the problem is, by normal MA and Scenario rules the K/D is different.
Strip
Scenario Deaths are ShotDown, ShotDownProxy and ShotDownCaptured...
You can check it yourself...smart ass
Oneway
-
Not to nitpick, but an "even" kill/death would be 1. A "positive" kill/death is above 1. A "negative" kill/death is below 1 (a decimal). This is commonly accepted, and arguing the semantics isn't the point of the post.
If you two could tone back the hostility a bit, I think we do have a bit of confusion that needs clearing up. Perhaps I can help both sides.
Strip, I think he's only counting when somebody gets credit for your last drone. I.e. me in frame1:
15:20:14 Was shot down by lothmog.
I think the methodology is very flawed, since the kills/deaths for the fighters shooting down the bombers suddenly out-pace actual losses by leaps and bounds. "Magic" kills start showing up. Logically speaking that makes no sense. I'm thinking the methodology is flawed, and should be redone to include these.
Oneway, that's also one thing that's been an issue with the logs pages on ahevents.org for ... well since forever: doesn't list bomber deaths properly. It's a choice they made to simplify the logs. Not equatable to "MA scoring" or anything -- just the way they formatted these. When scenarios or FSOs are run that add points for lost bombers, killed bombers, etc, they do go in and count specifically how many were lost and add the details up as needed. It's just that for the general public they don't re-write the code. This may be where we disagree with you. That's not a "standard" -- it's just the way they format the logs for public viewing. It's not indicative of how the actual scenarios are scored for losses based on plane types or anything.
Hope this helps clear things up a bit.
-
.
-
Why bother anymore....
-
Frame 1: 13 GvBAP lists 4 pilots "killed" on our side of the logs, 251 GvBAP lists 3 (counting "by unknown players" -- not sure if 1way doing that also)
Basically only when it lists "15:21:02 Was shot down by HotRod1 (crashed)." [from tudza, frame1] does it add 1 to the death list.
That's how he added those up. So frame 1 would only net 7 by that criteria (as mentioned I disagree, I'm just trying to explain it more as it stands)
Edit: Checking the logs and updating as I do: By that criteria, no "deaths" in frame 2 at all. checking frame 3 and 4
Frame 3 would be 12 total for both units
Frame 4 would be 4 total for both. So given that I probably missed a couple here and there, like my disco counted as a death to somebody, that's around the 25 deaths listed. Again, not saying I agree, just clearing up the issue.
-
I did, your numbers are wrong....
Frame 4 Shotdown + ShotDownProxy + ShotDownCaptured = 21
Frame 3 Shotdown + ShotDownProxy + ShotDownCaptured = 18
Thats way above 25 for the scenario and that is not counting drones, I still don't see anyway to get that number.
Strip
STOP IT STRIP!
THE LOGS SAY NOTHING OF THE SORT!!!!!!!!
I already told you that Drones are not being counted...
If you want to count drones write your own program...
My program CAN ACCOUNT for DRONES....BUT THE K/D IS NOT COUNTING DRONES....
Get it through your thick head....
Across all 4 Frames....B-25C pilots had their Sortie Ended in a ShootDown ONLY 25 times
B-25 sorties whose outcome WasShotDown 25
frame1 GypsyB Outcome: ShotDown at 15:18:42
frame1 GypsyB Outcome: ShotDown at 16:18:45
frame1 Krusty Outcome: ShotDown at 15:20:14
frame1 Soulyss Outcome: ShotDownProxy at 15:19:37
frame1 gas50 Outcome: ShotDown at 15:20:51
frame1 tudza Outcome: ShotDownProxy at 15:21:02
frame1 tudza Outcome: ShotDown at 16:16:08
frame1 Teufel Outcome: ShotDown at 16:36:13
frame3 cactus Outcome: ShotDownProxy at 16:14:49
frame3 cactus Outcome: ShotDown at 16:55:47
frame3 GypsyB Outcome: ShotDown at 16:11:22
frame3 GypsyB Outcome: ShotDown at 16:53:20
frame3 Krusty Outcome: ShotDownProxy at 16:15:48
frame3 Soulyss Outcome: ShotDownProxy at 16:11:56
frame3 Soulyss Outcome: ShotDownProxy at 16:58:19
frame3 gas50 Outcome: ShotDown at 14:39:09
frame3 Strip Outcome: ShotDown at 14:39:35
frame3 Beefcake Outcome: ShotDownProxy at 16:01:53
frame3 Beefcake Outcome: ShotDownProxy at 16:54:10
frame3 A8hunter Outcome: ShotDown at 16:56:17
frame3 Duke Outcome: ShotDown at 14:40:25
frame4 GypsyB Outcome: ShotDown at 14:54:44
frame4 Popsman Outcome: ShotDownProxy at 14:54:37
frame4 gas50 Outcome: ShotDownProxy at 16:38:50
frame4 Strip Outcome: ShotDownProxy at 14:59:01
-
Frame 1: 13 GvBAP lists 4 pilots "killed" on our side of the logs, 251 GvBAP lists 3 (counting "by unknown players" -- not sure if 1way doing that also)
Basically only when it lists "15:21:02 Was shot down by HotRod1 (crashed)." [from tudza, frame1] does it add 1 to the death list.
That's how he added those up. So frame 1 would only net 7 by that criteria (as mentioned I disagree, I'm just trying to explain it more as it stands)
Edit: Checking the logs and updating as I do: By that criteria, no "deaths" in frame 2 at all. checking frame 3 and 4
Frame 3 would be 12 total for both units
Frame 4 would be 4 total for both. So given that I probably missed a couple here and there, like my disco counted as a death to somebody, that's around the 25 deaths listed. Again, not saying I agree, just clearing up the issue.
Yes of course I am counting unknown players....and in fact I actually match up the unknown player with an actual player by checking the other players kills...its how I get in the final analysis how many guys were killed by AutoGuns...for every unknown player that cannot be matched to an actual player with an actual kill is by default an autogun
And yes...you are correct that 7 pilots were shot down in Frame 1
And yes you are correct NO deaths in frame 2
Here is the code that reconciles unknown players by the way:
private void AssignKnownVictors()
{
// PURPOSE: MATCH UP VICTIMS WITH THEIR VICTORS
// get a list of sorties with unknown victors
List<Sortie> list = _Sorties.SearchVictor("UNKNOWN");
foreach (Sortie sortie in list)
{
Kills kills = _Sorties.Kills.ByFrame(sortie.Frame).ByVictim(sortie.Pilot);
foreach (Kill kill in kills)
{
if (Sortie.ContainsTimeStamp(sortie, kill.TimeStamp))
{
sortie.Victor = kill.Sortie.Pilot;
}
}
}
}
-
Well if he wants to total reinvent the wheel so be it......I dont agree with his methods either but oh well. This system is totally different than any method used in the MA or scenarios for the most part hence the confusion. Oneway, do as you please with regards to scoring, I will enjoy the scenario regardless of its scoring means.
By that definition I would agree to 25, however your definition of death is in serious misalignment with common practice.
Strip
-
Forgive me...
How do account for our entire first sortie of frame 4?
Both of our entire squadrons were shotdown by enemy aircraft resulting in 13 (if memory serves me) scenario "lives" being lost.
You only have three deaths listed, a big discrepancy of data verses logic applied to real life.....hence why we disagree on what constitutes a "death".
Edit: Changed four to three owing the fact that one was over an hour later and was unrelated.
Strip
-
Well if he wants to total reinvent the wheel so be it......I dont agree with his methods either but oh well. This system is totally different than any method used in the MA or scenarios for the most part hence the confusion. Oneway, do as you please with regards to scoring, I will enjoy the scenario regardless of its scoring means.
By that definition I would agree to 25, however your definition of death is in serious misalignment with common practice.
Strip
Wrong...
I am displaying the data consistent with the public LOGS for a Reason...BY CHOICE
If someone wants to actually bother to look at the logs they will find the output is EXACTLY consistent with the public data...
In the end I don't care what people want to call a death or a life or a ride or a machine...
They will be able to set the program up any way they see fit...it has already been programmed...
There are little boxes you check:
Ditch Counts as Life (true/false)
Bail Counts as Life (true/false)
Crash Counts as Life (true/false)
Drone (Counts as Life) (true/false)
Its not a flaw that the K/D is displayed as such...it simply mirrors what AH lists as Kills and Deaths on its LOG output...
-
Forgive me...
How do account for our entire first sortie of frame 4?
Both of our entire squadrons were shotdown by enemy aircraft resulting in 13 (if memory serves me) scenario "lives" being lost.
You only have four deaths listed, a big discrepancy of data verses logic applied to real life.....hence why we disagree on what constitutes a "death".
Strip
Give it a rest...son
I am showing you the sortie OUTCOME...not your interpretation of a Death....AND IT IS EXACTLY AS THE LOG SHOWS
Unlike your wild accusations and inuendo above which I find quite insulting to be honest
-
Please, go attack someone else....your little comments mean nothing and affect me even less. You would rather attack me personally than anything else, at least I ignore the source and state my mind unbiased of the origin.
Whether you reply or not, makes no difference, my statement stands. In frame four 13 or 14 formations of B-25s were shot down in the first 30 minutes of frame four. For whatever reason you have only chose to count three as deaths, hardly logical in my mind. Nothing can be said or done that would sway me other wise.
You have proven one thing though......
Edit: Never mind, I have spent enough time on this, choose to do as you wish as is your right. Don't be surprised at the repercussions, I am done with this thread though. Save yourself the reply....I wont be reading it.
Strip
-
I am showing you the sortie OUTCOME...not your interpretation of a Death....AND IT IS EXACTLY AS THE LOG SHOWS
... here's the thing....
Those logs themselves are an inaccurate interpretation of what a death is many times. The logs on ahevents.org are very generalized. They give players an idea of what goes on, but even the CMs don't read these. The CMs go into the real logs.
What we see on ahevents.org must itself be interpreted, as well, because we don't have access to those detailed line-by-line logs (nor will we ever, CMs only).
If you want to code a program to read the summary output from ahevents.org, you will need to find a way to best describe things. It's not absolute. Frame 2 may show no losses from being killed, but I promise you there were many a drone lost due to ack, manuvering to avoid attackers, and other reasons.
I don't think you can apply a totally logical tilt to filtering these logs, since filtering them (the act itself) is subjective as we see in the case of bomber drones.
Perhaps better to mainstream a few of the settings (such as kills, deaths, and so on) before handing the keys over to the CMs ;)
-
Oneway,
The logs do not show a death when a drone is loss. But they do show a kill of a specific plane type when that occurs. Try running your program to count the number of B-25 kills each frame.
-
Oneway,
The logs do not show a death when a drone is loss. But they do show a kill of a specific plane type when that occurs. Try running your program to count the number of B-25 kills each frame.
I have done that Fencer...I chose not to include loss of Drones as "Deaths" in the initial table...I chose not include ditch/bail/capture etc as a death....
As I mentioned above...with the exception of drones lost to maneuvering (when nowhere near an enemy - proxy NOT awarded AND the pilot lands his sortie), I have total and complete control over the drone situation...99.9% of the drones are accounted for...
Here is the table when you apply Krusty style Death to the event...including drones...with the exception of Vanished/Disco...Scenarios do not count Disco as Death
Its not the data....or my code...Its rock solid and can pump out any flavor desired...
woops...here it is
NOTE: This data set includes landing at the wrong base as a LIFE
The Machines:
| Fighter | Sorties | Kills | Lives | K/L | Destroyed | Field | Factory |
| La-5FN | 145 | 79 | 46 | 1.72 | 108 | 37 | 71 |
| La-7 | 250 | 241 | 108 | 2.23 | 98 | 89 | 9 |
| P-39Q | 148 | 33 | 34 | 0.97 | 164 | 56 | 108 |
| Yak-9U | 249 | 153 | 115 | 1.33 | 16 | 16 | 0 |
| Bf 109G-14 | 90 | 80 | 67 | 1.19 | 1 | 1 | 0 |
| Bf 109G-6 | 121 | 38 | 95 | 0.40 | 2 | 0 | 2 |
| Bf 109K-4 | 119 | 82 | 97 | 0.85 | 3 | 3 | 0 |
| Bf 110G-2 | 28 | 6 | 19 | 0.32 | 161 | 0 | 161 |
| Fw 190A-8 | 40 | 10 | 19 | 0.53 | 1 | 1 | 0 |
| Fw 190D-9 | 162 | 143 | 98 | 1.46 | 1 | 1 | 0 |
| Fw 190F-8 | 183 | 99 | 113 | 0.88 | 477 | 145 | 332 |
|
| Bomber |
| A-20G | 78 | 18 | 32 | 0.56 | 264 | 15 | 249 |
| B-25C | 152 | 29 | 191 | 0.15 | 1078 | 157 | 921 |
| Il-2 Type 3 | 141 | 31 | 91 | 0.34 | 166 | 163 | 3 |
| Ju 88A-4 | 91 | 9 | 192 | 0.05 | 505 | 137 | 368 |
|
| Tank |
| Sherman VC Firefly | 163 | 70 | 115 | 0.61 | 62 | 59 | 3 |
| T-34/76 | 3 | 0 | 1 | 0.00 | 0 | 0 | 0 |
| T-34/85 | 166 | 100 | 98 | 1.02 | 236 | 188 | 48 |
| Panzer IV H | 93 | 30 | 70 | 0.43 | 27 | 11 | 16 |
| Tiger I | 104 | 121 | 79 | 1.53 | 67 | 23 | 44 |
|
| AAA |
| Ostwind | 28 | 0 | 5 | 0.00 | 41 | 11 | 30 |
| Wirbelwind | 76 | 14 | 16 | 0.88 | 150 | 5 | 145 |
|
| Troop |
| M3 | 124 | 2 | 64 | 0.03 | 30 | 14 | 16 |
| SdKfz 251 | 106 | 1 | 63 | 0.02 | 21 | 21 | 0 |
|
| FieldGun |
| Gun Ship or Field | 157 | 14 | 0 | ---- | 12 | 12 | 0 |
|
| Gunner |
| Gunner-Observer | 93 | 8 | 0 | ---- | 0 | 0 | 0 |
BBS Code Generated by AcesHigh.Scenario.LogReader Class
A Scenario Planning, Management & Analysis program written by Oneway in C# .NET 3.5
Number of Auto-Generated Chars = 8960
-
Like I mentioned...
I already know who killed what and when...
wnt2/Fw 190D-9 shot down Soulyss/B-25C frame4 at 14:55:59
wnt2/Fw 190D-9 shot down Krusty/B-25C frame4 at 14:57:28
DrDea/Fw 190F-8 shot down Teufel/B-25C frame1 at 16:36:08
Fencer/Fw 190F-8 shot down cactus/B-25C frame1 at 15:17:43
Fencer/Fw 190F-8 shot down cactus/B-25C frame1 at 15:18:12
Fencer/Fw 190F-8 shot down cactus/B-25C frame1 at 15:18:28
Fencer/Fw 190F-8 shot down gas50/B-25C frame1 at 16:31:52
Fencer/Fw 190F-8 shot down Teufel/B-25C frame1 at 16:32:59
Fencer/Fw 190F-8 shot down tudza/B-25C frame3 at 14:38:53
Fencer/Fw 190F-8 shot down Strip/B-25C frame3 at 14:39:05
Fencer/Fw 190F-8 shot down Strip/B-25C frame3 at 14:39:18
Fencer/Fw 190F-8 shot down Duke/B-25C frame3 at 14:39:40
Fencer/Fw 190F-8 shot down Duke/B-25C frame3 at 14:40:04
Fencer/Gun Ship or Field shot down Harpij/B-25C frame4 at 17:16:30
gavagai/Fw 190F-8 shot down Soulyss/B-25C frame1 at 15:17:38
gavagai/Fw 190F-8 shot down Popsman/B-25C frame1 at 15:18:24
gavagai/Fw 190F-8 shot down Popsman/B-25C frame1 at 15:18:48
gavagai/Fw 190F-8 shot down Soulyss/B-25C frame1 at 15:19:37
gavagai/Fw 190F-8 shot down gas50/B-25C frame3 at 14:38:56
gavagai/Fw 190F-8 shot down gas50/B-25C frame3 at 14:39:09
gavagai/Fw 190F-8 shot down Duke/B-25C frame3 at 14:40:25
Hajo/Fw 190F-8 shot down tudza/B-25C frame3 at 14:40:46
Hajo/Fw 190F-8 shot down tudza/B-25C frame3 at 14:40:46
Joker1/Fw 190F-8 shot down Soulyss/B-25C frame1 at 15:17:34
Joker1/Fw 190F-8 shot down Krusty/B-25C frame1 at 15:18:07
Joker1/Fw 190F-8 shot down Krusty/B-25C frame1 at 15:18:53
lothmog/Fw 190F-8 shot down Popsman/B-25C frame1 at 15:18:24
lothmog/Fw 190F-8 shot down Krusty/B-25C frame1 at 15:20:14
TheMaj/Fw 190F-8 shot down GypsyB/B-25C frame1 at 15:18:17
TheMaj/Fw 190F-8 shot down GypsyB/B-25C frame1 at 15:18:19
TheMaj/Fw 190F-8 shot down GypsyB/B-25C frame1 at 15:18:35
TheMaj/Fw 190F-8 shot down cooley/B-25C frame3 at 14:38:51
TheMaj/Fw 190F-8 shot down cooley/B-25C frame3 at 14:39:02
TheMaj/Fw 190F-8 shot down cooley/B-25C frame3 at 14:39:10
Galland9/Bf 109G-6 shot down GypsyB/B-25C frame1 at 16:18:32
Galland9/Bf 109G-6 shot down GypsyB/B-25C frame1 at 16:18:36
Wedge/Bf 109G-6 shot down unclkurt/B-25C frame1 at 16:17:56
Wedge/Bf 109G-6 shot down Soulyss/B-25C frame1 at 16:18:32
Wedge/Bf 109G-6 shot down GypsyB/B-25C frame1 at 16:18:37
Heater/Bf 109G-14 shot down gas50/B-25C frame1 at 15:18:45
Heater/Bf 109G-14 shot down gas50/B-25C frame1 at 15:19:40
Heater/Bf 109G-14 shot down gas50/B-25C frame1 at 15:20:46
HotRod1/Bf 109G-14 shot down tudza/B-25C frame1 at 14:48:54
HotRod1/Bf 109G-14 shot down Doc72CH/B-25C frame1 at 14:54:39
HotRod1/Bf 109G-14 shot down tudza/B-25C frame1 at 15:21:02
Magpie/Bf 109G-14 shot down Teufel/B-25C frame1 at 14:46:42
Magpie/Bf 109G-14 shot down Hibbie2/B-25C frame1 at 15:20:53
SoonerMP/Bf 109G-14 shot down tudza/B-25C frame1 at 15:20:16
SoonerMP/Bf 109G-14 shot down tudza/B-25C frame1 at 15:20:16
SoonerMP/Bf 109G-14 shot down Teufel/B-25C frame1 at 15:21:10
Twizzty/Bf 109G-14 shot down gas50/B-25C frame1 at 14:50:36
Twizzty/Bf 109G-14 shot down Doc72CH/B-25C frame1 at 14:52:04
Twizzty/Bf 109G-14 shot down Teufel/B-25C frame1 at 15:20:59
Twizzty/Bf 109G-14 shot down Strip/B-25C frame1 at 15:21:48
Twizzty/Bf 109G-14 shot down Strip/B-25C frame1 at 15:22:02
Twizzty/Bf 109G-14 shot down Hibbie2/B-25C frame1 at 15:22:21
VANDALS/Bf 109G-14 shot down Hibbie2/B-25C frame1 at 15:22:15
VANDALS/Bf 109K-4 shot down Strip/B-25C frame3 at 16:51:37
Akondo/Fw 190D-9 shot down Soulyss/B-25C frame3 at 16:11:56
Akondo/Fw 190D-9 shot down gas50/B-25C frame4 at 14:55:03
Akondo/Fw 190D-9 shot down Popsman/B-25C frame4 at 16:36:46
Babalon/Fw 190D-9 shot down A8hunter/B-25C frame3 at 16:11:50
Babalon/Fw 190D-9 shot down cactus/B-25C frame3 at 16:14:49
Babalon/Fw 190D-9 shot down Krusty/B-25C frame3 at 16:15:11
HiSpd/Fw 190D-9 shot down GypsyB/B-25C frame2 at 16:51:16
HiSpd/Fw 190D-9 shot down GypsyB/B-25C frame2 at 16:52:09
HiSpd/Fw 190D-9 shot down GypsyB/B-25C frame2 at 16:52:37
HiSpd/Fw 190D-9 shot down cactus/B-25C frame3 at 16:08:39
HiSpd/Fw 190D-9 shot down GypsyB/B-25C frame3 at 16:11:20
HiSpd/Fw 190D-9 shot down Soulyss/B-25C frame3 at 16:11:26
HiSpd/Fw 190D-9 shot down Krusty/B-25C frame3 at 16:15:11
HiSpd/Fw 190D-9 shot down Krusty/B-25C frame3 at 16:15:48
HiSpd/Fw 190D-9 shot down cactus/B-25C frame3 at 16:52:06
HiSpd/Fw 190D-9 shot down Soulyss/B-25C frame3 at 16:52:51
HiSpd/Fw 190D-9 shot down Soulyss/B-25C frame3 at 16:58:19
HiSpd/Fw 190D-9 shot down Krusty/B-25C frame3 at 16:58:39
HiSpd/Fw 190D-9 shot down Krusty/B-25C frame3 at 16:59:49
HiSpd/Fw 190D-9 shot down Soulyss/B-25C frame4 at 14:52:49
JVnotch/Fw 190D-9 shot down cactus/B-25C frame3 at 16:53:24
JVnotch/Fw 190A-8 shot down Krusty/B-25C frame4 at 16:39:35
JVnotch/Fw 190A-8 shot down Krusty/B-25C frame4 at 16:40:34
thorsim/Fw 190D-9 shot down GypsyB/B-25C frame3 at 16:07:36
thorsim/Fw 190D-9 shot down A8hunter/B-25C frame3 at 16:07:56
thorsim/Fw 190D-9 shot down Beefcake/B-25C frame3 at 16:54:02
wagger/Fw 190D-9 shot down Soulyss/B-25C frame4 at 14:55:56
wagger/Fw 190D-9 shot down Beefcake/B-25C frame4 at 14:58:52
Wraith/Fw 190D-9 shot down Beefcake/B-25C frame3 at 16:52:09
Wraith/Fw 190D-9 shot down GypsyB/B-25C frame3 at 16:52:26
Wraith/Fw 190D-9 shot down GypsyB/B-25C frame3 at 16:52:52
Fudgums/Bf 109K-4 shot down gas50/B-25C frame2 at 16:57:01
MiG/Bf 109K-4 shot down Teufel/B-25C frame1 at 16:14:58
SunsFan/Bf 109K-4 shot down Strip/B-25C frame1 at 16:13:30
SunsFan/Bf 109K-4 shot down tudza/B-25C frame1 at 16:14:52
boingg/Fw 190D-9 shot down glennco/B-25C frame4 at 14:55:11
boingg/Fw 190D-9 shot down glennco/B-25C frame4 at 14:55:54
boomerlu/Fw 190D-9 shot down cactus/B-25C frame3 at 16:00:46
boomerlu/Fw 190D-9 shot down Krusty/B-25C frame4 at 14:56:38
boomerlu/Fw 190D-9 shot down Krusty/B-25C frame4 at 14:58:09
CANUKK/Fw 190D-9 shot down cactus/B-25C frame4 at 14:55:53
CANUKK/Fw 190D-9 shot down OzzyRev/B-25C frame4 at 14:56:46
CANUKK/Fw 190D-9 shot down Beefcake/B-25C frame4 at 14:57:12
Frodo/Fw 190D-9 shot down Popsman/B-25C frame3 at 15:59:40
Frodo/Fw 190D-9 shot down Popsman/B-25C frame3 at 15:59:44
Frodo/Fw 190D-9 shot down Popsman/B-25C frame3 at 15:59:45
Frodo/Fw 190D-9 shot down Beefcake/B-25C frame4 at 14:57:51
Morfiend/Fw 190D-9 shot down gas50/B-25C frame4 at 14:55:29
Spinner/Fw 190D-9 shot down Beefcake/B-25C frame3 at 15:59:48
Spinner/Fw 190D-9 shot down Beefcake/B-25C frame3 at 16:00:12
Spinner/Fw 190D-9 shot down Strip/B-25C frame4 at 14:57:32
Stampf/Fw 190D-9 shot down Harpij/B-25C frame4 at 14:54:22
Stampf/Fw 190D-9 shot down GypsyB/B-25C frame4 at 14:54:32
Stampf/Fw 190D-9 shot down GypsyB/B-25C frame4 at 14:54:44
Stampf/Fw 190D-9 shot down cactus/B-25C frame4 at 14:55:22
Turner/Fw 190D-9 shot down tudza/B-25C frame4 at 14:53:40
Turner/Fw 190D-9 shot down Strip/B-25C frame4 at 14:54:36
rob53/Bf 109G-14 shot down Duke/B-25C frame3 at 15:46:24
rob53/Bf 109G-14 shot down Strip/B-25C frame3 at 15:46:32
shamus/Bf 109G-14 shot down LTHopper/B-25C frame3 at 15:48:12
shamus/Bf 109G-14 shot down tudza/B-25C frame3 at 15:48:31
shamus/Bf 109G-14 shot down tudza/B-25C frame3 at 15:48:41
shamus/Bf 109G-14 shot down gas50/B-25C frame4 at 16:37:40
shamus/Bf 109G-14 shot down gas50/B-25C frame4 at 16:38:27
shamus/Bf 109G-14 shot down gas50/B-25C frame4 at 16:38:50
Voudou/Bf 109G-14 shot down tudza/B-25C frame3 at 15:47:20
Voudou/Bf 109G-14 shot down Strip/B-25C frame3 at 16:51:49
Voudou/Bf 109G-14 shot down Duke/B-25C frame3 at 16:52:29
Redtail7/Bf 110G-2 shot down Popsman/B-25C frame2 at 16:24:55
Redtail7/Bf 110G-2 shot down Popsman/B-25C frame2 at 16:25:04
Redtail7/Bf 110G-2 shot down Popsman/B-25C frame2 at 16:25:34
Beefcake/Gunner-Observer shot down A8hunter/B-25C frame3 at 16:10:11
Nutzoid/Fw 190F-8 shot down gas50/B-25C frame3 at 14:39:01
Nutzoid/Fw 190F-8 shot down Strip/B-25C frame3 at 14:39:24
GE063/Bf 109K-4 shot down gas50/B-25C frame3 at 16:51:40
4510/Fw 190D-9 shot down Krusty/B-25C frame2 at 16:50:16
4510/Fw 190D-9 shot down Krusty/B-25C frame2 at 16:51:13
4510/Fw 190D-9 shot down Krusty/B-25C frame2 at 16:55:34
4510/Fw 190D-9 shot down GypsyB/B-25C frame3 at 16:53:20
4510/Fw 190D-9 shot down cactus/B-25C frame3 at 16:55:43
4510/Fw 190D-9 shot down Popsman/B-25C frame4 at 16:37:14
4510/Fw 190D-9 shot down Popsman/B-25C frame4 at 16:37:24
horble/Fw 190D-9 shot down Beefcake/B-25C frame3 at 16:01:53
horble/Fw 190D-9 shot down OzzyRev/B-25C frame4 at 14:53:16
horble/Fw 190D-9 shot down Popsman/B-25C frame4 at 14:53:23
horble/Fw 190D-9 shot down gas50/B-25C frame4 at 14:54:19
horble/Fw 190D-9 shot down tudza/B-25C frame4 at 14:54:31
horble/Fw 190D-9 shot down tudza/B-25C frame4 at 14:55:30
horble/Fw 190D-9 shot down cactus/B-25C frame4 at 14:57:04
FOXTROT1/Wirbelwind shot down tudza/B-25C frame3 at 15:07:09
JVlobo/Fw 190D-9 shot down Beefcake/B-25C frame3 at 16:54:10
JVlobo/Fw 190D-9 shot down A8hunter/B-25C frame3 at 16:55:25
JVlobo/Fw 190D-9 shot down A8hunter/B-25C frame3 at 16:55:39
JVlobo/Fw 190D-9 shot down A8hunter/B-25C frame3 at 16:56:05
JVlobo/Fw 190D-9 shot down Soulyss/B-25C frame3 at 16:57:24
10thMD/Fw 190D-9 shot down Popsman/B-25C frame4 at 14:53:39
10thMD/Fw 190D-9 shot down Strip/B-25C frame4 at 14:59:01
Choppit/Fw 190D-9 shot down OzzyRev/B-25C frame4 at 14:53:30
Choppit/Fw 190D-9 shot down Popsman/B-25C frame4 at 14:54:37
-
Here is the table when you apply Krusty style Death to the event...including drones...with the exception of Vanished/Disco...Scenarios do not count Disco as Death
This is the way I too have used to calculate the K/D. Did I understand correctly that your program can be configured how it counts the deaths? If that is the case, it is great and I do not see the point of this whole argument here since both ways can be used.
-
I think it was a bit of confusion spiralling into bitterness :aok
I agree that it will be a nice tool, given that it's configurable.
-
Oneway,
Your next pm gets sent to Skuzzy......stop now while you think your ahead.
Strip
-
Shouldn't that went through PM strip?
-
Tried that already.....
Strip
-
La7s are great :)
-
This is the way I too have used to calculate the K/D. Did I understand correctly that your program can be configured how it counts the deaths? If that is the case, it is great and I do not see the point of this whole argument here since both ways can be used.
Exactley Right Have...
You can count Death or Life anyway you see fit...
What the program does is that it pareses the Log...
Then it fills in ALL of the missing holes in the Log such as the drones, reconciling who the "unknown" enemy was if it wasn't an autogun, missing launch fields because the logs were started too late, missing "rides" because the logs were started to late...it even goes as far as taking into account formations that hot padded and turned drones back into the hanger...even if 1 or 2 drones were killed on the first leg of the sortie...
It tracks what a squads predominate base is, and what their predominate ride is to catch guys who decide to up from the wrong field or in the wrong ride...did you know that in the Beta 221 BAD never recorded a Departure Field?...the log started late and they hot padded the entire frame...In this unique and special case, the program is forced to assume the squad predominate field is the predominate landing field, not the predominate departure field...in this case 221 BAD rtb'd finally at the end of the frame to A13...the program never was able to deduce the predominate ride of course...this is where the Human comes in and he assigns 221 BAD the A-20G for Beta...the program alerts the user to log anomaly and offers a solution...
It tracks what type and style of target was destroyed, where it was and when it happened...it even tracks and checks the ownership of a base through the course of frame and allows an object destroyed to be flagged because it belonged at the time to attacker...In RSKS, because you could attack your own country objects, I can print a full report of objects destroyed by their owners, and separate it by object type and style...during RSKS, it was quite common that just after a base had been captured...it continued to take fire from those attackers...until word got out that "WE GOT IT"....the program captures all of that because their is sub-module that is in essence a Title company that keeps track of who owned the base and when...by feeding it an object destroyed time stamp it feeds back whether the destruction is valid or invalid...
It tracks whether a strat object was part of the viable strat types allowed for that frame...in RSKS one guy bombed the Radar Factory for Allies....it checks that and knows it...
It tracks Friendly Fire, both Kills and Assists...and it does so by the type and style of the ride of both the attacker/victor and victim...It can output fighter to fighter FF, bomber to fighter FF, vehicle to vehicle FF...
It tracks every sortie including drones with respect to landing at a wrong field, hot padding an unauthorized field, landing too late....
It tracks hostilities that occurred after the call to end hostilities...
You can define the rules regarding troop transports and whether or not the transport driver captured a base or destroyed an object after his normal vehicle lives were used up...you can even define a number of extra lives for gv guys for use of transports at the end of the frame...
It has the option to scrub out double teamers; guys who managed somehow to fly for both sides in a frame (yes they occur in the frame logs and did so in RSKS).
It has the option to scrub out unnamed pilots; sorties in the log that do not even have a pilot name ( yes even this rare oddity occurs and did so in RSKS)
It has the option to scrub out ZZZ No Squad if desired...
It has the option to scrub out guys who flew for squadrons demonstrably out of color such as Koko's Flying Circus...
It even checks for pilots that flew for more than one squad, on the same team for a frame...and yes this rare oddity occurs...and did so in RSKS...yep...one pilot in RSKS started a frame in one squad, withdrew from that squad...and then joined another squad...his name is listed twice in the logs for that team...under two different squads...in this particular case I wrote a function that assigns this pilot to only 1 squad based on the time he spent joined to one of the two squads...in this case its the Pilots Predominate Squad check. This particular pilot upped a sortie with one squad then flew 4 other sorties in his Predominate Squad...the program allows you to scrub his non-predominate squad activity and achievement...the code and choices the user can make are that solid...that detailed...nothing is missed...
It checks launches from non-active airfields and vehicle bases as defined in the rules and set up by the user....in RSKS over 100 sorties were flown by aircraft from non-active airfields...from airfields standing in as vehicle bases...it allows the user to scrub all of that if desired...its as simple as flipping a true/false switch for that rule...
It calculates the amount of bombs dropped by bombers by selecting the assumed load outs for those plane types...taking into consideration whether drones are disabled or enabled for that plane for that frame...
And of course it checks multiple lives. It allows the user to check what a life is and is not...it tracks whether the pilot returned to the wrong field....
It allows the user to set up the bases that are active capture targets and defense targets, and apply a score or value to it. It allows the user to score the capture...or set a flag that checks only the end of the frame for the scoring....like in RSKS...which was capture and keep, defend to the end...
The user is allowed to set up the scoring schema...and the program will PERFECTLY score an event...if you want to score like Brook had it where machines lost were a point for they enemy...it does that...if you want to apply a higher score for certain types of aircraft or vehicles...it does that...if you want to score kills it will do that too...
All of this checking allows an even more profound capability...the ability to nullify the achievement of rule violators by any type of criteria....in other words if you want to scrub out friendly fire vehicle losses or kills...check a box...if you want deny a team points gained by kills or objects destroyed by multiple lifers...check a box...
Of course stats and reports are part of it...as well as scoring but it goes well beyond that...including mapping, routes, flight assignments, load outs, skins...auto generated orders, email lists for team members so a commander can send out the orders...
Its about Scenario Planning, Management and Analysis...
The Log Reader is one of 3 modules...
I started the first two modules right after Coral Sea...the Log Reader was started on the eve of RSKS ...
Their are over 15 thousand lines of code in this program so far...
Just so I am crystal clear...I don't care what switches people want to flip...this tool is being built so we have the switches to flip...deciding is above my pay grade and irrelevant to me...so long as we are all on the same page prior to the first frame...what the switches are, and which ones are flipped...then we live and die by the rules...
Oneway
-
But does it do Julienne Fries? ;)
-
But does it do Julienne Fries? ;)
:rofl
Don't worry...you will be swept up in a dragnet one of these days...not yet...but everyone makes a mistake sooner or later...
Lucky this time...
:aok
Output: Pilot == Fencer (ALL Switches Flipped)
=====================INVALIDATED KILLS ========================
invalidated kills: 0
=====================INVALIDATED OBJECTS DESTROYED ========================
invalidated objects destroyed: 0
-
Its hard to get into trouble when you are at 200 feet and 300 mph the entire scenario.