Mike5560

I just had the same problem. I RTB'd when I was about bingo. Never got credit for the mission. Spying on the package's Su-25s it seems only flight lead gets weapons off. And then they circle the target airfield doing nothing.

Either: 1. Have enough HARMS (~2 per TEL) to engage, and do not engage the Snow Drift radar. If you do, you'll likely be allowed to get closer to the site, but the track radars on the TELs will target you at random distances, which makes them difficult to target with HARMS. 2. Have other weapons in addition to HARM. Use HARM on the Snow Drift first to take out its SA, then move in terrain masked to engage with CBU / bombs OR fly at 30k fast as possible, take a gamble with GBU-38s. Should be able to release around 16nm range.

1. This is a non-standard targeting format; if this is the Raqqa mission, I'm familiar. Normally the JTAC will pass a 9-line and elevation is line 4.

I would think the SA-2 would be a good unit test, it operates at a lower band even than the SA-5; E/F/G band vs H.

I noticed this one the first HARM shot I took with the HTS. So I've been SAM hunting with GBU-38s; my hopeful workaround is to select the threat with the major and minor ellipse are small enough, and then immediately TMS down and rely on a TGP search. Another buggy thing I discovered while doing this is 95% of the time, the TGP remains slewed to where it went when I TMS up and TMS down on a radar.....but once in a while it slews back to the selected steerpoint.

I think there's possibly a legitimate issue here. One is potentially a bug, that the (HUD) target designator doesn't follow the targeting pod generated SPI. I don't know if that's accurate as-is for the F-16 though. I will say that attacking a moving target from the front with GBU-12s is a bit of a gamble. Often times from the front, the seeker will never acquire the laser with its narrow FOV. AFAIK, the ballistic solution isn't based on a moving target, it only calculates a solution based on a stationary target. If attacking from the front makes the most sense for other tactical reasons, it might be best to drag the TGP well in front of the target before release, drop, then reacquire the target, then lase. I just now tested hitting a BTR-80 going 45 kts on a straight road (from rear aspect) with no TGP trickery, just keeping on the target in point track. It appears to be updating the SPI position through the TGP.

I haven't noticed a marked difference in the JDAM accuracy. Killing main battle tanks with GBU-38s was about a 50% probability of kill from my experience from 2014 until the latest update. I just did a test with the Hornet and dropped 8x GBU-38s on eight separate T-90s and killed 5/8. More recently the flight profile was made more realistic, in the sense that the bombs maximize glide range for standoff. -This was probably necessary to model the GBU-54s, which do not use bang bang guidance. And before the update, their terminal velocity even flying a more ballistic path was quite slow (250-350 kts IIRC). I think there are some bugs in the sim logic that might need to be looked at, such as failing to reach the target on toss bombing; but then again it's not what they were designed for.

And the JTAC should be able to change their laser code. Everything IRL is changeable in mission except for the codes on the 12s themselves.

The L MAV has advantages that are much more beneficial to counter-insurgency operations (COIN). The target does not need to be an IR/EO significant blob, and with the laser you have much more precise control of where the weapon will impact. That said, it requires a man in the loop needing continuous lasing until impact.

I occasionally have the same comms issue in the F-16, though I havent had any issues with this campaign. Only thing I can suggest is make sure you use the VHF transmit comms key instead of the easy comms key. The runway headings at Kish are wonky. The two digits are rounded to the nearest 10 degrees of magnetic heading. So if a runway heading is 278 it should be labeled '28' and the opposite direction '10'. It might be an issue with the game, or an issue with the runway and what world magnetic model they were using at the time that causes a discrepancy in the game. I set my course knob to 090 for runway 09 "runway 10" and it's spot on.

Just to report an issue, I couldn't complete mission 11 (TARCAP). After reviewing the mission in the editor and the tacview file, I noticed a flight of MiG-25s that activated but did not taxi to the runway. After about an hour Id hoped there was a mission complete message that I missed so I RTB'd.

I don't use easy comms, and am pretty familiar with how the Viper comms work. Some missions, I cannot get the wingmen to listen or reply, so I am left to my own devices of engaging 4+ bandits. Even if the "flight" frequency is UHF and I change it to VHF, so I can monitor tactical and interflight. I don't remember if it worked for Coiled Viper, but I've had good luck on Island Style, Home on the Range and Night Life missions.

It only applies to Paveway II LGBs. GBU-10/12/16 have “bang bang” guidance.

Is it not trying to fly the route though? As in put you back on the actual line that is drawn between waypoint?

Appreciated! I will be sure to select information Alpha. Aside from the frustration in trying to pass the mission, I’m enjoying the campaign.