Pyrocumulous

I've been learning the AV8B this weekend, so this may totally not be new behavior, but it's different than I'm used to with the Hornet. I can connect, and I can stay connected, but it seems like the probe has to remain perfectly aligned or else the probe passes right through the basket. The first time it happened, I held in formation for several minutes wondering why refueling wasn't complete when I glanced over to see that the probe was half in the basket. So, not sure it's a bug, but doesn't look right to me. Difficult for me to fly and capture a good screenshot, and the track log is worthless because the aircraft don't align the same in replay. Edit: this is apparently a long-term issue since 2018 that is listed as resolved but it's not (or potentially has re-emerged): Here's a photo of the probe slipping out of basket: av8b-ara-basketslip.trk

Training mission 1 incorrectly indicates that the radio channel selector knobs are volume control. A different error is made in the manual on Page 283, which labels the keypad as the volume control, but the knobs are correctly labeled on page 481.

Here are a couple of kneeboards that I built for Operation Cerberus North that might be of use to someone else. These helped me nail Eagle and Falcon approach every time while avoiding restricted airspace. Also helpful for orientation as you move around Syria, or potentially need to stop for gas on the way home. Put them in ..\Saved Games\DCS.openbeta\Kneeboard\FA-18C_hornet

Fantastic campaign, thank you for your work. Nice level of complexity of scripting, yet it actually works consistently despite the ever evolving codebase. Most of all, appreciate the ability to take mission on using your own strategy, particularly 7 and 15-16. Definitely a stretch for me to be able to completed 16 at 100%, but eventually got it, good thing there are checkpoints between the parts! The only two critiques that I have is that there isn't a good way to coordinate unplanned refuel with the remainder of your flight, so that always goes badly if you remain on-station too long and need to hit up Texaco on the way home. #2 is that I'd prefer to see the radio channel plan stay consistent throughout the campaign, where possible. Now, to learn AV8B for Hormuz Freedom...

After completing the primary objective of Mission 16, the onscreen message instructs: "Both primary targets have been destroyed, engage any further targets if you wish. When ready to depart contact Sentinel using the F10 menu." This matches up with the mission briefing "Once we have hit the primary target our secondary objective is to attack any SAA targets of opportunity within the FMA or the wider designated free fire area." Assuming the player does that, they call Sentinel once they are winchester and ready to depart, whom responds "SENTINEL: Devil 1-2 can you complete secondary tasking?" Being winchester, the player has to decline the tasking and loses the 10 points without credit for following the instructions and destroying additional ground targets. Not a big deal, just seems odd to wait until the player is done free-lancing additional targets in the free fire area to assign additional taskings.

Sort of a sub-option of #1,

Here's a hotstart mission and very short track showing it. Incirlik at sunrise (about 05:57 in mid-August). Incirlik_sunrise.miz Incirlik_sunrise.trk

I was under the impression that the Open Beta list was always before the Stable, but looking further down the list, I am incorrect.

Appears that there is an error in the Changelog, it's showing both the "small fix patch" on May 4th and a giant one on May 5th, both numbered 2.8.4.39731. It appears that it's a Stable entry listed with Open Beta.

This might be an old bug, but I don't recall seeing it before, so apologies if so. Sun is rising in front of (some) terrain, or perhaps shining through terrain. In screenshot below, you can see a hill in front of sun, and then mountains behind. This is with 2.8.4.39731 Open Beta MT in Syria.

Any hints on the proper altitude to fly Gold Corridor and avoid breaking the altitude block? I've tried BALT set at 27.5k and 30.0 and both times got the "We're outside our altitude block" warning. Screenshot below shows me at barometric 30020 (BALT set at 30000, but it doesn't hold super tight to that) and Devil 1-1 at 30.5k. Answered my own question: fly Gold at 29,500' and everyone is happy. For whatever reason, Devil 1-1 flies at 30,000' (according to barometric altitude flying in formation) but it's reported in SA page as 30.5, but you can't follow him at co-altitude.

@Shibbyland These are Steam prices, but they are generally the same as direct from ED: https://isthereanydeal.com/game/dcsmosquitofbvi/history/

I'm finding that 2-3 Tornadoes get hit by manpads every time on this one. Even if I load up with 8 GBU-38s and take out every single SAM and AA site that I can find, Action just gets annihilated. Taking out the drone, the two MiG-29s, most of the anti-aircraft, and then landing at Incirlik with 1000 pounds of fuel seems to be good for results of about 85. Feel like telling Action to use a bit more flares, less burners, more altitude, or something. I swear!

