Single ship missions RIO tunes wrong presets until takeoff

[eLgargantuan]

I noticed it in the initial mission(s) with Paco in the backseat and also in mission 9 departing Nellis: It seems that when ready to taxi the RIO tunes presents one behind the radio they should be on. In the front seat I tune preset 2 for clearance while the RIO is still on preset 1. Then the RIO increments to preset 2, I need to tune preset 3 to hear the "ground" taxi request/clearance. Same for tower on preset 4. If the front seat doesn't tune the correct frequency you won't hear the audio/clearances from ATC.

I think this is a bug because I was given the impression that the front seat didn't need to tune anything and leave it on preset 1 for the tactical frequency. Not sure if this is a DCS AI limitation but wanted to report it if it wasn't yet.

Loving the campain and how humbling it is!

This was no issue for me when doing 2-ship and 4-ship flights, the RIO tuned correctly on those.

[Reflected]

It is a bug but it’s on your end, it works fine here and apparently for others too.  Try running a repair and remove all unofficial mods you have. 
 

or maybe you use some sort of voice attack that messes with the rio scripts. I’m just shooting in the dark here but your dcs install must be corrupted one way or the other, hard to figure out why. 
 

try again using the ‘autostart’ cheat key and see if it works then.  Maybe you do something very unusual during startup that messes with the triggers?

Edited May 20, 2023 by Reflected

[eLgargantuan]

All of that is possible, if it's not reproducing for others then I'm happy to call it my own issue and close this one.

I don't think the voice attack would be doing anything differently when I am a single ship vs 2-ship or 4-ship. The same goes for my start up procedure, which is as close to "by the book" as I can get when referencing the NATOPS (doing the tests, checking hydraulics, etc). its odd to me that it only happens on the missions when i am single ship.

Also the voice attack should only key up when I select the mic to unmute it, otherwise it shouldn't be accepting any input/commands. Generally I just use the "Jester, start up" and then nothing until "ready to taxi". In this campaign specifically, since the "RIO" handles most of the setup/switching back there, I don't really need to use it at all and it typically just sits waiting for command input (when I push the button for it to listen).

[Reflected]

What if you use the auto start cheat key? Does it happen then?

[Reflected]

OK, I checked, JEster is told to go button 2 3 sec after you turn on the HUD. I tested it twice and both times it worked as advertised.

[eLgargantuan]

On 5/31/2023 at 7:09 PM, Reflected said:

OK, I checked, JEster is told to go button 2 3 sec after you turn on the HUD. I tested it twice and both times it worked as advertised.

Interesting... I've been turning on the HUD immediately after connecting ground power+air, before telling jester to begin start up. Do you turn on the HUD at a different point?

[Reflected]

Yes, after the engines are online.