AI Wingman Callouts

[Bagpipe]

Ok....JEEEEEEZO does this need addressed!

 

Setting: Just loaded up the F16 Persian Gulf cold and dark quick start mission into the editor, assigned myself a wingman, changed to night time and plopped two 2-ship F14A flights on the Iranian side to keep the screens interesting.

 

Not two minutes in the air and my wingman is perpetually spamming the "2, contact at xx for xx" chatter.

 

I mean seriously, this really grinds.

 

Is it in the pipeline ED? Please say something reassuring! :helpsmilie::helpsmilie:

[stormrider]

It is possible to set the option in the mission editor to restrict the kind of contacts that they will report, although it seems to be at least slightly bugged.

 

 

First, you set this option for the waypoint, it's not automatically applied like every other setting, but you need to re-open this option so it applies, that means, you click add > set option > report contacts > select/deselect checkboxes. Then you close this dialog but the changes are not applied until you double click to open it again.

 

 

Second, you set for example:

Report contacts > Only air;

Report engagements > Only air;

Report kills > Only air;

 

 

and as soon the your wingmen start their attack runs, they will reset back and start calling all the ground targets as if nothing was setup.

[Bagpipe]

It is possible to set the option in the mission editor to restrict the kind of contacts that they will report, although it seems to be at least slightly bugged.

 

 

First, you set this option for the waypoint, it's not automatically applied like every other setting, but you need to re-open this option so it applies, that means, you click add > set option > report contacts > select/deselect checkboxes. Then you close this dialog but the changes are not applied until you double click to open it again.

 

 

Second, you set for example:

Report contacts > Only air;

Report engagements > Only air;

Report kills > Only air;

 

 

and as soon the your wingmen start their attack runs, they will reset back and start calling all the ground targets as if nothing was setup.

 

Thanks fir the info man.

 

Their were only at most 4 air contacts in the entire mission yet the Ai was just spamming out the same contact whenever it changed its BRA by one degree or more.

 

I just muted the radio after a while but its not really a solution to the issue

[RedeyeStorm]

That is why I immediatly order my wingmen to shut their radars off. That only leaves the mud calls.

[Bagpipe]

That is why I immediatly order my wingmen to shut their radars off. That only leaves the mud calls.

 

Can you bind the commands radar on/off to a key? That would help

[Oceandar]

Ok....JEEEEEEZO does this need addressed!

 

 

 

Setting: Just loaded up the F16 Persian Gulf cold and dark quick start mission into the editor, assigned myself a wingman, changed to night time and plopped two 2-ship F14A flights on the Iranian side to keep the screens interesting.

 

 

 

Not two minutes in the air and my wingman is perpetually spamming the "2, contact at xx for xx" chatter.

 

 

 

I mean seriously, this really grinds.

 

 

 

Is it in the pipeline ED? Please say something reassuring! :helpsmilie::helpsmilie:

Lol, same. I've been playing DCE for F-16 and the wingman kept spamming me obvious contact until I switched the radio freq and switched back before enggagement.

 

I agree this need to be addressed for SP gameplay convinient.

[Harker]

It is possible to set the option in the mission editor to restrict the kind of contacts that they will report, although it seems to be at least slightly bugged.

 

 

First, you set this option for the waypoint, it's not automatically applied like every other setting, but you need to re-open this option so it applies, that means, you click add > set option > report contacts > select/deselect checkboxes. Then you close this dialog but the changes are not applied until you double click to open it again.

 

 

Second, you set for example:

Report contacts > Only air;

Report engagements > Only air;

Report kills > Only air;

 

 

and as soon the your wingmen start their attack runs, they will reset back and start calling all the ground targets as if nothing was setup.

This hasn't been working for me lately. Wingmen and sometimes other AI flights ignore that setting and spam the radio anyway.

 

I usually use:

Report contact > OFF

Report when engage > Air (& SAM)

Report when kill > Air (& SAM)

 

They'll still call out air or ground contacts.

 

Is it working OK for you, in the latest OB?

[stormrider]

This hasn't been working for me lately. Wingmen and sometimes other AI flights ignore that setting and spam the radio anyway.

 

I usually use:

Report contact > OFF

Report when engage > Air (& SAM)

Report when kill > Air (& SAM)

 

They'll still call out air or ground contacts.

 

Is it working OK for you, in the latest OB?

 

 

Its not working for me either.

[Harker]

Its not working for me either.

Thanks, at least I know it's not me.

[Taz1004]

You can disable contact callouts only by editing lua file.

 

Scripts\Speech\common.lua

 

Line 1414

[base.Message.wMsgWingmenContact] = WingmanContactHandler,

 

Change to

[base.Message.wMsgWingmenContact] = '',

 

 

Well, you can disable other callouts in that same list using same method.

[Bagpipe]

I don't want to/shouldn't have to delete/edit anything. I just don't think they should be spamming the same contact repeatedly.

 

Thanks

[norman99]

Any word from ED about this issue at all?

 

My wingman constantly calling contacts 200nm away (I don't even know how he's seeing them in the first place?), for over 40 min, just kills the single player experience completely.

 

Track attached, so someone can investigate further.

Track.trk

Edited March 24, 2021 by norman99

[BIGNEWY]

On 3/24/2021 at 4:02 AM, norman99 said:

Any word from ED about this issue at all?

 

My wingman constantly calling contacts 200nm away (I don't even know how he's seeing them in the first place?), for over 40 min, just kills the single player experience completely.

 

Track attached, so someone can investigate further.

