AOCS not working on user missions

[Adam]

Hi,

 

I'm trying to get AOCS to work on missions. I have the radio tuned to 71.000 (by using the command "SELECT CRYSTAL PALACE") successfully.

 

But when I do additional commands for briefing or status, even though they're recognize in Voiceattack, I get no response.

 

The log I have is:

 

11:39:41.818 TX2 | COMM2: ARC-210: [ AOCS ] , [ Read Mission Briefing ]

11:39:41.788 Recognized : 'briefing' (Confidence 95)

11:39:40.484 (awaiting additional input)

11:39:40.459 Recognized : 'crystal palace' (Confidence 94)

11:39:37.840 Listening resumed

11:39:37.793 Joystick : 'Transmit TX2 press'

11:39:36.996 Listening suspended

11:39:36.928 Joystick : 'Transmit TX2 release'

11:39:36.803 TX2 | COMM2: ARC-210: [ AOCS ] , [ Select Recipient ]

I'm getting the feedback beeps, and chatter audio fine.

 

I've noticed that This works if I choose "Instant Action-Ready on the ramp". However if I choose a user created mission it fails.

 

I tried setting AOCS in MP (even though I'm running this as a single player mission)

 

I created a simple test mission (attached) that it fails on.

 

(I have also tried deleting the VoiceAttack\Apps\ViacomPro Config and Database folders and re-applying my license and configurations with no success.

 

On the PTT page, it shows my unit (FA/18 Hornet)

Temp.miz

[hornblower793]

Hi,

 

I'm trying to get AOCS to work on missions. I have the radio tuned to 71.000 (by using the command "SELECT CRYSTAL PALACE") successfully.

 

But when I do additional commands for briefing or status, even though they're recognize in Voiceattack, I get no response.

 

The log I have is:

 

11:39:41.818 TX2 | COMM2: ARC-210: [ AOCS ] , [ Read Mission Briefing ]

11:39:41.788 Recognized : 'briefing' (Confidence 95)

11:39:40.484 (awaiting additional input)

11:39:40.459 Recognized : 'crystal palace' (Confidence 94)

11:39:37.840 Listening resumed

11:39:37.793 Joystick : 'Transmit TX2 press'

11:39:36.996 Listening suspended

11:39:36.928 Joystick : 'Transmit TX2 release'

11:39:36.803 TX2 | COMM2: ARC-210: [ AOCS ] , [ Select Recipient ]

I'm getting the feedback beeps, and chatter audio fine.

 

I've noticed that This works if I choose "Instant Action-Ready on the ramp". However if I choose a user created mission it fails.

 

I tried setting AOCS in MP (even though I'm running this as a single player mission)

 

I created a simple test mission (attached) that it fails on.

 

(I have also tried deleting the VoiceAttack\Apps\ViacomPro Config and Database folders and re-applying my license and configurations with no success.

 

On the PTT page, it shows my unit (FA/18 Hornet)

 

I may be able to have a look at this later (dependent on a new PC having arrived for my son) but have had it running happily on missions I have created in the past.

 

As a thought, do you have a briefing included in the mission you have created (I am away from PC so cannot open the miz file)

 

Sent from my SM-T835 using Tapatalk

[Hollywood_315]

The Hornet radio requires manual modulation selection, confirm it is not set to FM.

Also 071.000 MHz is out of range for some radios, try tuning to 142.000 MHz instead and then call AOCS.

 

Sent from my SM-G960F using Tapatalk

[hornblower793]

The Hornet radio requires manual modulation selection, confirm it is not set to FM.

Also 071.000 MHz is out of range for some radios, try tuning to 142.000 MHz instead and then call AOCS.

 

Sent from my SM-G960F using Tapatalk

@Adam - I think @Hollywood_315 has it (as the master). Try manually tuning the radio to 071.000 using the UFC and I don't think it goes this low. I cannot remember as I have not been flying the Hornet recently

 

Sent from my SM-T835 using Tapatalk

[Adam]

Thanks! I think that is it. I did use the 'Select Crystal Palace' voice command prior which automatically chose 71.00 but I had a test last night and manually selecting 142.000 instead got past the problem.

 

Just wondering should VIACOM be trying to select frequencies automatically that aren't available? (ie, is this a bug that may be corrected in the future), or 'working as designed'?

 

Thanks again!