Fighting Irish Forums

Guess I'll get this one rolling.

First off, for those interested, here are a few sites with info worth reading:
1. http://tailslide.firelight.dynip.com/ww2art.asp" onclick="window.open(this.href);return false;
2. http://luthier.stormloader.com/SFTacticsI.htm" onclick="window.open(this.href);return false;
3. http://www.simhq.com/_air/acc_library.html" onclick="window.open(this.href);return false;

So far, I have not found any info specific to Ground Attack. However, I will continue to comb the hyper-universe for something concrete. This Sticky will be updated as often as I find sites with appropriate info. Any particular points of interest, personal observations, tips, etc., will be posted seperately.

I believe the first topics we should address should be Aircraft Familiarity, and Communication.
We should not only be familiar with our preferred aircraft, but more importantly, those of our foes. One can't consistently come out on top if one doesn't exploit the inherent weaknesses of other aircraft.

I'm sure all using TS have noted the lack of protocol when communicating, causing overlapped/missed/incomplete transmissions. Communications in a battle environment should:
1 - a)be as short as possible,
b)be as descriptive as possible, and
c)be as few as possible.
2 - A sample transmission, for example - "This is Helo. Bandits Ten o'clock low! Over!" or "Blue 3 to Blue 2. Gear up! Over!"
Note that in each transmission the transmitter a) identifies himself, b) gives the message/order, and then c) indicates the end of the transmission by saying "Over!"
3 - In the second example above, Blue 2 would respond "Roger that! Gear up! Over!"
I repeat: ALL transmissions should be ended by saying "Over!" to indicate to all that you are finished talking!

This may seem rigid to some, but it really is an effective way to communicate, and enhance situational awareness (SA).

Regardless of the power of one's PC, we can still only hear one person at a time. So if more than one are talking, the rest of us only hear a garbled mess consisting of two or more transmissions that are far from complete and even less understandable.

I'll bet dollars (Euro, American, or Canadian) to donuts that the established squadrons out there are basically using this system, and would recommend it to anyone.

I'll finished this opener with an announcement:

I just passed a kidney stone! (Either I have a dull dick, or those guys that told me about pulling fixtures out of the wall due to the pain are a bunch of pussies! )

sounds like good advice

that should be adered to

all for ts dicipline, and i can vouch for the know your enemy

i used to fly only german 109s (might be some wierd affiction)

but practicing for the VOW using russian A/C it really does help.

promise

( i heard passing a kidney stone is like drinking 18pints of guniess then trying to take a dump the next day) "painfull but necessary"

Redneck

Knowing different aircraft is important. One important thing to remember: boom and zoom with the German planes and turnfight with the Soviet planes There are a few exception of course, but in general that works. The 109 G2 can turn quite well for example.

is born!!!!



Ouch!

I distinctly recall may last episode with a bladder/kidney stone. There were no discernible flames but the smoke from the fire was very difficult to see through. Pissin red for two days was rather disconcerting as well.

...wasn't painful to pass. But working it's way down from the kidneys was MURDER!!!!

The drug conglomerates are good for something, after all!

I've discussed some training ideas with Rabitski. So, just a note for all of you joining in on the training sessions. Next Wednesday I'll be hosting a new tough as nails FI boot camp . So be prepared for a tough set of training missions.

s!
:twisted:

Here is some good reading material for us all:

The Vulture's Thought's on Air Combat
// a good short over view of air combat
http://www.vulch.cwc.net/manual.html" onclick="window.open(this.href);return false;

MarkShot's STK/EAW
// one of my favorite docs on 1v1 energy fights
http://www.simhq.com/_air/air_037a.html" onclick="window.open(this.href);return false;

SimHQ's Aircombat corner library
// a great set of articles (includes stuff on ground pounding)
http://www.simhq.com/_air/acc_library.html" onclick="window.open(this.href);return false;

Those are my favorite online references although there are many more.

I've read Mike Spick's Luftwaffe Fighter Aces, it's a good read but your not going to get that much aircombat tips from it just entertainment and history.

I also have Robert Shaw's Fighter Combat. It's a good book and very comprehensive but personaly I've found the online docs to be better. It is a bit dry so I don't think it is for everyone. *** I started reading Fighter Combat when I was a newbie to IL2 (before even going online) and I have recently gone back and started reading it again. I have to say its a whole different book after you have some more experience under your belt. I think it is a good book to read after you have read some of the online docs like SimHQ and STK and have gotten a good handle on 1v1 energy fighting. Once you have this practical experience under your belt this is a very good book.***

I would atleast read the first two docs I think they are realy worth the time investment if you are learning like me.

s!
Snoop

Can you direct me to a book on how to get Ardmore in an LA-7,off your six.

No need for a book....

Just shout "Your round" and see how fast he runs

G

Good one Finbar, only it had nothing to do with my flying, it was all down to my braces being wrapped around your rudder.


Vin

Dang I'm thinking off getting myself a pair of them braces now

We should follow this once in a combat situation .

Brevity code:



Directive: (Call Sign of whom you are talking to) + (Brevity Code words)

Example: "Numb Skull one two, Break left!"

Descriptive: (Your Call Sign) + (Brevity Code words)

Example: "Studly one one, Tally two left eleven, one mile, slightly high!"

"Directive: (Call Sign of whom you are talking to) + (Brevity Code words)"

>>> >>>anal grammarian gratuitous interjection<<< <<<

"Directive: (Call Sign to whom you are talking) + (Brevity Code words)"


also, something about which I know a wee bit less ...

if you are in a nice formation or you aren't scrambled up too much ...

it's okay to use one o'clock, two o'clock, etc.

but if there things are a confusing tangle,

then clock designations may mean little ...

keep aware of your position and try to give heading references instead.

ex: Dead Frog Six ... target north west high.

Opinions???


Gotta miss tonight, WAY too many family/Thanksgiving stuff happinin' ...

keep the faith and happy turkey day!!!


falcon

Discussions w/m8s via TS during practice.
Generally agreed on the following:

Directive: <Ident of caller+directive+end>
Ex: "Helo, Snoop Break left, Over"

Advisory:<Reciever(s) - Caller - Advisory - End>
Ex: "All, Bandits, 12 o'clock, Over"

Re Id and location of bandits, how about <heading+clock angle>
Ex: "Bandits at 270, 11 o'clock"
This would provide a good approximation if all are flying formation.

When in a fur ball, an advisory to a particular pilot could be no more than "Snoop, at your 9, high!"