investigating M03 - Wingman does not re-attack tank with GBU12

[Aerovenator]

Today I got stuck in M03, when my Wingman was tasked with destroying the tank (after the gundish task and I had no GBUs left). His first GBU-12 hit and he was tasked to re-attack. But instead the wingman ist just circling. The mission then is completely stuck.

[baltic_dragon]

Hey @Aerovenator I had this reported before twice, and in both cases it was something on user's end. Please check the following list (especially if you have any mods installed). These days many things installed on user's PC can break the AI behavior for some reason: 

The No.1 Rule with DCS Campaigns... If you have ANY mod that is NOT purchased from the DCS Store, it will probably cause issues. SRS and OpenKneeboard(Mostly VR users) seem to be ok, as we test these missions using both. Make sure to remove any and all mods before flying campaigns. (Check out OVGME, I use it daily and it works well)

If you have no mods, or if removing all mods still does not fix the issue, take the following steps(Test after each step):

1) Delete fxo and metashaders2 folders in your saved games. Can get gummed up with old files.

2) Rename you DCS Saved Games folder, run DCS and let it create a new one. Close DCS and then just copy the Config folder from the old to the new so you don't lose your bindings and also copy your logbook.lua from saved games mission editor folder, that way you don't lose campaign progress. (Some mods can write to places like your scripts folder in your saved games location as an example. Also seems to help sometimes even if you never run mods at all)

3) Do a full deep repair of DCS to clear up any unwanted stuff in your main game folder.

Some settings to check:

1) If you have easy comms enabled, disable it.

2) Under Gameplay options, make sure the tick box on the bottom right for "No force from mission, use mine" is NOT ticked.

3) Try disabling TacView under special options. It can cause issues, usually performance, that can lead to bugs if your cores are overloaded/too busy and it misses a trigger point due to that.