Pyrocumulous

There's a track linked in the first post. I didn't conclusively link it to airspeed, but it did appear to resolve the issue.

I originally said that Chief is pretty useless in this mission, but then I tried activating Chief at the beginning of each new target assignment. That worked much better, and he actually ended up dropping 8 bombs on 6 targets and going winchester. Starting out with 10 LJDAMs + 2 Rockeyes, I ended up hauling 3 back to the FARP.

This was a phenomenal mission, really enjoyed (and frustrated with!) the terrain challenge in the second half of the mission. I actually now appreciate the rockeyes, absolutely the right tool for the job!

Upon further experimentation, I think the issue is low air speed at launch. Not sure if that's correct behavior or not, but it seems that the rockets do not track if fired below some air speed regardless of dive angle. Not sure what that air speed is, since I'm always in A/G mode, but it feels like it's somewhere around 300 knots.

I am experiencing that APKWS rockets will sometimes fail to track, which seems to happen after several rockets have been launched successfully, and then all subsequent rockets will fail to track. Attached is a track of this occurring. I have additional tracks showing the same thing if that is useful. Launching of rockets begins at 05:20.The TPOD worked to guide in 6 LJDAMs and then continued to work for the first rocket, before something stopped working. I tried cycling TPOD through standby, changing code and resetting, as well as using D&M or EYES mode. None of which remedied the problem. The track is flown with 1688 set as the APKWS code, but I had the same issue yesterday with 1777 code. It's almost like the APKWS code is changing mid-flight, but if it did, it was not indicated on the in-flight kneeboard. DCS 2.8.6.41363 Open Beta in MT mode with OpenXR Pilot error is always a possibility! (note: looking back, I have not noticed this behavior when I wasn't using GBU-54 LJDAMs; however, LJDAMS and APKWS are my favorite weapons in the AV-8B so it doesn't mean all that much) https://drive.google.com/drive/folders/1W54Zv5uXF02Qe40xVi9kZyBgAvDICJM5?usp=sharing

Comms are working for me in DCS 2.8.6.41363 Open Beta, although I have to toggle back and forth between Comm 1 and Comm 2 to get the communication menu to appear, but then I can switch to the proper radio once it's on the screen. So, working, but not as expected.

"fixed internally" means that it is incorporated in an unreleased build, and should be in the next Open Beta.

First, I really enjoyed flying Hormuz Freedom, thank you. Specifically on the radios, I appreciated the static channel plan throughout. Knowing that Comm2 channel 5 is always Focus is how it should be. Suggest adding Liwa, Al Dhafra, and the tankers to that channel plan, that said, entering additional frequencies on the fly is part of piloting. However, there are quite a few missions where the frequencies programmed in the radio at mission start do not match the starting message. It's not a big deal, as it got to be habit to plug in the frequencies before I even requested permission to start up. These are the channels that I noticed had issues as of DCS v2.8.6.41066.1: M1: freqs are all there, but not in the channels identified in the starting message M2: freqs are all there, but not in the channels identified in the starting message M3: freqs are all there, but not in the channels identified in the starting message M4: freqs are all there, but not in the channels identified in the starting message M5: freqs are all there, but not in the channels identified in the starting message M6: all good M7: all good M8: all good M9: all good M10: all good M11: all good M12: all good M13: Comm2 channels 4, 5, 11 M14: Comm2 channels 4, 5, 11 M15: Comm2 channels 4, 5, 11

You could simply revert back to a prior known working open beta version. From command prompt (in ..\Program Files\Eagle Dynamics\DCS World OpenBeta\bin), run: DCS_updater.exe update 2.8.4.39731@openbeta

The loadout for Mission 12 is invalid for: Uzi 1-1 on station 2 (3x Mk-82, incompatible with AIM-9M on station 1), and station 7 is empty (possibly intended) Uzi 1-2 on stations 2 (3x Mk-82, incompatible with AIM-9M on station 1) and 6 (3x GBU-12) Consequently, Uzi 1-1 (player) spawns with nothing on station 2, and Uzi 1-2 spawns with nothing on either station 2 or 6.

I think the issue is that I wasn't flying over Waypoint 7, instead calling into Siri and lining myself up with runway 30. Doing that, if I land and then taxi all the way to the end and then back to parking area, I got Results 100 (both times I tried it) despite only taking out a couple of SCUD TELs, possibly because I taxied all the way to the NW end of Siri runway. Is that possible?

