phtate0830

Thanks for the quick reply and the workaround!

After the latest DCS update, wingmen 3 & 4 won't start up and depart. I head to WP1 and there's no crew member in 3 or 4 when using the F2 view. I tried 3 times with the same result. I did a slow repair after the update before trying the mission.

I flew it yesterday in multiplayer after the update and experienced no issues. Maybe try a DCS slow repair?

Hi, So I decided to do some more testing as I don't have any mods and the first experience I had the same issue again where I noticed that the wind speed progressively increased after departure and I quit after it had reached 80 kts. I then I ran a slow repair as I had played another campaign (Arctic Thunder) before playing LOWOS; even though I had run a slow repair after the last update. I was surprised to see that the issue did not appear again. However, I did notice that the wind slowly crept up to about 50 kts at 5000ft and maintained that til about 8000 ft as per the initial clearance. After I began to turn toward WP4 and continue the climb, the wind then began to decrease before stabilizing around 25-30 kts. I've attached a track of this incident as hopefully this will help pin-point the issue. Note that the track only includes the startup, arrival at WP2 at 8000ft and then beginning the turn and climb to WP4 after checking in with Sentinel and Vacuum. I sincerely hope this helps. As a side note, I completed the campaign and can tell you put a lot of work into this. Other than the issue with Rotor mentioned in another thread, there were no bugs and I really enjoyed the experience! Weasel Last Out Syria Mission 07.trk

Just as another data point, I experienced the issue and play in VR. Just wanting to provide in case there is an issue that affects only VR players.

No, no mods are in use (I don't use mods). If it helps, I did complete the mission but had to ignore the ATC commands due to low fuel. The wind was 127 knots from about 250 until touchdown.

Hi, really enjoying the campaign and thank you for your hard work. Just wanted to confirm that I'm experiencing the same issue and that I had previously done a slow repair after the last update. Just wanted you to know it's not an isolated issue.

Hi, love the campaign and this is my second play through. I'm having the same issue as Fedduk. I attack the mortar position and all is destroyed but the mission doesn't progress. I ask Ronnie to attack and they complete their attack run and reform on me with the mission still not progressing. All visible targets including the outpost are destroyed as I dropped 2 more gbu trying to make the mission progress. I don't change my FM radio frequency. I'm not running any mods and I recently ran a DCS repair. Just wanted you to know the issue still exists even after the last DCS update. Thanks for your help.

Thanks!

Starting the mission, there are no player comms. If you wait, nothing happens except the AI Apaches land too close and you can't depart. Second playthrough, I took off without waiting and it seemed things would work ok. However, upon beginning the attack, all ground fire stopped and I couldn't identify all of the targets to progress. In both cases it seems that certain triggers are not firing. Thanks for all of your work, I'm really enjoying the campaign.

Not sure if I missed something from a previous update as I haven't flown sling loading flights in the Mi-8 for some time. I had the "auto unhook" command bound to my throttle and even though I received a notification that it was on/off, the cargo would not release and would go through the ground. However, after some research I tried using the tactical drop command which worked fine. My only issue with this is that I can't understand the commands (they're not in English) and know when the cargo is safe on the ground and I can release. Just wanted to confirm this is normal behavior? Thank you for your help. EDIT: Tried it again after shutting down and remapping the bindings and auto unhook works in both single and multi thread. Thread can be closed.

Not sure if this helps troubleshooting, but I am also experiencing the issue of having a Russian cockpit even though I've selected English. I was previously unaffected by this bug. However, it started affecting me when I began flying the second mission of the Mi-24 Border campaign that was released with the latest open beta update. I was not affected flying the first mission but I did close DCS between the first and second missions. The livery workaround works for instant action but not in the campaign as only one livery is permitted. I tried a dcs repair and deleting the mods/aircraft/mi-24 cockpit file followed by a repair without any improvement. Just wanted to share in case this helps. Edit: Confirm it affects multi-thread only. When i use the regular version, the issue goes away.

Just wanted to say it definitely worked better after the clean up repair. Weed engaged the Mig-23 with an Aim-9 and the F-14s helped with the Su-27s. Thanks Baltic!

So I did a cleanup and repair and selected the slow repair with the look for additional files. I think I had only done a slow repair before. Flew it again and had no issues. Thanks for your help!

Thanks Baltic. I don't run any third party mods but I'll run a repair and let you know.