1.5.7 Operation Dixmude Mission 1 broken?

When the CH-47 comes in where it's supposed to allow troops to embark, it lands.. and shutsdown it's engine. I take off....troops embark but Sluggy or Soggy or whatever his callsign is doesn't start his engines again. The Apache never stops his engine, and takes off with me as soon as I take off. The chinook acts like he's done flying for the day.

I tried editing the mission editor to change the "land" command on his first waypoint to "embark" but he puts down a bit far away from the FARP, no matter if I put the Embark WP right on top of the landing pad the troops run to.

In my one attempt in 1.5.6, he never shut his engine down and took off immediately after the troops loaded up and I was able to escort to the target area no problems. Unsure what caused this behavior with the update to 1.5.7.

Even if my switch to the embark command had gotten the troops loaded up, it's far beyond me to ensure that any triggers and scripts occur to get him back on mission.

*edit* I didn't see the "Bugs and Problems" sub-section at the top when I posted this.. feel free to move as you feel necessary.

mrexls posted a "fixed" version of Mission 1 in this thread

The mission was broken by a DCS update and fixed by dimitriov (the author) only to be broken shortly after by another update.

The "fixed" mission seemed to work in 1.5.6 (start of the mission was working), I don't know if it still works in 1.5.7

https://forums.eagle.ru/showpost.php?p=3042819&postcount=42

Thanks. I'll check it out. The mission downloaded when I bought the Gazelle in 1.5.6 seemed to work fine.. but I'll give this one a shot and see how it goes.

*edit* No dice. Mission performs exactly as the mission downloaded with the Gazelle module. I'm inclined to think it has to do with the Chinook's first waypoint where he's set to land. As soon as he touches down he seems to begin the shutdown process, where the Apache sits there with his engine running waiting for me to take off. The Chinook goes through his dialogue for troops to embark and saying he's going to take off but he never starts his engine back up.

In 1.5.6. the Chinoook never stops his engine and is ready to go as soon as I lifted off and the troops loaded up.

I'm almost wondering if the Polychop or ED included the fixed mission you pointed me to in their module package, as they're both showing the same behavior, and both apparently worked in 1.5.6, where the Chinook wants to shutdown when he touches down in 1.5.7.

Not holding my breath or anything.. just letting it be known that since updating to 1.5.7. this mission isn't functioning correctly so hopefully maybe someone can get around to correcting it, whether it be the mission makers or the ED team having changed how a command works between updates. If I knew the mission editor well enough I'd try to fix it myself. :) But I haven't the slightest what to change.

I did this mission yesterday for the first time, for now just ignore the Chinook and do the rest of the mission. It still counts as successful.

I did this mission yesterday for the first time, for now just ignore the Chinook and do the rest of the mission. It still counts as successful.

Lol I'll give that a try... I thought the Chinook was the whole mission? I guess I can try to manually navigate it..was a little easier to do following the nook though.

Simply edit the mission by putting the landing zone of the chinook (the little triangle when clicking on the chinook) outside from the FARP.

Simply edit the mission by putting the landing zone of the chinook (the little triangle when clicking on the chinook) outside from the FARP.

Will try.

That worked! I thought maybe he would still land on the FARP, but he landed in the spot I moved the arrow too, kept his engines running and embarked troops before taking off after I took off.

Good call Dimitriov.

Thanks everybody for the helpful replies.

Unless a polychop dev sees this, there won't be any official fix to the campaign, I'm not working with Poly anymore so I will try to give you fixes via the forum but I don't guarantee the delays ;)

Nicolas

Hopefully a Polychop dev will take notice eventually, but in the meantime your solution is satisfactory. Escorting the Chinook was pretty immersive, and also gave me some practice flying close formation in my virtual Gazelle. ;)

Thank you for your willingness to help the community when you feel like you can. I also hope there wasn't too much effort involved for you in finding this simple workaround.

Best of luck to you and any current or former members of the Polychop team. As a member of the simming community, I can only have good wishes for sim developers.

It will likely be a bit before I personally stumble on any other problems that may exist with the campaign if any as I'm still trying to learn how to set the Gazelle down gently.. and my struggles with that are another issue all together. ;)

Ahah I didn't even look at the mission for this one, just thought "mmmh it lands on the FARP... So I know what did ED **** up !"

I reconverted myself in organizing mass scenarized flights in the french community now, pretty better to fly with people ^^

Nicolas

Hey, so do we need to edit the missions ourselves for this to work? Just started this campaign and i thought the missions were password protected?

Any chance someone can share the updated mission please? Didn't seem to work when i moved the landing zone for the chinook?

Thanks

James

Ok, so it works if you change the landing point of the Chinook so it lands before the FARP. Mission takes a while, got all the way to the end in VR and crashed when the phone rang. be a while before i have the time to try again haha

Still broken?

Chinook wont take off.. sad

Dimitriov posted a solution quite a while back.

Just open the campaign mission in the mission editor, click the chinook, and move the triangle slightly away from the farp. Mission will work as normal.

Hi gents, files have been sent to polychop, so it should be fixed soon.

Current workaround is to put the chinook landing zone outside from the FARP (more than 150 m away from the FARP icon). BTW, it is the solution I kept for the official fix.