Track.trk 3.13 MB · 0 downloads

 

 

Thanks for the track, there seems to be a scripting issue with it when I try to replay it?

 

AI radio use can be adjusted in the editor when creating the mission. If anyone has a short track replay showing this not working please attach it

 

thanks

[norman99]

On 3/29/2021 at 10:03 PM, BIGNEWY said:

AI radio use can be adjusted in the editor when creating the mission.

Which function should I be looking for in the ME, to try and improve this?

 

The missions I’m flying are part of MBots’s Dynamic Campaign, so I’m not sure exactly how they’re constructed, but I’d be happy to modify them slightly if it can fix this issue.

[norman99]

I’ve found the relevant functions in the ME, but as mentioned further above, it’s not really a fix, just a bandaid. I still want to ‘relevant’ calls to be made. A contact all 200nm away is not relevant. Nor is the same call every second because the contact changes position by a fraction. It shouldn’t be all or nothing.

 

Calls should be within normal radar identification range, and only one call per group. If the group ‘disappears’ maybe a realistic timer is started so it’s not immediately call again for a short ‘drop’. Maybe 30sec, or 1 min? Just something that keeps unnecessary calls to a minimum, but still provides tactical value.

[84-Simba]

More importantly, wingman will not aknowledge nor follow order when he is on it's calling spree.

You'll have to wait he's finished and then give him orders.

[Noctrach]

On 4/24/2021 at 1:02 PM, RoxSy said:

More importantly, wingman will not aknowledge nor follow order when he is on it's calling spree.

You'll have to wait he's finished and then give him orders.

Yep, this issue actually low-key breaks some campaign missions because you cannot order your wingman to do anything anymore.

This needs to be solved, its not a "scripting problem", this is an AI bug. They just get stuck in a loop calling out the same contacts perpetually and become useless and unresponsive for the rest of the mission.

[Bagpipe]

On 3/29/2021 at 3:03 PM, BIGNEWY said:

 

Thanks for the track, there seems to be a scripting issue with it when I try to replay it?

 

AI radio use can be adjusted in the editor when creating the mission. If anyone has a short track replay showing this not working please attach it

 

thanks

 

On 4/2/2021 at 5:26 PM, norman99 said:

I’ve found the relevant functions in the ME, but as mentioned further above, it’s not really a fix, just a bandaid. I still want to ‘relevant’ calls to be made. A contact all 200nm away is not relevant. Nor is the same call every second because the contact changes position by a fraction. It shouldn’t be all or nothing.

 

Calls should be within normal radar identification range, and only one call per group. If the group ‘disappears’ maybe a realistic timer is started so it’s not immediately call again for a short ‘drop’. Maybe 30sec, or 1 min? Just something that keeps unnecessary calls to a minimum, but still provides tactical value.

 

I agree that this has been an issue for a very long time and sometimes it is out with some users scope of ability or willingness to have to edit a mission in the editor to stop the perpetual wingman callouts. Something needs to be hard coded into the sim to allow it to decide when is appropriate to call out I guess.

[Taz1004]

You can try this until it is fixed.

 

 

[Bagpipe]

17 hours ago, Taz1004 said:

You can try this until it is fixed.

 

 

Excellent Taz. You really are a handy guy!

If i disable bra calls does the awacs still respond to bogey dope requests?

[Taz1004]

6 hours ago, Bagpipe said:

Excellent Taz. You really are a handy guy!

If i disable bra calls does the awacs still respond to bogey dope requests?

 

There's two BRA callouts.  Line 454 and Line 455.  I believe 455 (VectorToNearestBandit) is the request but I haven't tested.

[Realizm]

I'm having the same issue with the current build as of the time of this post. I'm flying two F-18C's in Syria with the new Cypress addition, and the wingman will not stop calling out contacts 180nm away. I told him to return home, he didn't respond, kept spamming. Finally I turned off com 1 and tuned com 2 to awacs. Super annoying. Anyone else having the same issue? The wingman was non-stop calling out contacts second after second even after 30 minutes.

 

[jross194]

Yes, it there as of today 9/91/21. My mission(s) are setup such that ground targets activate on a trigger. As soon as they activate it's non-stop "Contact XXX for YYY", 100+ miles in this case (a truck on the ground - he's go good eyes). I re-wrote such that they don't activate until I'm within 40 miles but same. Maybe it's related to Late Activation? Been this way for some time and is a real issue for us single player players. Does it every time.

 

F-18 flight FWIW, in Syria. 

[norman99]

I’d just like to reiterate that more than 18 months after the OP, this is till a huge problem, especially for those who predominantly fly SP. Not only is it immensely annoying, it basically makes make any control over your wingmen impossible, as you simply can’t get a word in until they’ve finished.

I know AI/comms is getting improved, we’ve been told that for years, but at what point will we start to see some actual progress?

(User edits to .lua files should not be considered a viable solution by the ED devs.)

[Flappie]

7 hours ago, norman99 said:

I’d just like to reiterate that more than 18 months after the OP, this is till a huge problem, especially for those who predominantly fly SP. Not only is it immensely annoying, it basically makes make any control over your wingmen impossible, as you simply can’t get a word in until they’ve finished.

I know AI/comms is getting improved, we’ve been told that for years, but at what point will we start to see some actual progress?

(User edits to .lua files should not be considered a viable solution by the ED devs.)

BIGNEWY told you he could not replay the track you attached last year. I've just tried it, and it doens't work for me either.

Can you please attach a new track showing the issue(s)?