Moody1204

Hi everyone ! Here is my problem : I want a flight of Mirage to fly on the deck for a long distance until they reach the target. They need to stay on the deck because if they go above 500 feet AGL, they will activate SAMs site and QRFs. So I create a trigger as follow : Switching condition -> unit (Mirage) AGL above 500 AGL -> Flag on (1) + Activate SAM and QRF units The tricky part comes here : I want this condition to end when they are close to the target and once in the zone they receive a message telling them that they are closing (so they can go high without receiving the warnings and the strike is consider to be a success because stealth till the end). So I created a trigger zone as follow : Once -> Part of group inside the trigger zone -> Flag Off (1). It does not work because, once I'm in the trigger zone, I receive the message telling me I'm approaching target, but when I go above 500 AGL I still activate the SAM and QRF... Can somebody help me with that ? I believe I use flag the wrong way and I cannot managed to solve this. Thanks for your help !

Hi guys, Back on topic, do we have an ETA for the mighty Mirage's overhaul ? I heard in the new's video that the priority is the Harrier (which is true) and that the Mirage will come after. As in the begining of this topic it was planned for early 2019, how long is "after the Harrier" ? Cheers !

Thanks for your reply. That's a good new that this bug will be squashed, thanks for taking this into account. Also it is pretty cool that it is one of the AdA request, I look forward to use this functionnality.

Thanks for your reply. As long as it paintains the lock on target to guide the fox1, seems good to me. Is this mode a real one on the Mirage (and are you allow to tell us) or is it a mode made up for the DCS ? Anyway waiting forward for this overhaul ! Cheers.

Thanks for the infos !

Dailey, it works well with me. Exept the B-scope switch all of the switches work with the fix. Are you in open beta ? or stable version ?

Hi Zeus, Hi everyone, Concerning the new radar options you talk about (page 4 of this thread, ground cluttering, jamming, terrain return); will the "new" radar take into account the fact that in narrow mode, we experienced loss of lock and contact ? I know it has been and is still discussed but I'd like to have your opinion on that. The overhaul seems to be a good opportunity to correct and improove that. Thanks !

I consider myself as an optimistic, because otherwise I would have drop the Mirage long time ago but when you love something it's difficult to drop it. Anyway even if I'm positive, I agree with you, you're absolutely right when you say there is no quality controls and as custumer (60euros to remind you...) we deserve more consideration. Let's hope they'll understand this time and that we'll have a nice free from bug overhaul. Finger crossed !

Just apply the fix (and change the speed animation if you want) and you'll be able to taxi. Please don't pollute the topic with stuff like I cannot taxi because I didn't apply the patch. Cheers

No gamebreaking right. But still and it's my last about the subjet because it's not the topic here. The radar keep loosing lock when using the narrow searching mode. And this is not because the target is beaming, or using counter measure, it's a bug, it has been for a long time and this is gamebraking in multi because no one can hunt in wider search mode : you're telling everyone "hey I'm here cause my radar is not finished". This is really anoying but once again I'm confident that they will solve the proble with the mid-life overhaul, right Zeus ? :thumbup:

Sorry but yes you miss many things, just go to the bug reported page, some of them are reported for much more time than other jet. The probleme is, why the switches animation was a priority in a module that isn't finished yet ? I could have wait much longer to see the proper animation of the Mirage but I would have prefer some consequent changes let say for exemple the radar lock issue, or the fonctionalities that are still missing after years (I know the mid-life overhaul is comming and I glad about it !). I'm just disapointed to see how "they" left this jet (probably one of the most liked, just as the Harrier = RAZBAM again), in the hand of a small team which do it's best to upgrade it. Why the Mig19 when we need a Mirage and Harrier finished ? Zeus has courage to keep doing it and I'm thankful to him and the other on the Mirage, but sometimes things are not prioritized well and end up with a mess about some switches.

Of course we didn't complain : it was working... They were fine. They decide to update it (by the way, why ? Maybe some other point were more important than the switches animation but anyway...) And now it is broken, animation is too slow (not a big deal) but some other features are bugged (see the radio chanel button, the ILS button, and the safety ones which are not safety one anymore). It's anoying to have an update, and to have a fix that create more probleme than it resolve, I'm just saying. I'm still confident in the mid-life overhaul, and I understand there are not so many people working on the Mirage than on the F18 (but we deserve more consideration, at least because we paid that module years ago) Please, be a little more rigourous next time those switches bugs were quit easy to test. Waiting for next update !

Hi Razbam and other. There was a bug with the switches You were late for the update and so post a fix to download After the fix there are still some problem (switches mooving too slowy, secure switch can be turn on/off, radar grid not working, etc...) Just saying : wha't wrong ? A fix is suppose to fix. Please solve these problem before the mid-life overhal. Cheers !

Thanks for your tests Ramsay. I will try again in Mozdok to check if there is the same problem but I'm afraid it's the case. If I understand well, the problem is that, ATC and PRGM (also for NDBs) use a different "script" to allow you to land ? I read you said that it is a known problem but it's not on a high priority level, so I just hope that eventualy they fix the problem and that we will be able to land on both runway when the PRGM is in both direction. There are few PRGM (which is a bit anoying sometimes) so if we can at least us them correctly it would be great !

Indeed, I can confirm it's also bugged in single player mission. I didn't test it with the modification of the wind direction and speed but for Mozdok and Krymsk the PRGM beacons should be in both direction. But, when flying on a single mission with the L39C, only one direction is available with PRGM... In DCS 1.5 it used to work in both direction. Do you think it is also the same problem as Ramsay spoke about ? Regards, Moody.