Funky Monkey

In mission 15 "AWACS Hunting", the "OBJECTIVE" portion of the briefing says that we will take-off from and land at Gudauta. That's probably copied from other missions in the campaign. In this mission, we actually take-off from Nalchik and land at Gudauta.

I just played through it again. I also saw some message text in Russian while playing in English. I could decipher F-10 from that message so I checked the F10 radio menu. The F10 radio command to say that I'm RTB was also in Russian so I didn't know what I was saying except that the subsequent message said RTB. So I started to RTB even though the strike wasn't over, and later on when the enemy fighters popped up I was way out of position. Overall, the mission is completable now but it's a bit confusing for those of us playing in English.

In the 6th mission (though the filename is "Su-27 Camp 5.miz"), there is a 4-ship group of AI Su-27 named "RU Su-27 (Moz Def)" that is set to late activation but there is no trigger to activate it. It is configured to orbit at waypoint 2, looking for threats, which is sensible in the context of the mission. I'm guessing it just needs to have late activation turned off rather than add a trigger to react to encroaching bandits or something like that. Without that group activating, this mission is still completable, but it turns what was probably supposed to be an 8 vs 12 into a 4 vs 12. EDIT: @Flappie just to be clear, this is the case even after yesterday's update. T4buk hadn't reported this particular issue but I thought it might make sense to roll it into this thread. Thanks for your help!

This is fixed with today's update to version 2.9.15.9408. Flight 227 now actually resumes escort a couple seconds after saying he will.

In the "Interception of a B-52H bomber" instant action mission for the FC Su-27 on the Cold War Germany map, the "Situation" in the briefing reads: "Your task is to provide cover for a bomber carrying out a strategic air strike. The enemy has launched interceptors and will try to destroy the target before it enters the combat course. Your main goal is to intercept and destroy the enemy aircraft without losing your bomber." This text seems more appropriate for the corresponding F-16C mission where we play as blue side rather than red. In the Su-27 mission, our objective is actually to destroy the bomber, not protect it.

@NineLine thanks for looking into it so quickly. I played through it one more time and got the same behavior, and remembered to save a track this time (attached). 227 still doesn't resume escort after he says he will. After playing this, I did a repair with "Check all files" but I checked the md5sum on this mission file before and after the repair. It was cfb098a38f51596bdd398844002139af both times. This time around, I also noticed a few typos/voice line issues so I looked through all the triggers: Trigger "425 TAXI------------------------------------------": the message says "taxing" when it should probably be "taxiing". Trigger "227 TAXI---------F11-----------------------------": the message/voice says to taxi to runway 17 right but all the AI takes off on 17 left. Trigger "227 PRE-------------------------------------------": the message/voice says "internals" when I think "intervals" is meant. Trigger "F15_5-------------F305----------------------------": the message says "(227)" but I think it's supposed to be from "(F-15)". Trigger "227 FINAL-----------------------------------------": the message/voice says "17 right" but the 227 AI landed on 17 left in my playthroughs. su-27-unwanted-guest_lead_wont_resume_escort.trk

In the "Unwanted Guest" mission for the Flaming Cliffs Su-27, I saw the message saying "(227): 227 flight, resume escort." But the 227 group that represents the flight lead did not actually resume escorting the Su-25s. I followed him around in his orbit for a long time while the Su-25s flew home. Eventually the 227 group did return home but we were too far away from the Su-25s to trigger the last couple messages that are supposed to show up. I played through this mission twice and saw the same thing happen both times. I forgot to save the track for this but I've attached a TacView recording showing the Su-25s departing while 227 and I just keep orbiting. Breaking it down further, the trigger named "227 RTB----------F710---------------------------" did fire because I saw the message it sends. That trigger also turns on flag 710. The follow-on trigger is "227 RTB FLG----F711---------------------------". That trigger waits 8 seconds after flag 710 is set and requires flag 600 to be false. Flag 600 would only be true if I had initiated combat and I didn't do that, so it should be false. This second trigger pushes an AI task for group 227 to escort the Su-25s. I don't know whether this trigger didn't fire or the AI task didn't work, but group 227 did not break its orbit 8 seconds after the message from the previous trigger. I also don't know whether 227 eventually returned home because of the trigger or because of something like low fuel. Tacview-20250331-134512-DCS-Su-27 - Syria - Unwanted Guest.zip.acmi

