Pyrocumulous

Not a problem, it's just the SA-10 codes that are listed. Also of note in M14 in DCS 2.9.17.12034, sometimes Crew Chief 6 collides with Uzi 2-2 prior to taxi. Sometimes it goes under the nose, sometimes it goes boom. Similarly in M13 (also DCS 2.9.17.12034), but has no mission impact, NPC Heli-2 -3 lands on top of NPC Heli-2 -2 and also goes boom.

HARM codes for SA11 in the briefing should be: 107: Snow Drift target acquisition radar 115: Fire Dome target tracking radar in the TELAR reference: APPENDIX B – ALIC CODES & RWR SYMBOLS of the DCS aircraft manual

Radio traffic in mission 10 says: "1-2 -1-2 switch to Darkstar Chanel 3 on Uniform" and then "1-1 1-2 check on Channel 3 Uniform." However, channel 3 is 399.97 rather than 355.50.

The exploding bombers? I think it was M03.

It does work when using the Flight Engage Bandits command; thanks. There does seem to be an awful lot of exploding bombers at Anderson, presumably due to the bumpy terrain in the taxiways. Nothing you can do about that, though. Is kind of amusing to hear the regular chatter on the flight frequency meanwhile a C-17 just blew up in front of our eyes.

Ski jumps in the taxi ways are normal DEM / topo lines and experience on Guam suggests this is erroneous; was hopeful it would get fixed with WW2 work. Best to just fly rotors at Anderson.

I'll try again when I have a chance to fly again in a few weeks. Is that the intent, to issue that command to the entire flight? I wasn't sure, and I think I tried that. Same issue on the following mission. I believe that I'm on the right frequency, but I don't recall there being a channel plan in the briefing or kneeboard, so I just punched in frequencies as directed by radio traffic. I definitely hear traffic that makes me think all is working as intended.

I didn't see a way to instruct the wingman to engage the bandits in mission 2; did I miss something? He just trails me around while I go Winchester.

#3 only happened twice, so I'm not sure, but seems reasonable to assume that I missed a trigger near WP6 on RTB. Those might have been the times I was experimenting with taking out the SA11 and SA2 with an extra pair of HARMs and then boogying west to WP6 to skirt their engagement zone. I definitely didn't get any of the fence out or approach / tower queues when #3 occurred.

This mission appears to be having issues with: 1) scoring: It doesn't seem to be possible to score 100 regardless of whether you just destroy the southern two SA-6s, get all three, or even go grab a couple extra snow drifts as well. 60 points is what I get every time, no matter what. It doesn't seem to matter if you jump the gun and shoot the HARMs as soon they come online or wait to complete the briefing. 2) Post-mission Briefings: Out of 10 completions, I only once got a briefing, so not sure what scoring deductions are occurring. 3) lost communication: Same experience as @AlessandroFuBu except without AAR, I'd lose all prompts somewhere around WP6, and get nothing all the way home including approach, tower, ground, and no Mission Complete upon arrival at the shelter. Score of 50 both times that this occurred. Love the campaign, thanks for your work! Really like the post-mission briefings when they work.

Minor issue, but the fighter to fighter briefing for Mission 9 sorts the launchers when clearly the radar is intended since weapon is AGM88s: PLAYER: Two, one. Fighter to fighter. Line abreast, shooter - shooter, AGM-88, in from the east, off north, sort north. Lead takes two southern launchers." Question: what is the best way for a pilot to determine which two SA-6s are the southern most? Compare latitudes? For the two that are close together (eastern pair), which is the southern most is obvious in the TPod, but not so much for the western one.

I flew M02 twice, and both times, Weasel 33 crashes into Texaco upon disconnection. Weasel 33 must be invincible, because he keeps going, but seems to miss some radio traffic after that so maybe radio damage? Texaco doesn't fair so well. I'm not sure how a mission creator prevents that, though. DCS version 2.9.15.9599.1

I did some testing, and was able to recreate it. It is due to Spartan 3 landing at the same time as Sword 2, so it appears to be the player's grade but it is not. When I flew Mission 9, Spartan 3-1 trapped the moment I landed, and then 3-2 when I exited the runway. Apparently LSO grades are broadcast to everyone on the coalition, regardless of distance.

This is the first mission (#9) I've flow since the 2.9.15.9599 update, so it could very well be a DCS or Syria bug, but upon landing at Akrotiri, I'm given a LSO grade. I suspect it's not a mission bug, but I'm not seeing any mention in the main DCS bugs or Syria forums, so, weird, huh?

Ditto this! I have a campaign outline created for exactly this that I'd be happy to give away, but the reality is that I'm never going to have time to give it the attention it deserves . The reference points scattered around Sweden when "real life" is used are pretty fantastic for allowing the player to deal with unexpected twists. The radio logic for triggers is kind of weird, not nearly as simple as with Viper or Hornet, but I figured out pretty efficient way of handling that. The real headache for me, anyway, was building an ATC system for the BAS 60/90 air bases, each with numerous runways. A Viggen campaign has to use roadbases to be fun /realistic, and a probably a whole bunch of them. In my mind, ATC should work like it does in a Ground Pounder campaign, and for me anyway, the sheer quantity of triggers quickly got out of hand given the limited time I could devote to the project.