Pyrocumulous

I just completed 15 (entire thing, from launch to recovery), and thought the same thing. I assumed it was due to me having to reprogram channels due to the COM2 issues, and getting them confused. I have to fly it again because I was only awarded one point, although I have no idea what I didn't do, perhaps there was another key communication that I missed? This was with 2.8.3.38090 OB MT

I was able to get all of the F14s off the deck without fireworks by proceeding to the catapult and launching ASAP. That shouldn't matter, but I was a 0 for 6 when I waited for yellow shirt, and then 2 for 2 when I launched early. YMMV.

Thank you @Recoil16!

Was planning to create a fictional South Atlantic campaign around WW2 era, but would really want some historic VFR Sectionals to make that work. The only one I was able to locate is AAF Aeronautical Chart 1627 (Mt Piramide, Chile) from 1943. Any one know of a good source for a raster layer that would include Cape Horn? The AAF Aeronautical Chart index indicates 1668, 1669, and 1626 would complete that Tierra del Fuego / Falkland Islands set. Alternatively, I could stick to modern era, but I'm not finding much good to work with there either. Probably because I'm not looking in the proper place or using the right search terms. Alternatively, I could just re-assemble the dds files from the RasterCharts folder. Other ideas?

I didn't notice any difference between ATFLIR and F10 / Mission Editor (I have not looked at either). I am just noting that the map and coordinates for P35 in the briefing materials are incongruous. I find that I have to pay very close attention to what you write in the briefings!

From what marked with the ATFLIR, I believe P35 should be about: N 34° 01' 42.60", E 36° 05' 35.37" Waypoint 3 was pretty much right on P35.

@Sandman1330 I did set Rock, just took me too long to locate the correct aircraft and complete the intercept the first two tries. Shortly after firing warning shots I would run out of time and fail. Me not paying enough attention to flight direction combined with not being aggressive enough about chasing the aircraft down.

Haven't flown it yet, but the coordinates appear incorrect for P35's target in M08 briefing. The image and kneeboard read N34 01 70.95, E36 05 59.37. Clearly can't have more than 60 seconds, but even it's supposed to be Decimal Minutes, it should be between the latitude of P36 (N34 01 41.535) and P34 (N36 05 40.21). The longitude is real, but it should be between P33 (E36 05 26.84) and P36 (E36 05 38.47), but it's not.

Thanks, trying to find Marauder quickly enough to not fail the mission M05 without D/L is exposing my apparently subpar radar / rock-calls skills.

Is there really an IR sparkle in this mission or is it just headlights? I would think you'd be able to see that with the ATFLIR IR, but I can only see headlights, which are visible in ATFLIR TV and NVGs. Maybe it's a DCS 2.8.3.37556 MT issue? I didn't have too much trouble locking onto the moving vehicle, probably because I got him before the streetlights, but the parked one... not so easy! The darned mav locks onto all of those warm things around the target but not that one. I swear! I ended up getting my right horizontal stabilizer shot off getting close enough to the parked target. That became abundantly clear upon engaging flaps while attempting recovery to the Abe. I was pretty stoked to find that I was given a mission success after diverting to Ras Al Khaimah for repairs and then recovering to the Abe. Thanks for the great campaign, looking forward to see where we go next!

Fantastic! God bless the team! I'm running overpowered hardware, but damn, every graphical sparkle maxed out and I'm pegged at the 90fps that my Reverb G2 can handle. The smoothness of seeing aircraft fly by is so realistic now. Interesting inspecting the single vs multithreaded core utilization. On the MT version, actually get far higher single thread utilization, and the GPU can just goooooooo. OpenXR is reporting around 15% headroom on Turbo Mode (meaning the CPU is staying ahead of the GPU), which it never had before.

The initial coordinates from Strike are: N 25 42 83, E 57 48 34 The format of the on screen text and the way it's spoken (as well as the format used in preceding missions) leads me to believe this is supposed to be in DMS format (N 25° 42' 83", E 57° 48' 34"), but 83 seconds is impossible. N 25° 42.83', E 57° 48.34' does appear to be a reasonable location, so I'm headed there now to look for Moon Beam.

This was a really fun mission, I always love these low level ingress missions in topography! Voice Attack or throttle bindings are critical to staying on top of waypoint management while staying heads-up and spatially aware. Tacview-20230226-125558-DCS-ROPL2 M9 PART 2 RUMBLE WITH A GRUMBLE.zip.acmi

Somewhat related, the initial BRAA for the Fulcrums is "Bulls 0-8-0" when I believe it should be "Bulls 0-0-8".