In the MiG-29 instant action mission "MiG-29A - Airfield Strike" on the Sinai map, the mission success trigger and mission goals both require the "enfield81" unit to be alive. The problem is that is an AI unit in a separate flight from the player. The player's unit is "springfield91".

Thanks for the explanation. That is certainly an entertaining chain of events. You've enabled my software engineer brain to sleep a little easier at night.

@killjoy73au are you still supporting these missions? I played the first couple of them for the F-15C but I think I'm seeing some issues with the triggers and mission goals. I'd be happy to help work through this stuff and playtest if you're interested.

If you ever had to kill all the Flankers, I don't think you do now. In my successful playthrough, there are still 2 of them flying around at mission end. After killing the first 2, I got the message "[Magic] Dodge 4-1, the Flankers are bugging out. Disengage and return on station, steer 2." The biggest difference I can see in the TacView for the failed vs successful playthroughs is that in the failed one, the Dodge 5 flight RTB'd as soon as the Flankers got close even though it doesn't look like the Flankers shot at them, so they never engaged the Frogfoots or the Fencers. In the successful one, Dodge 5 flight hung in even after getting shot at by the Flankers, and proceeded to engage both the Frogfoots and the Fencers.

I took one more stab at it and got through it successfully. This time I got lots of dialogue while I was RTB that I didn't see in the previous playthrough. I'm attaching the TacView for the successful playthrough in case there's something to be found via comparison. I don't think I consciously did anything differently except maybe go a bit easier on the throttle on the way to WP2, anticipating that I might need to save fuel to chase down those Su-24s at the end myself. Thanks for your support and for the great campaign. I enjoyed it immensely. Tacview-20241203-125206-DCS-F15C TGW M15.zip.acmi

I played through mission 15 and ended up with a result of 50 even though I successfully RTB'd to Kutaisi after receiving the message "[Magic] Both bandits are down, good job. Dodge 4, you may RTB. Dodge 5, continue pressing." after killing 2 of the Su-27s and both of the MiG-29s. I'm attaching the TacView for the playthrough. I don't know how this mission is supposed to go, but I noticed that the dialogue instructs Dodge-5 to anchor 15 miles west of Gori. In my playthrough, it looks like at this point Dodge-5 RTBs to Kutaisi instead of anchoring west of Gori. Then later when the Su-24s come in from the northwest, Dodge-5 is not in the game anymore to kill them like the dialogue seems to indicate they should. If mission success is tied to those Su-24s dying, then I guess that would be explain my insufficient result. I ran through another playthrough, watching on live TacView, far enough to see that Dodge-5 went back to RTB at Kutaisi again instead of anchoring west of Gori, so the problem is at least consistent enough to have happened twice in a row for me. Tacview-20241202-155714-DCS.zip.acmi

In the "The Valley" campaign for the A-10A, mission 4A has most of the briefing and triggered messages written in English. However, there is a part of the briefing and one of the triggered messages that are written in German.

I'm seeing missions that used to work no longer work because they depend on the "all of group out of zone" trigger firing when the group is either destroyed in the zone or driven out of the zone. If the entire target group is destroyed inside the zone, the trigger does not fire. Is this intended? I attached a track with 3 different groups and zones. Ground-1 has 1 unit inside the zone and 1 unit outside the zone. When the unit inside the zone gets destroyed, the trigger fires. Ground-2 has a single unit that moves itself out of the zone, at which point the trigger fires. Ground-3 has a single unit inside the zone and the trigger does not fire when the unit gets destroyed. all-of-group-out-of-zone-bug.trk

I saw a video on YouTube from July 2022 that would seem to indicate this bug had been fixed, but I am seeing the bug now. I set up a test mission with a single red ground unit in a zone and a blue helicopter that kills it. There's a trigger that will display a "RED OUT OF ZONE" message when the the "ALL OF COALITION OUT OF ZONE" condition is met for the red coalition in the zone. This works just fine when there are no static objects in the zone. When I add a FARP helipad or a "Big smoke" in the red coalition to the zone, then the trigger doesn't work. Curiously, if I add a red-coalition cow to the zone, the trigger still works. I'm attaching track files for both versions of the mission (one without any static objects and one with a "Big smoke"). with_static_object.trk without_static_object.trk

