Cyking

Thanks! I've already made the change on my end and will include it in the next patch.

I had to stop their patrol route, sadly they're just standing there now. The route was placed well away from the road and taxiway, but for some reason they keep deciding to walk on the road anyway. Maybe they're trying to avoid getting their feet wet from all the snow 😂🙈… But no idea what's going on with the pathfinding worked fine the last couple of months, but thanks again for reporting it.

Hey, 
Thank you for your feedbackIt is already fixed on my end and should be fixed with the next dcs patch on your end. 
 
Meanwhile you need to tune in the channels manually or see screenshot in post above where you see the „wrong“ presets as they are set now. But seems you already found that workaround. Happy to hear you and enjoy it so far 😎

Hey Gents, 

@GimmeYourShoes  thx for confirming. I also checked and can confirm i messed it up, my fault. One of these typical last minute changes and here you can see the result. The Atis was one of last elements I added and also changed some of the radio preset order, seems here I did not test it correctly. 

It is fixed on my end now and I will push to ED for next update. 

Meanwhile workaround is you have to tune in the channels manually. Below a screenshot of the presets how they are in the mission right now. As you can see 2 and 3 are both ATIS, the 4 is Kiruna Tower. Darkstar is missing and you need to tune manually on 348.7, sorry for that. 

should be fixed with todays patch. 

Hi @guitarxe

Yes I updated all the missions to the latest Syria Update!

Thank you, and yes, you’re right—it was a copy-paste error. I’ve already fixed it on my end.
The debug marker is also fixed on my end already… I think! But I’ll double-check it just to be sure.
Please let me know anytime you find something. One of the big challenges I’ve faced with my first project is that, after a while, you can become blind to certain details or forget to re-check them, whether it’s an ADF frequency, text errors, or misspellings. So, I always appreciate your feedback.

Yes that's probably the reason, so there was a check flag missing on your way back and so the divert to Haifa did not trigger. I think I will adjust the trigger layout here to avoid sth like this in case the player takes off to early. 

Hey Dim, so as mentioned in mission 1 by Oberst Schroeder you should use the Nav Radio to tune in to the radio station. Otherwise you will block the frequency for the radio calls in some of t he missions. By using the Nav Radio you are able to listen to the music and the radio calls. 
Honestly not sure, why there is big noise if you use the vhf comms for it, it is kind of a DCS thing I think. I always used the Nav Radio for it in my tests. 🙈

Hi, 
yeah sadly the latest syria update broke some of the missions. Should be solved with todays upcoming update. 
 
 

Hi, thank you! Good point, i will adjust that. 

Hi, thank you for your feedback. Let me have a look at the codes and the frequency again. But the 440 is quite hard to find because there is a other beacon on the map with same or nearly same frequency. Which was not there when the mission was created. I am on it to change it. 

Regarding the smoke, amazing scripting work, ha? 😂 ... Just joking, the smoke is part of the ship module. It just has smoke, but the smoke change to white color. It was black back in the days when mission created. 

Hi Thank you for your great feedback!  

Regarding your question. Maybe it is a bit missleading with the F10. It is not the F10 map. I mean the DCS radio menu, and then F10 (others). Let me check how I describe it in the mission and maybe adjust it a bit. 

null

Ok, I have replicated the issue and fixed it in my build. 
 
Workaround Instructions:
- If landed on the Castle Leeds again and once the ship has destroyed the 2 speed boats, the mission counts as complete.
- Exit the mission at that point and use the SKIP MISSION function in the campaign menu to proceed with the next mission. 

or

- Shutdown the helicoptoer. 
I apologize for the inconvenience. A fix should be released with next patch. 
 

the new way to enable this is, go to autoexec.cfg in your dcs saved games \config

add following line: 
input = { command_code_tooltips = true, }