xflyer

Oh phew - glad the lag roll repeat bug is known. I got dumped out to the debrief screen on my first play-through when loading the first task. Then I uninstalled all of my beloved mods except SRS and the A-4 and tried again. Got though three repeats of lag pursuit, did the lag roll and decided to try one more time. Got dumped out again. I was starting to get frustrated that this might keep happening, but glad to know I triggered the one known instance of this being bugged.

In '82, correct. Shortly after that they stuck an AEW radar on a Sea King, which would be a nice asset for the Invincible.

Really? I swear I've set it to "CAP" in the ME and it's been allowed. Radar-less intercepts would be more practical with vectors. Too bad we don't have either GCI or the RN's AEW&C helicopters, but you could put in a hidden AWACS as a substitute.

To come up with something fun for a campaign you basically have to do an alternate history scenario. Here are a few ideas: 1. Move the war to the early '90s and pretend that either the Sea Harrier never existed or it was retired early and the RAF/RN is now using the GR.5 under Joint Force Harrier. 2. There's an HMAS Melbourne model out there. Maybe it's still 1982 but the Sea Harrier never existed, so the RN just has helicopter carriers. Australia joints the coalition, and the RAN brings the Melbourne with its Skyhawks to provide air cover. 3. Scenario 2, but it's a few years later and the Aussies now fly Hornets off the Melbourne, which they keep in service (I think the Hornet is compatible) 4. Scenario 3, but the Aussies bought the Bon Homme Richard to replace Melbourne (use the new CV-31 model), allowing them to fly E-2s and S-3s in addition to the Hornet 5. This one's outlandish, but let's pretend that the US actually got possession of the islands (which is plausible after the intervention of the USS Lexington in 1831). Argentina invades in the middle of Desert Storm, making the US resources available for response far more limited, maybe just a single carrier and an LHA.

It was probably the dive angle and not using CCIP. Used CCIP on the first target and got it right away, then tried CCRP with the DMT on the second one in a pretty shallow attack. Kept nailing the building, not the units.

Did you manage to kill the second target? I dropped 3 MK82s and emptied my gun into it, but kept getting reattack calls. Finally flew away with the JTAC no doubt cursing me.

I should add that I could be completely wrong about elevation being important for the TGP. I only noticed that behavior specifically on the DMT, but unless the TGP knows the elevation profile I'd imagine it's the same.

Which mission? I flew M4 the other night and it was in both nine lines.

Try entering the elevation as well. That fixed it for me. Otherwise the pod is looking at a spot almost a mile underground.

OK, so 100% operator error on my part. I didn't realize I had to take the EHSD out of "Data" mode. I was also wondering why waypoint designation wasn't working.

I'll try a repair again. Yes, the WP increment HOTAS button works but clicking the arrows up and down on the EHSD will cycle the waypoints on the EHSD but will not update the selected waypoint in the HUD. I will still allow that this may be user error on my part. On one of my last missions a single button push was the difference between successfully lasing the target and ballistically dropping my GBU-12 on a residential neighborhood!

Update: Uninstalled almost all of my mods except VoiceAttack and SRS, since I need those for MP. Still wasn't working (skin did not appear in ME or the campaign). BUT, I discovered a workaround: I just copied the skin to my saved games/DCS/liveries folder and it now works fine.

I have SAM sites and A-4E as well, so one of those might be the culprit.

I'll do some investigating tonight. Running a couple of asset mods, VoiceAttack, and SRS.

This has been happening to me too, on every map, before and after the MT patch (and I did run a repair post-patch). Only way to cycle WPs is the WP increment bind. I assumed it was operator error, but still can't figure it out.

Just completed Mission 1 - Awesome work, it's great to have a Harrier campaign that's up to the current standards of immersion, and this really is. Had to attempt M1 twice after I forgot how to lase properly. I'm not sure I did much to win hearts and minds when I ballistically dropped a GBU-12 into a residential neighborhood. One issue though - all of the Harriers in M1 had the default VMA-223 livery. I see the VMA-311 DetB skin in the campaign folder. Haven't played M2 yet. I'm running the multithreading beta on Steam.