In the Revanche campaign for the Su-25A, the tenth mission "Assault Operation" has some mistakes in the briefing. The player is tasked with attacking enemy forces between 06:20 - 07:00, but the mission starts at 07:00. The other times listed in the briefing for the other flights are similarly suspect. Additionally, the briefing says the player is to "Lead an SU-25T 2-ship flight" but the mission is actually setup for the player to lead an Su-25A 2-ship flight. None of this affects the way the mission plays out but it's a bit confusing.

In the Revanche campaign for the Su-25A, the ninth mission "Assault Preparation" has us tasked with destroying an SA-11 between 03:10 - 03:30. The mission starts at 03:05. However, the Gudauta ATC does not acknowledge a request to startup even when sent within seconds of the mission starting. The player can sit well past 03:30 and never be authorized to startup. The player can just ignore ATC and go off and do the mission, but it's a bit confusing because some of the other missions in the campaign make us wait for taxi authorization for good reason (other flights taking off). Revanche09 bug.trk

With version 2.9.6.57650, in the Revanche campaign for the Su-25A, a few missions had their start times shifted by an hour so that they are now daylight missions whereas they had been night missions previously. This is a great change as it was way too difficult to see the targets in these missions without increasing gamma settings. Unfortunately, there are times listed in the "Objective" section of the briefings that are now incorrect. Missions CWW-03-1 and CWW-03-2 now start at 08:30 but have takeoff times listed as 07:35 and the times for the other waypoints are similarly skewed. Missions CWW-06-1 and CWW-06-2 now start at 17:30 but have takeoff times listed as 18:35 and the times for the other waypoints are similarly skewed. This doesn't affect the way these missions play out but it could be confusing to players who aren't familiar with the history of these missions, as all the other missions in the campaign have sensible times in their briefings.

After the update to version 2.9.6.57650, I didn't see this problem happen after about 20 attempts to reproduce it.

I verified this is fixed in version 2.9.6.57650.

@dlder thanks for helping out. If you don't get a chance to run through it, I will be able to in about a week.

In the Revanche campaign for the Su-25, the fourth mission "Beginning" has an enemy group named "Укрепление" that we have to kill for mission success. It starts off east of the river that is east of Gali, heads north along a road, crosses a couple bridges, and then follows the road west into Gali to kill a bunch of our friendlies. Just in front of that group is another group called "Наступление ВЗ_1" that has the same route but whose destruction isn't necessary for mission success. For me, about 80% of the time the "Укрепление" group that we need to kill gets stuck around the first of the two bridges it needs to cross to get to Gali. Watching what happens just before it gets stuck, it seems like it is getting tangled up with the "Наступление ВЗ_1" group. You can see units from one group going off the road to pass units from the other group. Often around the first bridge, both groups will slow down quickly and and then slowly grind to a halt after the initial slowdown. When this happens, there is always at least one unit that is not on the road at that time. It's still possible to complete the mission by destroying the "Укрепление" where it gets stuck, but based on the timing it's pretty obvious the player is intended to engage this group on the east side of Gali but west of the big river. The group is set to not disperse under fire so we're supposed to be attacking moving targets on the road. Revanche04 bug2.trk

In the Revanche campaign for the Su-25, the second mission "Target Range 101" begins with an external camera view and some text messaging describing the target range and the different targets on it. The camera jumps around a little bit as this goes on, but at no point does the external camera view point at anything that is being described by the text messaging. It seems like the camera is supposed to be showing the player the various targets in preparation for starting the mission. The mission plays just fine after the player is dropped into the jet, but it's a confusing start.

In the Revanche campaign for the Su-25, the first mission "Relocation" has a discrepancy between the mission start time and the flight order listed in the Objective portion of the briefing. In the flight order, we are told that callsign 866 will take off at 06:57 and we will take off at 06:59. The mission start time is 06:30 so it seems like we'll be sitting for almost half an hour before getting in the air. However, when the mission starts, 866 is already on the runway and takes off immediately at 06:30. If the player starts up and takes off as soon as possible, the mission plays just fine. However, if the player tries to follow the instructions from the briefing, they might think they should wait 29 minutes, during which they'll hear and see all the messages they are supposed to be receiving in the air, and they'll get instructions for landing at Sukhumi-Babushara before they've even taken off from Sochi-Adler.