Mission 1 triggers

[Pyrocumulous]

Mission 1 worked for me until the first power station (Waypoint 2) inspection. I stayed on station for 1 hour 17 minutes, the first half of which Wolf 1 just hovered in HIGE, then landed and shut down for inspection. I refueled at Batumi, then returned to Waypoint 2 to check on Wolf 1, by which time he had slid all the way to the water's edge. Tried landing, etc, to trigger the next stage, but no luck. Proceeded to Waypoint 3, circled but no trigger, on to Waypoint 4 and the story began to proceed again. Wolf 1 never showed up to trigger a departure, so I eventually departed Waypoint 4, went back to check on him again at Waypoint 2. Still there. Went onto land at Waypoint 5, then back to Batumi without any radio traffic since departing 4.

Tacview attached.

Tacview-20240407-220038-DCS-WORLDS APART Mission 1.zip.acmi

[CHPL]

@Pyrocumulous
Hello, and thank you for giving the Campaign a try.
It's on some PCs, maybe because some MOD was installed. WOLF 1 did not touch the ground, so the trigger did not work.
In that case, a workaround in the Radio Menue F-10 appears when WOLF 1 approaches the station. It is aboard the landing of WOLF1, so it will move to the next station. There should be at least some radio talk.

 

This problem in Mission 1 is the only one to my knowledge.
I appreciate your patience.

Edited April 8, 2024 by CHPL

[Pyrocumulous]

Thanks @CHPL. Tried it again, with the same result. This time I used the F10 menu when WOLF 1 hovers at waypoint 2: "Follow WULF 1 and give cover" and received the reply "Sorry, Frank, we have to wait for WOLF-1 – close the Throttle to idle, it saves fuel and its more relaxing." I tried "ABOARD MISSION AND PROCEED TO MISSION 2" and that just ends the mission.

There were no other F10 options besides tuning the radio. No mods, in fact this is a fresh Windows and DCS install due to some issues with a previous Pimax install.

No worries, I'll move onto the next mission tomorrow, appreciate your work.

[CHPL]

@Pyrocumulous Sorry i may not be clear enouth in my explanation. 

You need to activate the workaround before Wolf 1 hovers while he is still on approach. So he would not hover, instead going around and heading to the next station.
The mission would not have worked without WOLF 1 going ahead because triggers at the second station relied on his presence there.
If you feel unsure, I will make a short video, so do not hesitate to tell me.

 

Edited April 9, 2024 by CHPL

[CHPL]

@Pyrocumulous

Does today's DCS update also include the Mission 1 update?
Have you possibly installed the original stable version of DCS, but you have not received an update yet?
I know this is a big ask because it takes almost 40 minutes to get to the station, but would you try again without a workaround?
I am inquisitive if this could have been the reason. 

[Pyrocumulous]

@CHPL I'm traveling now, but I'll update, fly, and report when I return next week.

[Pyrocumulous]

@CHPL the update apparently resolved the issue, Mission 1 now proceeds perfectly without use of the F10 menu. Thank you! (DCS World 2.9.4.53707 MT)

Edited April 16, 2024 by Pyrocumulous

[CHPL]

@Pyrocumulous

Many thanks for your efforts.
I'm very sorry, but the information from ED about updates comes from the crystal ball.

[Pyrocumulous]

No worries there, I feel the collective Creator's pain on that front. Hope to see Storm Front in a surprise drop someday soon! Do you think ED might be open to a third-party campaign testing and verification service as an alternative pathway given their capacity-limits lately?

[CHPL]

Am 17.4.2024 um 01:51 schrieb Pyrocumulous:

No worries there, I feel the collective Creator's pain on that front. Hope to see Storm Front in a surprise drop someday soon! Do you think ED might be open to a third-party campaign testing and verification service as an alternative pathway given their capacity-limits lately?

Testing is not the problem; all was to be done in November 2023.
Simple releasing.