Pyrocumulous

#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.

I replayed Mission 8 to see what happens if you don't stay tight during the I couldn't get Sentinel to clear for Silver, couldn't get Approach F10 to come up, couldn't get Emergency F10 to come up (but did verify radio was working, because I could hear the ATIS), I hit Anane Star, still couldn't get Tower, nor Ground when taxiing back to parking. I kept figuring the fail safe would kick in, but it didn't. Clearly, this wasn't what the player is supposed to do, and I'm not sure that it'll break it every time. If you want the track or tacview recording, I could upload them somewhere, but they are way too big for here. Great mission, thanks for the fun.

The sleeve goes at the top 1/4" screw to expand it's diameter to fill the damper's hole. Here's a photo. I had to replace that listed dampers after it failed, this 351mm dual tube damper, so far, seems superior.

Worked perfectly that time

thanks, I'll give it another run when I get a chance.

I just flew mission 3, successfully destroyed the popup SA6 and SA8, and the three fixed SAMs (SA2x2 and SA3) as verified in the mission summary and Tacview, but the strike got turned around due to active SAMs still in the cooridor, and my score was 90. Looking at the Scoring Guide, I believe that means I got all points except the Strike Go Ahead.... so what am I missing? Is there a 6th SAM that I didn't locate?

This was resolved in 2.9.14.8222. Thank you!

There's considerable number of ways to get keystrokes and axes inputs from MIDI devices. I think one of the more useful is the midi2vjoy python scripts which pass button pushes and axes values onto vJoy (BrunnerInnovation build for Windows 11). Of the numerous midi2vjoy scripts, I found midi2vjoy-again (by luppahannu) to be the most useful due the numerous options that can be configured.

Good info, thanks. It is my understanding that the mission LUA console is locked down in public releases. Is there another way to access the mission environment besides simply placing the LUA code in a mission editor trigger?