Totally nitpicky, and I only mention it because I'm really loving this campaign... but would be nice if the radio channel plan was static from mission-to-mission, matching what is shown in the Player Guide (page 3). I'm not a real Hornet pilot, so I don't know what is realistic, but I assume like civilian aviation, you generally leave your radio banks relatively static rather than reorganizing channels every day. With 20 channels available in the primary radio, I suspect that a static plan is possible. As an example, Noble 4-1 is channel 12 in the Player Guide, and channel 3 in Mission 5. I'm not asking for a any changes to Cerberus North, just making a suggestion for future campaigns. Thanks for the fun, looking forward to flying Kerman next!

Do you still need a track? HSEL has been flaky for quite awhile now, at least a couple of months. Sometimes it will hold a heading, sometimes it won't. Seems to be most consistently bad at capturing and holding the bearing if it's close to your original track. For example, if you are headed 083 degrees and you set heading to 085 degrees. Going from, say, 050 to 085 seems to work much more reliably. Was just checking on the status of this bug as I had the TACON-freeze bug occur when flying approach into Incirlik just now, and couldn't get the jet to hold a heading while I manually entered the lat/long.

2.8.3.38090 Open Beta MT same error message every time a target is destroyed in each of the missions that I've attempted. By "target" I mean primary target, you can destroy other bandits, SAM sites, etc without triggering it. Deleting the DCS folder in %TEMP% did not remedy. Would like to play this campaign, the concept is solid, but having to bail out of VR to close errors is getting old, real quick.

Correct, but both Sword 21 and 22 shows as SD21.

Looking back at screenshots, it appears that I was on Strike and Texaco at the time, so that explains how I missed that conversation. It's too bad the player doesn't hear just their own transmission (that never gets heard outside of the cockpit) as a queue that they are on the wrong channel.

I purchased the Hornet and Super Carrier modules specifically to fly the two Raven One campaigns in order(Dominant Fury followed by Raven One), and these two made that well worth it, even if I was never going to fly the module again. These are not beginner campaigns, you really need to be proficient in flying the Hornet, utilizing the radar, navigation, and weapon systems, and able to maintain your spatial awareness. Both campaigns are truly works of art. Not sure how Baltic is able to keep these missions working over 95% as intended with the constantly changing DCS code, but it's impressive, and clearly takes time and devotion to maintain. It's one thing to create an amazing set of missions with complex triggers that works on a single version, it's another to keep it working as the underlying canvas is in constant flux. Probably foolish, but amazing, none the less! The briefing terminology can be daunting, and understanding the codewords in real-time radio traffic is challenging. Realistic, but the pause button is a blessing for such occasions! There are a few minor errors in the kneeboards / briefs, but nothing game breaking by any stretch. Only complaint would be that datalink is only partially working, for no apparent reason some friendly aircraft just don't show on the SA page (and show as ambiguous when you get a radar hit), and others do. Looking through the mission files, I certainly can't figure it out, but it's really odd. Just means that you need to be even better with the radar and extra careful that your target is actually a hostile. I don't recall any air-to-air refueling that you absolutely couldn't skip, but these are actually relatively simple due to the reasonable airspeeds (300 knots is typical) flown. Of course, having wake turbulence turned on brings the stress back, particularly as your remaining fuel drops below 2000 pounds. Thank you for the experience!

Anvil 12, 13, 14 start up but remain on deck until an hour into the mission if the player uses Cat 3. They launch as programmed if the player launches from Cat 1. I believe the event that is triggering them to launch (when I used Cat 3) is Thor calling bogey picture. Ran this a few times in both MT and ST modes, results appear to be the consistent. Even so, the mission still works, the additional Anvil targets get hit about 35 minutes late, so about when the player has completed refueling. 2.8.3.38090 Open Beta. RavenOne14.log Tacview-20230402-172502-DCS-R1 M14.zip.acmi

Mission 13 works great, but just a heads-up that both Sword 21 and 22 are using "Springfield 2-1" as their callsign, so they both show as SD21 on the SA page and JHMCS.

Does a result of 90 on M13 mean I got everything, or missed something? Maybe I'm getting docked for taking a BVR shot at one of the MiG-29s when I was supposed to have the ATFLIR focused on Sapphire? ( 2.8.3.38090 Beta MT)

This was a fun one, reminds me of WW2 bomber intercepts over the Channel. Thanks!

I suspect this is just a one-off DCS issue, and not tied to this mission. I just mention in case it's a trend others are seeing. When I came back to mother, Cat 3 jet blast deflector was up. Radio communication was all normal and did not indicate that the deck was fouled. Approached three times with no change, so I just angled it in there. Not recommended in real life!

The coordinates on the kneeboard for P35? How can >60 seconds be fine? It's not possible. The coordinates that are pre-loaded into the GPS as waypoint 3 are valid.