investigating RTB and AI Wingmen

[MVS-Viper]

The AI wingmen do not return to base when given the RTB command.  Not a big deal right now, but if you are using the dynamic campaign - it does matter.  AI wingmen tend to get shot down or bail out before returning to base.  Each time they do that, the blue side of the campaign loses a jet unnecessarily.  This should be fixed before DCS rolls out their dynamic campaign engine.

 

 

[Flappie]

So far, we don't know:

• which aircraft you're talking about
• which terrain the action was taking place
• the position of the AI wingman (away from you, in formation?)
• the position of enemy SAMs
• the state of airfields (blue, red, or white - bombed or not)

My attached track shows my Su-25T wingman returning to base as soon as I ask him to. On my end, the RTB command seems to work fine.

 

Can you please attach a track showing an example of the issue you're describing?

Su-25T RTB OK.trk

[MVS-Viper]

Hi Flappie,

 

I'm talking about F-16's but it happens with the F-18's as well.

The Persian Gulf map.

In formation, we had just taken off. 

Enemy SAM's were far away.

Airfields were in good shape.  I had just taken off. 

I'll do a trak for you, but I've had this happen many times in the past with the F-16's and F-18's.

[MVS-Viper]

Here you go.  Trak file attached.  This one is in the Nevada map.

RTB Problem.trk

[Flappie]

Thanks. Your track was reather long, so I smply created a Viper mission over Nevada.

 

I concur about the Viper: an AI Viper wingman won't RTB when he's asked to.

However, I have no such problem with an AI Hornet wingman (short track attached).

Hornet_wingman_RTB_OK.trk Viper_wingman_RTB_NOT OK.trk

[MVS-Viper]

Thanks Flappie.  Yeah, sorry that mission was kind of long, but it took the wingman a long time to get airborne.  They are really dumb.  Lol, then I kept trying to send him home.  Thanks for checking on the Hornet, that was fixed - awesome.  Right now (on a dynamic campaign), you are better off telling the F-16 AI wing man to go home and save the plane.

 

Please see if you can fix the Viper's wingmen.  The AI is really dumb.  My wingie once crashed into me - while I was waiting to take off on the active.  I heard "two rolling" and then bang.

 

Thanks again.

[[ED]Ben]

Flappie -in your track, i am not seeing a blue base for him to RTB to?

[Flappie]

There is indeed no blue base in my two tracks above, but:

1. My Hornet wingman still RTB on any neutral airfield he can find (if you use my track, he will land at neutral North Vegas), and it goes the same for other non-Viper aircraft (F-5E track attached).
2. Right after I set North Vegas a blue airfield, I first saw my Viper wingman saying "OK" to my RTB order, then he landed at... neutral Groom Lake (unfortunately, I didn't save the track). Then on my following mission runs, my Viper wingman won't answer my RTB calls anymore (new F-16 track attached).

Viper_wingman_RTB_NO OK_with_blue_base .trk F-5E_wingman_RTB_OK_with_no_blue_base .trk

[[ED]Ben]

odd indeed

Can you replicate on Caucasus?

[Flappie]

OK, I know what's happening. All this time I was using " \ " (Main) to call my wingman. It seems he never answers orders passed through Main. Is it normal?

As soon as I use RAlt + \ (UHF Radio AN/ARC-164), my Viper wingman answers my calls, including RTBs.

 

This issue doesn't happen with the F-5E since it doesn't have a "Main" radio menu.

Viper_wingman_No answer on main_Answer on AN-ARC164.trk

[MVS-Viper]

Wingmen seem to respond (to the RTB calls) better on the Caucasus map, but they don't always RTB. 

[Flappie]

Please make sure you're using the "UHF Radio AN/ARC-164" menu when asking for RTB ( RAlt + " \ " ).

 

[PMcG]

Does this happen on Easy Comms?

[MVS-Viper]

Hi Flappie and PMcG,

 

@ PMcG Yes. it happens on easy comms.  @ Flappie: I will try see the UHF picklist even comes up with the easy radio set-up.

 

BTW, I'm traveling until 7/19, so my replies will be delayed until then.

[ataribaby]

There is strange AI problem about "forced" RTB, when AI reached bingo/no weapons or probably battle damage it starts flying to homebase at few meters alt constantly activating some sort of "ground avoidance popup and likely crash to the trees, powerlines or hills. 

 

This happens to me on regular basis it is nothing rare. Why AI do not force RTB at some sane altitude, jesus christ! This behaviour is so immersion breaker as after good mission you just see "ejecting" zillions of times for AI that became victims of this bug. It is especially visible with Operation Pontus payware campaign.

[Flappie]

6 hours ago, ataribaby said:

There is strange AI problem about "forced" RTB, when AI reached bingo/no weapons or probably battle damage it starts flying to homebase at few meters alt constantly activating some sort of "ground avoidance popup and likely crash to the trees, powerlines or hills. 

 

This happens to me on regular basis it is nothing rare. Why AI do not force RTB at some sane altitude, jesus christ! This behaviour is so immersion breaker as after good mission you just see "ejecting" zillions of times for AI that became victims of this bug. It is especially visible with Operation Pontus payware campaign.

 

This seems like a different issue. Please create a new thread and attach a short track showing what you describe.

[MVS-Viper]

   Hi Flappie,

 

yes, it still happens when you use the radio you mentioned above.

The trak file is attached.

RTB Problem2.trk

Edited July 27, 2021 by MVS-Viper