highzur

Fini également, top, merci encore

Hi both, Now that you mention it nachinus, I observed the same thing and actually took a screenshot (well, didn't remember the shortcut for the screenshot so actually took an horrible photo) - see attached. But I checked in the recent changelogs of DCS and didn't see anything related to the Gazelle. And they didn't use their gun either. R.MES, if you find something that could be wrong with the mission and would like to test a remediation, feel free to send me the file and I'll check. Regarding your PC crashing, could be worth cleaning/updating stuff before considering a change. Syria needs a lot of DDR but if you managed to start it in the recent past, there is no reason why it wouldn't work anymore now. Best, highzur

Hi there, I use the latest open beta. Checked tacview: Dragonfly 2 stays on its flight plan (or possibly approaches the target then go back). Dragonfly 1 actually did CAS twice over four attempts, but fires only once, misses, then do passes without attacking (despite available ammo). I thought ALAT could do better I used my gun to kill their targets and move on with the mission.

Hi R.MES, Thank you very much for both your campaigns. As others already said, we can see you have put a ton of work and love in there! It is diversified and super immersive with all the background you have built, great stuff. Thanks o-Tomcat-o as well, your walkthroughs are very useful. Unfortunately, I have an issue with mission 02. After succesfully dropping the two bombs I get the message to wait for the Gazelles to finish the work ("stay west of wp3...") but the Gazelle don't show up. They go to their wp2 then continue their flight plan to wp3 etc and ultimately land. I tried the mission three times and never saw them attack so mission fails. Any idea about what I could be doing wrong? Or it is broken due to an update or whatever? Thanks Highzur

You're welcome! Great! Thanks ;-)

Hi All I was facing an issue with the first mission of the Coup d'Etat campaign and found the fix: When the truck stops, Chevalier asks you to make a markpoint over the crash site. I tried several times to make that markpoint and never managed to trigger the next steps of the mission. I thought my markpoint were not precise enough and tried again and again. Eventually, I looked at the mission editor and realized that the trigger zone was huge The problem was coming from the fact that the trigger is set to detect cockpit arguments 581 and 583 (markpoint then validate). I checked in clickabledata.lua and identified that in my version (2.7.1.71.39) the actual arguments are 580 and 582. I edited the mission and then it worked like a charm. I don't know if this is an isolated case related to my setup or due to an update that changed the argument lists for all. In which case, I would recommand to check all missions using such trigger. @baltic_dragon sharing so that you can fix this during a next update maybe ? Also do you know if similar issues are to be expected in other parts of the Caucasian or PG's campaigns ? Merci pour ces belles campagnes en tout cas ! Thanks highzur