Highwayman-Ed

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.

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 this is being looked into.

OK, this is a little bit of an oversight with the wording of the startup process. It took us much longer to diagnose than it should have because when you know how things are supposed to work, you make assumptions... Sorry! The way the mission should flow is that once the IFCC part is complete, you should complete your aircraft startup prior to contacting ground. THEN you should contact ground for clearance and start to taxi, and Biff will follow shortly afterward. The current wording of the messages is ambiguous and does indicate that you should press Space to let Biff know that you've started up and are about to contact ground, but isn't clear that this should be done only when you are ready to taxi. Updated the on-screen prompt. Thanks for the report

You are welcome to use any and all assets for this, I like the campaign idea to the training too

The keyboard diff was for the Gazelle only way back when I made the profiles back just after it was released. I have no real idea if it’s needed any longer. The zeros not iterating properly is something to do with the code of VA scripting. It’s something that plagued me for years with a zero value not working on and off in the back end of VA, and I grew tired of constantly coming up with new ways to fix it. This is the primary reason I’ve given them away for free now as I simply don’t have the patience to troubleshoot anymore. Sorry I can’t give you an answer with how to fix it, but it’s to do with the scripting that tracks the radio frequencies. I hope that leads you to the right location.

Great script, really like how portable you’ve made is and it was easy to add the elements into our existing missions.