SLs, Pilots, get set up to call in Air Strikes

[StrikeFear]

The gist:

• SLs hit a key to whisper to all listening pilots, requesting airstrikes. They have 2 keys total, one for USMC, one for the other team.
• Pilots must log into TS using preset nicknames. Pilots tap a key to "bind that whisperer to a preset" and then press another key to talk to them.

SLs use the approprate key, depending on the team they're on.
Pilots log in using a particular nickname. They then hear the requests. When they hear it, they bind the whisperer to preset 0. Then they use the other key to whisper back to them.
When they get a request from another SL, they can bind/whisper again.

NOTE: Please use good comm procedures when doing this. Be brief, and ensure that you have our attention and that we're available. Below is an ideal example:
SL2: Squad 2 requesting air strike, over.
531: Airstrike available, squad 2.
SL2: Enemy armor, northeast of our position, ready to spot them.
531: Airstrike ETA 20 seconds.
... 10 seconds passes ...
531: Squad 2, spot the armor
- - - (Hopefully he's listening. I don't want to ask him to "come in" cuz it's too much comms. If he doesn't get it spotted, I'll ask again.
Armor gets spotted and crushed.

For more information, see these threads:
http://www.tacticalgamer.com/battlefield-2-general-discussion/58404-air-strikes-via-teamspeak-help-w-ts-pls-take-2-a.html
http://www.tacticalgamer.com/battlefield-2-general-discussion/58408-airstrikes-via-teamspeak-open-thread.html

Setup
Pictures are included below.
Also, a keybind file is included which has the keybinds shown in the picture. WARNING - if you import it, it will overwrite your current keybinds. You can save your current ones by exporting them to a file.

SLs
Set up a 2 keys to "Whisper to player list" and add all these names (which never change) to one:
USMCPilot1
USMCPilot2
USMCPilot3 ...etc up to 6

Now add all these names to the other one:
OPFORPilot1
OPFORPilot2
OPFORPilot3 ...etc up to 6

Pilots
1. Set up a key to "Bind last whisperer to preset 0"
2. Set up another key to "Whisper to preset 0"
3. Login to TS using your login/pword, but one of the preset nicknames.

[Ragged]

Cool. I set the SL bindings so I'll give it a try. Not sure why I put bindings for US pilots though since I don't really remember the last time I ended up on the US team.

If I have time tomorrow I might look into the SL comm rose and see if it is moddable since it would probably be a better solution. I just perfer stuff that integrated directly into the game.

[John CANavar]

keys are set, looking forward to test day on Sat...

[KeithMann]

Sounds good, let's try it out.

[StrikeFear]

Here is another excellent feature to help pilots (not SLs).

Pilots can logout/login to switch their nicknames without alt-tabbing from the game!

After you've set things up as described, make additional hotkeys for:

"Switch to server: <UMSCPilot1>"

... and for the others as well.
You might use these hotkeys:
Shift-Alt-Numpad1 - USMCPilot1
Shift-Alt-Numpad2 - USMCPilot2 .. etc.

Ctrl-Alt-Numpad1 - OpForPilot1
Ctrl-Alt-Numpad2 - OpForPilot2 ... etc.

Using this hotkey will VERY QUICKLY (<1 sec) disconnect you and reconnect you with the new nickname.
You'll reappear in the default channel, so you should create a channel switch hotkey to move you to the main "BattleField2 Retail channel".

[StrikeFear]

If you hear this announcement, TS airstrikes are LIVE!
It also comes in Chinese and MEC flavors.

[Kedge]

What happens if an SL or CO isn't using this particular system? Just defaults to normal coms?

[StrikeFear]

Correct

[AzrealDarkmoon]

I would love to use this, but for some odd reason BF2 and Teamspeak will not run at the same time. One shuts the other off.

Az

[StrikeFear]

The more players that know about this (both pilots and strike requesters), the more useful it will be.

[Obi]

Hey strikefear. How did the rest of the testing of airstrikes go? I had to leave early when it was being tested on the private server but it seemed to be working really well.

[John CANavar]

Strike,

It would be good if we posted the results of practice session here so that the ones who couldnt join would know the procedure. Especially the standard radio communication for requesting air strike and giving out the details.

[StrikeFear]

Argument for SL-requested air strikes

1. COs can't do it fast enough.
   With fighters, we can strike every 20-30 seconds. COs are too busy.
   With the bomber, we can strike every 10 seconds. COs are too busy to issue the jets orders every 10 seconds.
   LISTEN! The COs really don't actually want this job!
   (NOTE: There are occasions where the CO needs to designate a priority air strike that no SL would call in.)
2. COs don't have enough information.
   They can use the targets that players have spotted - but the jets can see that too.
   They can use the UAV - but the jets can see that too.
   They can use the scan - but it doesn't tell them what is armor or helo or infantry.
   They can use what the squads tell them - but the squads can just tell the jets.
   In EVERY case, there is ANOTHER problem. The CO doesn't know what the priority targets are. We may all see that someone has spotted a tank off on the horizon. But ONLY a squad knows (within the 20-second window), WHICH target they NEED eliminated to complete their mission.
   The jets don't know. The CO doesn't know ALL THE TIME. The information must be shared for us to be effective. If someone goes through the trouble of hitting the TS PTT key to call an airstrike, we darn well know they need it, and we WILL BE THERE.
   Otherwise, we spend our time wandering around wondering if the kills we get make any difference other than costing the enemy a ticket or 2.
3. Proof is in the pudding.
   During the scrim, a CO previously commended for his use of air squads, and another CO who actually has spent time flying - both of these COs recognized for excellence, one of them determined to keep in mind to use the jet squad well - failed to use the jet squad with ANY reasonable effectiveness. NO DISCREDIT TO THEM. None at all. I am convinced that the tools necessary to do that job well just aren't in the CO role. They didn't, because they couldn't.
   The best thing a CO can do for his squads concerning the jets is say, "Here squads, here are some jets. Use them as you see fit, until I need them for something specific."

Protocol for SL-requested air strikes
First, read this thread:
http://www.tacticalgamer.com/battlefield-2-general-discussion/58463-sls-pilots-get-set-up-call-air-strikes.html

Successful protocol
SL2: Squad 2 requesting air strike.
531: Airstrike available, Squad 2.
SL2: Tank, northeast of our position.
531: Airstrike ETA 20 seconds.
SL2: Airstrike positive. (or "Airstrike successful." or "Good kill." or "Target down.")

Once familiarity with the protocol is established, it can be shortened. This is helpful, because air strikes can often be completed inside 10 seconds.
Successful protocol - abbreviated
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Tank, northeast.
531: ETA 10 seconds.
SL2: Airstrike positive.


Special conditions:

Not available
SL2: Squad 2 air strike.
531: Negative, Squad 2. (or "Airstrike not available, Squad 2.")

Airstrike failed
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Enemy armor, northeast of our position.
531: ETA 10 seconds.
SL2: Airstrike negative. (Give new target info)
Examples: Target moving north. Target same location. Wrong target killed. (We hit the jeep instead of the Tanks. Oops.)

Abort
SL2: Squad 2 air strike.
531: Go squad 2.
SL2: Enemy armor, northeast of our position.
531: ETA 30 seconds.
SL2: Abort air strike, target down. (Target has been killed already)


Protocol for CO-ordered air strikes
CO: Creates attack marker waypoint
CO: "Target: helo" (NOTE: 2 words. Loud and clear.)
531: "ETA: 20 seconds"

There are only 2 excuses for not complying with a COs air strike order:
1. Currently dogfighting ("Strike unavailable-dogfight")
2. Jet is down ("Strike unavailable-jet down")

If either is the case, report that to the CO instead of giving an ETA.

[John CANavar]

very good job Strike !

[Obi]

Yeah I'm looking forward to trying this out in game.