AussieGhost789

Ah, ok. Thanks for the clarification. I guess I need to do a little more of this :book:

From the way I read it, the range at which you can track the target is 55 nmiles, not 20. The 20 nmile figure refers to the range at which you can track a target in TWS in Interleaved HPRF and LPRF. Beyond that range TWS must be in HPRF, and HPRF is also required for STT. HPRF is good for head on targets, MPRF (and I'm guessing LPRF and maybe interleaved HPRF in the case of the Mirage) is better for side on or tail on targets, particularly when notching is a factor. So I take that to mean that HPRF is good for targets with high closure rates and MPRF/LPRF is better for targets with low closure rate. So a target approaching head on can be tracked in STT or TWS from inside 55 nmiles, but only with HPRF. A target that is side on or tail on would have a harder time being tracked with HPRF, so interleaved HPRF or LPRF is used. This means the target can be tracked in TWS in these PRF settings, but they are limited to 20 miles and can not support STT. That's my take on this. Hopefully I'm not way off.

That's the thing, you do get some kind of launch warning, but only from an AMRAAM. It's not the same tone you get when you've been locked by an aircraft or ground threat. Also, last I read, Zeus said they were going to implement the MWS that sits on the Magic's pylons, the thing that the D2M switch activates. I know that whether or not that was going to be implemented was the topic of discussion for some time, but last I read they said they were adding it.

I have heard launch warnings but it only occurs when an AIM-120 is fired at me from relatively close range, and even then it doesn't always go off. I have no solid numbers about in what conditions it does or doesn't work, but I tried it with R-27's, R-77's (to see if it was only with actives) and even IR missiles (to see if it was the A-10 style MWS). In none of those cases did I get a launch warning. I only ever heard the warning with an AMRAAM launched from close range, and even then it only happens some of the time. So what is, or is supposed to be, producing the launch warnings? Is it the RWR or the D2M thing? Someone said to me that the M2000C's RWR can't actually detect launches in the way that the other relatively modern RWR's can. Is this the case? If so, then it would be the D2M detecting the launch, right? Either way, I don't recall reading a great deal about the RWR in any patch notes, so I'm going to assume that aspect is still majorly WIP and not working as intended.

I did a repair and it fixed this for me.

Did this make it through to the latest update on the live version? Edit: Did anything new actually go into the last update on the live version? Or is it just the things that were added to the beta version being moved over to the live version? Edit 2: Answered by Zeus on another thread. Same as beta :(

So, one thing I noticed is that the radar display doesn't seem to display things properly when on the 160 setting. The other thing I noticed is that I'm able to lock onto an Su-27 at 79 n miles (might be 80 or beyond, but with the display not showing contacts on the 160 setting, even ones I can see on 80 or less, I can't tell). I don't really know anything about the capability of the Mirage's radar, but I assumed it wouldn't have the detection range of the F-15C or Su-27S. However it currently exceeds them both quite considerably. For example, the F-15C in HPRF can detect an Su-27 at just outside 60nm and can lock it up at 55 nm. So, is the detection capability of the M2K still WIP, and should that be expected to be reduced significantly? Or should I be pleasantly surprised about the range at which the Mirage can detect targets?

This is a bug I noticed a while ago but it still persists. The rocket pods, when fully loaded with rockets, appear to be empty. As the rockets are fired the pods begin to fill up. The tube that the particular rocket came from goes from being empty to being covered, as if a rocket is inside. After all the rockets have been fired the pods appear full. Just a minor visual bug, but not sure if it ever got reported.

As it works in DCS; if locked in STT you will receive a lock warning and when launched on you will hear a launch warning, be it ARH or SARH. In the case of the F-15 firing in TWS, you wont get a launch warning until the AMRAAM goes active, and you will receive no lock warning (until the missile goes active). My question was focused on the Mirage 2000 in particular, as people are talking about getting launch warnings yet I am not. Just trying to figure out if there's something I haven't turned on, or if people are mistaking the new emitter "ding" combined with an M popping up on RWR as the launch warning. Of course, that does indicate an incoming missile but it isn't the actual launch warning. The only reason we can interpret that as an incoming missile is because we see the M on the RWR. And my point was that doesn't really help when facing SARH equipped opponents because no M will appear on the RWR as there is no detectable emitter on the missile itself. Edit: Is the RWR on the Mirage 2000C actually capable of detecting missile launches? Edit 2: Ok, now I've heard the launch warning and it has left me confused. I'm starting to understand the questions that began this topic. I am hearing the chirp that was described, but only sometimes, and it seems only for AIM-120's. This is weird.

Hang on, are you guys actually getting launch warnings? The only audio warnings I'm hearing are the lock warning and new emitter warning. Of course you can use that information to infer that there is a missile coming at you when it's an ARH missile because an M will pop up on the RWR. But it's of little help when facing a SARH equipped opponent. I was under the impression that the actual launch warning is yet to be implemented.

Blufor lonewolf Callsign: -MDS-SE-Toothless #75 Preferred aircraft: F-15C

Another thing to keep in mind is that the F-15 shows AoA in cockpit units, which is +10. So if your AoA is 5 degrees then your AoA indicator will read 15. Also, your AoA will show up on your HUD only once you have passed 8 degrees (which will read as 18 on the HUD).

Hooray! :D

The ER definitely has a speed advantage at high altitude. It's not massive, but it is noticeable.

I think it's a fantastic idea! Although I do think that the aircraft should get its A/PFM first, so I have voted accordingly. It's nice because it will give people the opportunity to try out a high performance aircraft for free, albeit one with limited capability.

That's just down to the aircraft being incomplete at the moment. It should be able to detect missile launches in the same way that the Eagle does, but currently that is not implemented. As for the A-10C style MAWS, whether or not our version of the Mirage is capable of using that is up for debate. Last I heard/read it was a no. Although I'd like to hope that changes :P Edit: Scratch that, looks like we will be getting it on the Mirage!

You can do as rage primal said, or just use the command that you have found in the controls. Personally, I use the unlock target command.

Fair enough. I've definitely seen it referred to as Range While Scan, though. But as you say, potato, potahto :P

I just checked the manual and it actually shows it as LRS, as Gryphon says. :doh: Guess I should fact check before I post. Although I'm still pretty sure that RWS is range while scan :P

Just for future reference, when you say LRS I believe you mean RWS which is Range While Scan. As for your tactic of searching in RWS and switching to TWS, I would suggest binding your TWS key to something on your stick or throttle (like a hat switch or button that's easy to reach). You'll get the hang of it eventually. I do the same thing, it might take a little while but you can get pretty quick at it. Edit: After having a quick glance at the manual again, it appears you're not wrong in saying LRS. Guess I should fact check before I post :doh:

The priority on the SPO-15 follows the bottom indicator lights from left to right, with the left most being fighter radars. Therefore, a fighter radar will take priority over a SAM (unless the SAM is locking you, in which case it becomes the primary threat and is prioritised). Also, the spo-15 (in game, at least) recognises and prioritises the radars on board ARH missiles.

If we were to get a Tiger, I'd love for it to be an ARH. The fact that it's the variant that Australia operates totally hasn't influenced my opinion :P

Does it automatically manipulate the radar so that the bugged contact stays in view?

^ Spoilt by western avionics :P

Awesome! I am officially looking forward to this aircraft :D