AI issues with other Rooster flight

[AlphaSputnik]

Hi,

I've been playing mission 1 and 2 ( and replaying them ) and I have a lot of issues with the 2nd rooster flight.

I wait at around 3k feet for the whole flight to join up, but when I roll out and set heading to the target, the 2nd rooster flight takes almost 75% of the navigation to join up to my flight, even when flying at 70/75% throttle.

 

Then, tally is called ( and mig shot down in M2 ), I send my flight to shoot down "ground targets" and hit F10 -> Attack primary target.
The second rooster flight responds to my F10 order, then stay in their formation and fly away, and land on its own. Just as if they would follow waypoints ( and no, I double checked, I didn't asked them to RTB ).

I even had that cinematic stuff with Blue 3 crashing with rooster blue already landed, and they never help me attacking the targets, it's getting frustrating...

 

Please help me !

Edited March 27, 2023 by AlphaSputnik
Typos

[Reflected]

Unfortunately it’s just the nature of the DcS Sabre ai. They can’t keep up. I reported it 3-4 years ago. 
 

the ai can only attack what they see. But lately they don’t see anything. So you need to mKe sure they see the target before issuing the order. Use the attack primary when available that works better

[AlphaSputnik]

Yeah I watch your videos and knew that AI in DCS is not in your control, but was scared that I was doing something wrong.

 

About the « blind » AIs, it’s a shame, because playthroughs of your campaign are showing perfectly fine gameplay, and it must have been before an update that broke AI spotting capabilities. 

 

Thanks for your reply and content, I will try and move on to M3 and maybe get a better AI behavior next time !

 

Also, I did buy V for Victory, Paradise Lost and Wolfpack campaigns and AIs seems to do the job on that one, maybe only the Sabre is messed up ?

[Reflected]

The Sabre AI is especially bad at keeping up. The P-51 AI is not very good either. The others are OK.

Spotting...I think all are blind. I recently had 4 FW190s less than a mile ahead, level, and I issued the engage bandits command: 'two, unable". "three, negative" And that was with the stock, built-in DCS AI wingmen...

[AlphaSputnik]

Update : I played Mission 3 today.

 

Of course, my flight managed to fly in formation with me, while the other part of rooster was completely lost a few nautical miles behind.

My flight managed to attack the bridges ( primary target ), and number 4 got shot down, number 2 got damaged and RTB on its own, and number 3 was not damaged but followed number 2 and RTB with him... Then the second part ofrooster arrived and they received the order to destroy the primary targets. They went on a lot of dive bombings but never realeased payloads, they just kept approaching, diving, and waving off, again and again. 

I decided to RTB ( and received the CAS call ), of course at that time number 2 and 3 had landed and number 4 was dead, the second rooster flight was not joining up on me at all and I ended up doing all the strafing work alone and RTB alone. It seemed that second part of rooster flight had landed on its own instead of joining up.

 

It feels just so bad to see how well the mission was thought and designed, for it in fact is a struggle to play alone and try and do perfect hit because of the low ammo count, and the AIs being more a nuisance than helpful... 

 

Maybe I should stay away from the campaign until ED repairs AIs and you can tell us it works better ? i don't know...

[Reflected]

Yeah that’s sad beacuse it worked like a charm for years

 

I would not hold my breath, sadly AI limitations are getting tighter and tighter lately. 
 

the only thing that would help is to reproduce the issue in a simole track and submit to ED but I simply do not have the time