I did get jumped by the bandits, but managed to get out alive with only a glancing missile strike. I did it with the mission loadout (with considerably less damage to the convoy) but wasn't passing, so I did again with 12 Mk-82 bombs and still no pass. I did manage to get a result of 100 by re-arming at Siri and going back to clean up the convoy on a second run. I wonder if I didn't reach the trigger zone when landing at Siri the first time? Regardless, this is a really fun mission. Clearly not the jet you would choose to be in when you get jumped by a bunch of fast interceptors equipped with radar!

I'm not sure what the victory conditions are for this one are, but I took out 12 vehicles with a ripple of 12 Mk82s, but only one of them was a SCUD launcher, and then both myself and wingman made it back to Siri for 50% result. Perhaps it's linked to the SCUD kills rather just survival and killings some random vehicles.

Attached is a quick demonstration of this bug: make call to ATC, while that conversation is occurring, make ground support call. This will break whichever radio was used for the duration of the mission. You will not be able to hear your transmission, nor the response, and nothing actually occurs (that is: it's not just missing audio). av8b-comm_break.trk

I have been seeing this as well. I often entirely lose Comm2, but can use Comm1 for the same frequencies. I believe I am able to trigger this failure by calling Ground Crew before radio traffic is complete. For example, requesting permission to Start Up and then immediately requesting ground crew to remove wheel chocks.

I believe that is exactly what happened. I took way long messing around with the CAS page and trying to see the IR marker before diving in. When I played it tonight, I took out 100% the enemy units on Farur Island, and the Sea Stallion set down next to the downed pilots but they never got on the ship. I remained on scene until bingo and then returned to Siri. Received a score of 110 and 100 result, so that's good but didn't actually accomplish the rescue. Comm2 didn't work for the entirety of the mission (this time only, very odd), so it's possible that I missed some instruction as I had to bounce around the frequencies entirely on Comm1. Tacview-20230601-213421-DCS-AV8_C1_M10.zip.acmi

I'm getting "Objective Complete. RTB" without even firing a round, just dove in and dropped a few flares. Headed back to Sirri, and shut down with a mission score of 0, but 100%. I'll try again tomorrow.

I can confirm that a very big boom is the product of hitting the targets.

Regarding the DPMI coordinates

The loadout for Uzi flight is not allowed (3 GBU-12s on station 2 and 6) and they spawn with nothing on these stations.

If you go in low (like 100 feet) you can avoid the MiGs, and then use APKWS rockets to take out the entire group of SCUDs, Shilkas, and trucks one-by-one staying below 1000 feet and the Hawk is not a factor. Recommend taking out the two Shilkas first, so there is no threat. 28 rockets shot in pairs, good for 14 shots. I ended up hauling a pair of GBU-12s and a full gunpod back to Siri. APKWS really are the best weapon ever for numerous targets without too much AA.

I flew it again, and noticed that codeword Irene actually gets called as soon as the flight is in the air, then codeword Fiona when near W2: Mission 5 has a similar discrepancy of frequencies and channels, but they are all in there so it's just a simple matter of getting the radio, in-game message, and briefing to match.

This is with DCS 2.8.5.40170 Open Beta. No complaints on load-out choice, good for me learning to get pushed to use something other than I would otherwise choose.

Briefing shows that Tarawa is on 330.0, which is correct, but in game prompt lists frequencies as Uzi flight: 305.000 Radio1 Button1 \ Focus AWACS/CIC: 251.000 Radio2 Button5\ Texaco: 256.000 Radio2 Button2\ Shell: 255.000 Radio2 Button4\ Tarawa: 305.00 Radio2 Button2 The radio is pre-programmed for 305.00 on Com1 channel 1, and Com2 channels 1 and 2, which is the Uzi flight rather than ATC for Tarawa. 330.0 is not programmed anywhere into the radio. Com2 channel 4 is correct. Com2 channel 3 is actually 256.0. Not a big deal, was able to reprogram the radio on the deck without too much trouble. Focus shouts Fiona a bunch of times when the strike occurs, and Uzi One clears the flight in hot despite never getting code word Irene. I continued holding at WP2, and couldn't get an "Irene" out of Focus. A shame that the loadout isn't APKWS HE, this is pretty much the perfect target for it.

I can confirm that the issue exists in 2.8.5.40170 Open Beta MT