Jtac will not answer.

[WildBillKelsoe]

Even if you do the radio comms right. There are indeed times when the JTAC either does not answer or answers later and sometimes doesn't give you further remarks. I figure that's realistic given the fog of war. One thing I started doing in the campaign to avoid labels is practice using mark points. Based on the briefing and map you have an idea where the enemy will be. So drop a bunch of mark points in the area. Set them as SPI and search that way.

 

If you have 1.1.1.1

I suggest Speed's Radio fix. it just did wonders!

[Jordan4]

Well I am in action. Watched a bunch of youtube tutorials and I am using the radio pretty well now. I still have a long way to go as I do not yet know how to intercept an enemy aircraft based on AWACS information nor do I know how to use the tacan to link up with a tanker. With the help of the people on this forum and youtube I am sure I will have the entire plane down in no time and be ready to start learning the P-51 in better detail and then go on and start learning the Ka-50 ( still havent done so since I bought it when it came out....) which I will go ahead and get blackshark 2 to do. Lets say I got a message that said " engaging armor bullseye 142 for 2" is there any way to take that information and input it into the cdu and create a waypoint so you can also engage that area? Thank you. Oh and can somebody decipher this for me: Hawg 1-1, Magic, Bra, 064 for 14 at 8000 flanking ( where is there a reference that tell you how to decipher radio comms like that? )

[WildBillKelsoe]

If AWACS/GCI has contact with an enemy aircraft then: "(a), (b), bandits bearing (x)(x) for (y)(y)(y). © (d)," where (a) is the callsign of the player, (b) is either "Olympus" or "Overlord" depending on if the player is flying an American or Russian aircraft, (x)(x) is the bearing to the threat in degrees, (y)(y)(y) is the range to the threat in miles if flying an American aricraft or kilometers if the player is flying a Russian aircraft, © is the altitude of the contact, and (d) is the aspect of the contact. Example: "Puma one one, Olympus, bandits bearing two zero for zero three five. Angles medium, Hot." If AWACS/GCI does not have contact with any enemy aircraft then: "(a), (b), clean," where (a) is the callsign of the player and (b) is Olympus if the player is flying a US aircraft or Overlord if the player if flying a Russian aircraft. Example: "Hawk one one, Overlord, clean." If enemy aircraft are within five miles of player then: "(a), (b), merged" where (a) is the callsign of the player and (b) is either Olympus or Overlord depending on the side the player is flying for. Example: "Dagger one one, Overlord, merged."

straight from LOMAC manual.

 

The AWACS response differs according to the range of enemy air groups:

 If BULL (over 50 nm): (Your flight’s callsign), (AWACS callsign), new picture, <number of groups detected> groups. First group, bulls <bearing> for <range>, <altitude band>. Second group, bulls <bearing> for <range>, <altitude>. (repeats up to three groups)

 If BRA (under 50 nm): (Your flight’s callsign), (AWACS callsign), new picture, <number of groups detected> groups. First group, bra <bearing> for <range>, hits <altitude band>. Second group, bra <bearing> for <range>, hits <altitude band>. (repeats up to three groups)

from A-10C manual.

 

In your case:

Hawg 1-1, Magic, Bra, 064 for 14 at 8000 flanking

 

Hawg 1-1 is your callsign

Magic is AWACS callsign

 

BRA = BearingRangeAltitude band to follow in the line so,

 

Bearing 064°

Range 14 nautical miles

Altitude 8000 feet

Flanking means his aspect is in parallel to your aspect, but incoming. Once he turns his nose towards you, it is now HOT. If he turns away from you, it is now COLD.

 

When to panic? When MERGED and you still haven't spotted him OR if HOT and RWR goes off MSL launch warning.

Edited September 17, 2012 by WildBillKelsoe

[SharpeXB]

If you have 1.1.1.1

I suggest Speed's Radio fix. it just did wonders!

I have version 1.2.0 should I still use the mod?

[WildBillKelsoe]

I have version 1.2.0 should I still use the mod?

 

negative, wait for speed he's making a 1.2.0 iteration for the same issue.