Just completed this mission (fun as always!), and never did get an "all clear." After the MiGs disappeared from my radar, I circled around until I got an RWR hit that lead me toward Senaki, but then that too disappeared. Eventually I just went back to mother and got the fireworks show (although, strangely enough, never got the ability to call Hornet Ball?). No issue staying well in front of the MiGs, most likely because I was already at 28k' going M0.77 back toward mother when they spawned. Reviewing the Tacview (attached), the two surviving MiGs flew over Kuaisi and landed at Senaki. Not sure if that was the intent, but those are some lucky pilots! Now that I'm caught up on the story, headed back to the Straits of Hormuz for RotPL2. Thanks for your work! Tacview-20230219-130801-DCS-Mission 10 Camp 2 SC.zip.acmi

That's unfortunate, thinking I was clever, I've been attempting to draw the SAMs toward me to so they'd ignore my JSOWs... with zero success

operator error then... hmmm... thanks for checking! Fun mission BTW.

I doubt this is a mission bug, but three times I flew this mission and all three times found that the ICLS glideslope beam bar put me way low / behind the carrier. Third time I just eye-balled it and managed to grab a wire, but it's weird none the less. Verified TACAN is set to 75X, and ILS to 1. Anything else I could mess up? Super Carrier "normal" campaign version (Mission 3 Camp 2 SC.miz) DCS 2.8.2.35759 Open Beta

420 runs away in Mission 13 when the Abu Choppers 1 group appear, and then a "new" 420 generates (Ford 4202) when Abu Choppers 410 group appears. It's actually a pretty clever way to force the player to engage group 1, while the wingman takes the 2nd group. The refueling collisions seems to happen when the AI thinks you are done refueling, and since I'm terrible at refueling and spend lots of time dancing with the basket, that's not super obvious. If I just get in there touch the basket once, claim refueling is done via F10, and fly away there is never a collision. The solution is clearly for me to learn fly more precisely rather than ED creating a more idiot proof AI.

Mission 15 was great, huge sigh of relief once I made it safely back on the carrier. Quite the impressive firework show in this one, thank you for a great campaign! Looking forward to part two! The scripting you've done is amazing, really making each AI entity play their role. There was one mission that I was really pissed when the Black Sharks showed up and Matrix ran for the hills! Looking at TacView afterward, it was obvious why you designed it that way. One minor issue (not with Mission 15, but common throughout), and I'm not sure how you would do it, but it would be nice if Ford 420 would depart tanking to the port side (or back out) rather than right into Ford 110. Probably not an issue for those with good, quick AAR skills, but I spend way too much time trying to get in the basket and stay there only to get hit by a freshly fueled Hornet.

Good catch, that is exactly what happened! Not sure how that switch got flipped, lesson learned to check the launch bar.

Here is a trackfile of Ground Crew "unable to comply" with remove wheel chocks command. Verified throttle was at zero. Tried all of the ground crew commands to get them motivated, but nothing other than shutting the aircraft down worked. This is in F/A18C on Super Carrier, freshly updated to 2.8.2.35632 Open Beta.wheelchocks.trk It worked several other times with everything identical, so not sure how to replicate.

The first time I ran Mission 9 (and apparently clipped the 24-mile ring that I didn't take as seriously as I should have!) Matrix launched the 4 JSOWs. The next time I ran it (successfully, despite the ACLS trying to run me into the drink), he just follows me without launching anything. Not sure what trigger I could have missed. The time he fired, I turned toward W3 a bit earlier (further south) than when he didn't fire. Doesn't really matter, and I wouldn't have noticed except for TacView since I only watched my own targets with the ATFLIR as I egresses. Really enjoyed this mission, made me wish I could throw my Viggen on the Abe! Tacview-20230122-222657-DCS-Persian 9 Early Morning Call.zip.acmi Tacview-20230122-213205-DCS-Persian 9 Early Morning Call.zip.acmi

If you install stable version 2.7.18.30765, you can play missions 6 & 8 on that, and the rest on the current Open Beta, copying the logbook.lua between the versions to save your progress: C:\Users\you_user_name\Saved Games\DCS\MissionEditor\logbook.lua C:\Users\you_user_name\Saved Games\DCS.openbeta\MissionEditor\logbook.lua or probably easier, roll back to 2.8.0.33006 Open Beta, from a command prompt run: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin>DCS_updater.exe update 2.8.0.33006@openbeta

After feeling like I had totally let Wave down three consecutive times, and flying ever closer formation.... I am so relieved to learn it's just DCS AI doing AI things. Thanks! Rolling back to 2.8.0.33006 Open Beta appears to resolve the issue for now. C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin>DCS_updater.exe update 2.8.0.33006@openbeta