Gary Grigsby’s War in the West 1943-45 is the most ambitious and detailed computer wargame on the Western Front of World War II ever made. Starting with the Summer 1943 invasions of Sicily and Italy and proceeding through the invasions of France and the drive into Germany, War in the West brings you all the Allied campaigns in Western Europe and the capability to re-fight the Western Front according to your plan.
the ***aircraft means another one of the same type is executing an attack, asterisk to show that something else Is happening
the rest Im not 100percent certain
"We are going to attack all night, and attack tomorrow morning..... If we are not victorious, let no one come back alive!" -- Patton
WITE-Beta
WITW-Alpha
The Logistics Phase is like Black Magic and Voodoo all rolled into one.
break off is if the unit takes losses and abandons its mission. Unit morale plays a large role here - if you play WiTE the Soviet airforce in 1941 is plagued with this result as they turn back after a few losses.
i enjoy watching the detailed action as well, and will welcome any further insight as to the meaning of the messages, especially the abbreviations used.
In air-to-air battles, it looks like what is often occurring is two opposing planes either trade shots or one plane gains an advantage and takes multiple shots at the other. When a shot hits, damage is reported in the form xx +yy and the durability rating of the target plane, where xx is the existing damage and +yy is the damage added by the most recent shot. If the encounter ends before the total damage exceeds the durability, the target plane is reported "damaged", or "shot down" or "destroyed" if the total exceeds durability. The x3, x4 and //2 indications seem to be multipliers to damage, but I cannot confirm for certain. BTW, "bounce" in A2A usually means a surprise attack, but I am not sure how it should be interpreted here - will continue to watch and see if it becomes apparent. Of course, this is all fogged if you have fog of war settings on, but that makes it even more fun...
Ground battles are also entertaining, especially when ground support is involved. I set the ground resolution detail to max (7, I think) and the message delay to 0.5 to make them readable and let an invasion battle play all the way through - it took over 4 hours to resolve, but the detail was fascinating. (I didn't sit there and watch exclusively for the whole time - I was relaxing and reading the very fine manual, referring to the play-by-play from time to time...) The action started at long range (I think something like "Firing range: 2000" and worked its way all the way down to 50 - are these in units of yards, or maybe meters?
I really like the system, and even though at the bottom of it all I know there are the inevitable simulated dice rolls, knowing that combat is modeled in such detail makes me feel like the decisions I make matter. Looking forward to learning more.
WARNING..., before anyone dies of boredom reading this post, I would like to say that this post is mainly for Mitchell who said that he welcomed more information.... continue at your own risk [:)]
I've observed the air combat phase a little closer by use of a video capture program (capable of 1/10 second indexing) and the following are some of my comments.
I've compiled 60 seconds of data which I have posted at the end of this post. All time based variables have been defined (eg, elapsed time index, delays, etc.)
The cycle of combat reporting appears to be:
STEPS:
1st) message identifies attacker & defender along with an the range (in unknown units).
2nd) message provides accuracy (?) of the specific weapon fired and a range (in unknown units).
2nd-A) based upon a probability (?): message indicates a special damage modifier.
3rd) message identifies the target and weapon(s) it was hit with (eg, .50 Browning MG(6) are six MGs).
4th) message provides [current damage level] + [inflected damage for this attack] along with airframe durability.
(Note: If the sum of damage is => airframe durability - the aircraft will be destroyed)
5th) message confirms the target was damaged - perhaps along with an "*" prefix - or even multiples of "*".
Per Belphegor - he proposes that the "*" deal with a different attacker. However I have only seen the "*" applied to the defending aircraft.
I agree with Mitchell's observations.
There may be a program glich dealing with the reported message routines - or maybe it is my lack of understanding. If you examine my compiled data - please remember that I was limited by only being able to index the video by 1/10 seconds.
At the elapsed time of 5.6s,I am told that "Destroyed by FLAK" - but the Spitfire was never specifically identified.
Between the elapsed time of 40.7 and 41.6, the Bf 109G-6 was never identified as DESTROYED.
At the elapsed time of 41.6s,you will see that the attacker is never identified.
Other observations:
Even though I have the combat message delay set to 0.5 seconds - it appears this is variable due to program processes.
The range given in the 1st step is multiplied by 5 (mostly) to produce the range given in the 2nd step.
The ACC which I think is the accuracy of the specific weapon does not equal the ACC under the device editor. This may be due to conditions (altitude, experience, tactics used, etc.) In any case - I could not find any pattern under my compiled attack summary.
Here is the compiled data:
Test 2, 12/31/14; Air Execution--:
Message Delay: 1.00 sec
combat Resolution Message level: 7
combat Resolution Message delay: 0:50 sec
combat Resolution Close Delay: 3:00 sec
Air Execution Phase Detail: High
@0:02.5
Execute Air Directives confirmed.
@0:02.7
Axis VP:25 Allied VP:7
Air Execution 0%
Pop-up of Air Execution Phase Progress window
stats Tab values are all 0
Allied red-line bomber path displayed
@0:03.0
Air Execution 1%
@0:03.4
Air Execution 5%
@0:04.4
Axis VP:25 Allied VP:10
Air Execution 8%
Air Execution Phase Progress window (stats) are populated; operational losses - Axis 13 Allied 0
@0:05.6
Pop-up of Combat Resolution window
AIR COMBAT
Message - Detroyed by FLAK
NOTE: No losses are indicated in window
@0:06.2
Message - Detroyed by FLAK
Allied total loss of 1 bomber indicated
@0:06.8
Message - Spitfire VB damaged by Flak
Allied total loss of 2 bomber indicated
@0:07.0
Message - Spitfire VB damaged by Flak
Air Execution Phase Progress window (air directive) shows:
Tactical Air Force
@0:14.4
Message - Spitfire IX/XVI firing at Bf 109G-6 - range 5
@0:15.1
Message - Bf 109G-6 firing at Spitfire IX/XVI - range 3
@0:15.9
Message - ACC 22::Range 15
@0:16.3
Message - ...damage x4
@0:16.9
Message - Spitfire IX/XVI damaged by 20mm Cannon MG151(1)
@0:17.5
Message - ...damage 0 + 10, durability 28
Air Execution Phase Progress window (air directive) shows:
Tactical Air Force
@0:18.1
Message - ACC 31::Range 15
@0:18.9
Message - ...damage x3
@0:19.4
Message - Spitfire IX/XVI damaged by 13mm MG131(2)
@0:20.1
Message - ...damage 10 + 9, durability 28
@0:20.7
Message - *Spitfire IX/XVI damaged
@0:21.4
Message - Bf 109G-6 firing at Spitfire IX/XVI - range 5
@0:22.0
Message - ACC 22::Range 25
@0:22.7
Message - ...damage x4
@0:23.2
Message - Spitfire IX/XVI damaged by 20mm Cannon MG151(1)
@0:23.7
Message - ...damage 0 + 10, durability 28
@0:24.6
Message - Bf 109G-6 firing at Spitfire IX/XVI - range 4
@0:25.0
Message - ACC 22::Range 20
@0:25.8
Message - Spitfire IX/XVI damaged by 20mm Cannon MG151(1)
@0:26.6
Message - ...damage 10 + 2, durability 28
@0:27.0
Message - ACC 31::Range 20
@0:27.6
Message - ...damage x3
@0:28.3
Message - Spitfire IX/XVI damaged by 13mm MG131(2)
@0:28.8
Message - ...damage 12 + 9, durability 28
@0:29.7
Message - Bf 109G-6 firing at Spitfire IX/XVI - range 3
@0:30.0
Message - ACC 31::Range 20
@0:30.7
Message - Spitfire IX/XVI damaged by 13mm MG131(2)
@0:31.4
Message - ...damage 0 + 3, durability 28
@0:31.9
Message - P-40N Warhawk firing at Bf 109G-6 - range 3
@0:32.7
Message - ACC 35::Range 15
@0:33.1
Message - ...damage x4
@0:34.0
Message - Bf 109G-6 damaged by .50 Browning MG(6)
@0:34.5
Message - ...damage 0 + 36, durability 31
@0:35.3
Message - *Bf 109G-6 destroyed
Allied total loss of 2 bomber indicated
Allied total loss of 1 fighter indicated
Axis total loss of 1 fighter indicated
@0:35.9
Message - P-40N Warhawk firing at Bf 109G-6 - range 2
@0:36.3
Message - ACC 35::Range 10
@0:37.0
Message - Bf 109G-6 damaged by .50 Browning MG(6)
@0:37.7
Message - ...damage 0 + 9, durability 31
@0:38.2
Message - P-40N Warhawk firing at Bf 109G-6 - range 1
@0:39.0
Message - ACC 35::Range 5
@0:39.4
Message - ...damage x4
@0:40.0
Message - Bf 109G-6 damaged by .50 Browning MG(6)
@0:40.7
Message - ...damage 9 + 36, durability 31
@0:41.6
Message - firing at P-40N Warhawk - range 1
Allied total loss of 2 bomber indicated
Allied total loss of 1 fighter indicated
Axis total loss of 2 fighter indicated
NOTE: there was no message indicating that the Bf 109G-6 was destroyed; however the total axis losses
indicated increased by 1.
@0:41.9
Message - Bf 109G-6 firing at P-40N Warhawk - range 4
@0:42.6
Message - ACC 31::Range 20
@0:43.3
Message - ...damage x4
@0:43.8
Message - P-40N Warhawk damaged by 13mm MG131(2)
@0:44.6
Message - ...damage 0 + 12, durability 31
@0:45.0
Message - **P-40N Warhawk damaged
@0:45.6
Message - Bf 109G-6 firing at P-40N Warhawk - range 4
@0:46.4
Message - ACC 31::Range 20
@0:46.9
Message - P-40N Warhawk damaged by 13mm MG131(2)
@0:47.7
Message - ...damage 12 + 3, durability 31
@0:48.3
Message - Bf 109G-6 firing at P-40N Warhawk - range 3
@0:48.8
Message - ACC 22::Range 15
@0:49.5
Message - P-40N Warhawk damaged by 20mm Cannon MG151(1)
@0:50.0
Message - ...damage 0 + 2, durability 31
@0:50.8
Message - Bf 109G-6 firing at P-40N Warhawk - range 3
@0:51.2
Message - ACC 22::Range 15
@0:51.9
Message - ...damage x3
@0:52.6
Message - P-40N Warhawk damaged by 20mm Cannon MG151(1)
@0:53.4
Message - ...damage 0 + 7, durability 31
@0:53.8
Message - ACC 31::Range 15
@0:54.4
Message - ...damage x3
@0:55.2
Message - P-40N Warhawk damaged by 13mm MG131(2)
@0:55.8
Message - ...damage 7 + 9, durability 31
@0:56.4
Message - ***P-40N Warhawk damaged
@0:56.9
Message - P-40N Warhawk firing at Bf 109G-6 - range 4
@0:57.7
Message - ACC 35::Range 20
@0:58.2
Message - ...damage x3
@0:59.0
Message - ...damage +22
@0:59.4
Message - Bf 109G-6 damaged by .50 Browning MG(6)
@1:00.0
Message - ...damage 0 + 38, durability 31
@1:00.7
Message - ****Bf 109G-6 destroyed
Allied total loss of 2 bomber indicated
Allied total loss of 1 fighter indicated
Axis total loss of 3 fighter indicated
Bf 109G-6
Durability is 31
Weapons loadout
one 20mm Cannon MG151 (#0032), Accuracy: 21
two 13mm MG 131 (#0024), Accuracy: 29
P-40N Warhawk
Durability is 31
Weapons loadout
six .50 Browing MG (#0023), Accuracy: 29
Spitfire IX/XVI
Durability is 28
Weapons loadout
two 20mm Hispano Cannon (#0034), Accuracy: 26
four .303 Browing MG (#0005), Accuracy: 34
Attack Summaries:
Spit
ACC 28 r = 15
ACC 28 r = 15
Bf109
range 3 ACC 22 r = 15 20mm (damage 10) damage x4
range 5 ACC 22 r = 25 20mm (damage 10) damage x4
range 4 ACC 22 r = 20 20mm (damage 2)
range 3 ACC 31 r = 20 13mm (damage 3)
range 4 ACC 31 r = 20 13mm (damage 12) damage x4
range 4 ACC 31 r = 20 13mm (damage 3)
range 3 ACC 22 r = 15 20mm (damage 2)
range 3 ACC 22 r = 15 20mm (damage 7) damage x3
P-40N
range 3 ACC 35 r = 15 .50 cal (damage 36) damage x4
range 2 ACC 35 r = 10 .50 cal (damage 9)
range 1 ACC 35 r = 5 .50 cal (damage 36) damage x4
range 4 ACC 35 r = 20 .50 cal (damage 38) damage x3 damage +22
Cheeks - good stuff, and thanks for sharing it. Never thought of trying to capture - our observations and conclusions are clearly consistent, at least as far as what can be gleaned from the messages offered during combat execution. I will keep watching resolution messages and add as I can. In the mean time I am really enjoying this game. The more I understand the more I appreciate the effort that went into creating so detailed a simulation, and the better I get at playing.
