Highwayman-Ed

Covered in other reports, but this is a relatively new issue that was introduced in DCS for 'Other AI flights' to follow you are being ignored in CASE II / III conditions. We've submitted the issue to ED and await further information about a fix.

Just finish refuelling yourself and head back to the Carrier, the AI following you and heading back to the carrier will not impact your score.

The refuelling issues for both missions should be fixed as of the last update we submitted to ED. Unfortunately, the DCS update introduced a new issue with CASE II / III weather with Mission 2.

We've recently identified an issue to do with the weather that was introduced in a DCS update in the past month. Thus far it seems that the follow commands that we use in the mission will not function as expected if the conditions are CASE II or higher, and when the command to follow is issued, such as after completing the refuel and breaking off for the exercise, the AI wingman will fly back to the carrier and orbit instead of carrying out his specified actions. We've logged this this with ED for investigation, but have no timeline on a fix I'm afraid.

Thanks for the report. I've logged this for the team to take a look at.

This has been identified and linked to a recent change to the F-16's Datalink in the recent DCS patches that caused the problem. Although we have identified the issue and the fix for it, the mission is still largely unplayable for the time being due to the Audio issues. We're awaiting information from ED on the timing of being able to disable the new radio implementation to resolve this.

Thanks for the report, we’ve seen the AI behave strangely when they get low and sometimes the AI just goes dumb. if you can repeat the problem, let us know. The voice line loops were most likely a result of the AI hitting the water and it getting stuck in a loop waiting for it to get into the area where the fight will resume.

To back up what BD has said here, we've tried and failed to utilize this method many times in the past with the pending radio changes coming. This issue comes down once again to the AI and the way it interprets multiple nested Advanced actions used as AI push tasks. To put it as simply as I can, the more actions you have in the list, the more likely it is for the Ai to just give up and go home, and god forbid you to try to edit that list and remove an action or add one into the flow because something needs to be updated or tweaked, you effectively have to rebuild that entire AI unit and all of its actions again from scratch and then all of the associated triggers. This is why we chose to keep the comms separate from the actual AI tasks, such as follow, engage, weapons safe, etc.

Something else to check here, we (DCS Players) often don't class VAICOM as a mod, but it does impact how DCS functions to some extent. During some recent testing, we found that players who used the OLD official version of VAICOM in the past, even though they are not using the program any longer were able to resolve their issues by removing this old version of VAICOM, backing up, and then removing their scripts folder in their DCS Saved Games folder, then performing a DCS repair. The new community version of VAICOM does not seem to be causing issues at this point, but I know the migration from the OLD version to the COMMUNITY version has caused issues for some players in the past. Not sure if this applies for you, but it's worth checking!

Another issue we're facing with the recent changes to how the radios work in DCS as well I'm afraid. Due to the complexity in the way that AI Tasks work and how a simple change to the order of those tasks can cause the entire thing to need to be re-built from scratch, we use hidden objects around the map to do the transmissions instead, and up until these radio changes, that worked fine. Now we have to account for the distance from that unit to you, so if you're too far away, or have an obstacle in the way the radio messages can get impaired... We're working on these as we identify them, but as you can imagine, there are a LOT of radio transmissions going on! The preset issue has been fixed and submitted to ED with the next patch release schedule, but for now, you can just set the manual frequency of the middle UHF radio to 251 and it will resolve the problem of not hearing the initial comms.

Confirmed that this is related to us assigning presets to the radios. The default aircraft frequency for the aircraft radio and Comm 1 (ARC-210 in the A-10C II) are bound. We’re currently investigating if this is meant to be bound, but for now you can manually tune the ARC-210 to 251MHz and you will hear the missing radio transmissions.

Thanks for this report, we've identified a naming error on the Miz file that should be loaded when you chose to load ALT A or ALT B. This has been corrected internally. You can try to make a copy of and rename the mission in your DCS World OpenBeta\Mods\campaigns\FA-18C Raven One folder from "R1 M03 ALT A.miz" to "R1 M03 v2 ALT A.miz"

Thanks for the report, I’ll log it for investigation.

We have been able to find a workaround that was added in the previous Open Beta update (mid November). Biff should now land and taxi correctly to Thunder.

Mission 1 was updated in the last OB release and Biff should now land and taxi correctly back to Thunder.