reported M14 Anvil launches an hour late

[Pyrocumulous]

Anvil 12, 13, 14 start up but remain on deck until an hour into the mission if the player uses Cat 3. They launch as programmed if the player launches from Cat 1. I believe the event that is triggering them to launch (when I used Cat 3) is Thor calling bogey picture. Ran this a few times in both MT and ST modes, results appear to be the consistent. Even so, the mission still works, the additional Anvil targets get hit about 35 minutes late, so about when the player has completed refueling. 2.8.3.38090 Open Beta.

RavenOne14.log Tacview-20230402-172502-DCS-R1 M14.zip.acmi

[baltic_dragon]

Thanks! I will just tell the player to go to CAT 1  good find!

[Roosterfeet]

I ran into this and never got the mission complete message after the "Bug southwest" message, probably because I didn't launch from CAT 1. Also my dash3 and dash4 launched around push time and never caught up.

Playing the second half (mission 15), I strongly suspect that the SU-33 is way more dangerous than it was when the campaign was first released. After repeated failures to get to the merge, I finally shot him down when I turned labels on and saved my AMRAAM to give him a pitbull in the face while I defended his AA-10.

Overall this is still a really good campaign. I managed to complete all the missions without skipping, except for 14 which wasn't really a big deal. (I took 4 JSOWS and did all the work myself in 11). It just needs a little love to safeguard against ED's wonky AI finding new and creative ways to break triggers.

[escaner]

I have been on this mission today. Launching from CAT1 did not work for me, "Enfield 31" (Blade) remained in the carrier.

I think that the Anvils begin starting up in sequence when you start moving, and the problem is that if you launch before any of them has started, he stays in the carrier. What worked for me in the end was to move to the sixpack area (between the island and the angled deck), wait for all other 3 Anvils to start moving, and just then go to the cat. They went to cats 2, 3 and 4, and I ended up in cat 1. By that time everyone else had already launched because I was just waiting for my flight to move.

Edited April 8, 2023 by escaner

[escaner]

Oh BTW, the mission ended abruptly without any warning immediately after an interchange such as: "Filp: Tron 51, do you have us in sight? Tron: Negative". I have checked videos in YT from a couple of years ago and back then there was a message: "Mission success, the mission will end now" or something like that. This did not show for me. I thought that somehow the mission had bugged until I saw the title of the next mission.

[baltic_dragon]

OK, I'll need to have a proper look at the whole mission, there seem to be several things wrong with it now.