Dagger71

Magic 2 uses the AD3633 seeker. Although it does have head on capability, it will be much more easily fooled by flares from this aspect. Besides, all IR missiles can be fooled by flares, when they are deployed at the right time and interval. Edit.. Are you saying 5nm or 5 miles out (which would be over just 4 nm out) ? When using Magic 2, you should almost always fire at rmin to get a better chance of kill. Anything more than that and it will easily chase flares. 5 miles out is way too far to fire M2K (and many other) Fox 2 missiles frontal aspect.

Yup from 0:45 to 2:26 is from theAC-130 spectre video game on the ipad! hahahaha! And the first part of the video does not look to represent any UAV in the Iranian arsenal. if part of the video is fake, then the entire video can be called into question.

same issue. endless loading screen then back to main men after 15 or so mins

same issues. so far no "fix" has worked. MP unavailable in 2.5 for me right now!

Ya sounds like you have a PCA select button mapped.

Also make sure you follow engine restart procedure properely: Engine shutdown to off fuel starter pump switch to on engine relight switch to on slowly push throttle forward until 50% N1

If the tank is empty I don't think it rips off at 7gs.

This is why from now on I am keeping a close eye on all modules as released. I will not purchase another razbam module until the M2K (which I bought a YEAR ago but only really started playing for the past few months) is patched to a released state. I would love to get the Harrier, but there are too many issues with the mirage for me to pump more money into and beta release.

This is the correct answer:P delete my post :)

I'm pretty sure they answer for all the modules I have KA A10C M2K. But your engines does in fact have to be off for repair to start. so not a bug.

did you shut down engines?

I was using HFR as well. not sure how you got 15nms. I rarely switch between HFR ENT and BFR because I see no difference in its application as modeled currently. I will switch between 4-2-1 and 60 30 15 if I am not too target fixated. Otherwise I switch between BHA BH2 and Vert special modes to lock until splash, but even there I almost exclusively use BHA

so max detecting range of the RDI for a cold contact is around 8nm?

1.58

Ok made a quick mission unlimited ammo enemy 0 weapons. So this video isn't showing what we are really talking about (RDI loosing radar contact at close range) But look what happens. first pair of 29s at 15000 less than 30nm out cold. My radar does not pick them up until the su27s which are over 20 nm beyond the Mig 29s get picked up! 7.8 NM before the RDI will pick up the M29s! Not picking up radar contacts when you know where they are (on MP We fly in groups so we usually know exactly where and what alt the enemy is at), is even just as frustrating if not more then loosing lock just before or right after firing. ) Sorry about the jumpiness in the cockpit. my TrackIR was messed up a bit. rdi.trk

I absolutely agree with everything you have explained so far. BUT that is not what we are discussing. Evading missiles using crank notch or pump is not what we are discussing. In the video the SU27 never lost lock, the F15 successfully trashed a tracking missile . What Conroy and most people are complaining about is how the RDI looses lock so easily even over water NOT how enemy evades the missiles. This all happens most of the time before weapon is even launched. We're talking about very close target between 2.5 and 10 degrees under nose. This did not happen before, at the rate and at such a shallow differential. As stated before I can sometimes even visually spot a target before the RDI displays the contact (much more often then before and we are talking multiple targets above below and same alt) I have definitively changed tactics over the past week or so, where I will always dive lower than a target to maintain lock, but again the RDI sometimes decides even the sky is clutter and will momentarily loose lock.

Conroy your pictures show exactly what happens all the time!! In every instance target is less than 5.5 miles out and look at the two bottom pics. In one, the target is LESS than 5 degrees off your nose and OVER WATER!!

Actully makes a lot more sense. Wasn't really thinking about it. Thanks But have you noticed a problem with the RDI since last patch where you can't even get a simple track sometimes with a known contact.. your alt stragith ahead , Yesterday I even spotted the AC in front of me, i got lower raising nose to him .. nothing.

You have to be ready to switch to special mode (I prefer BH) if you are locking a lower target as the radar will 99/100 loose the lower target forcing you to re-acquire. When I killed you yesterday while you tried to notch me, I knew I'd loose radar lock, so immediately switch to special to get the kill. I have my finger on the special mode button every single time I fire a 530. It's so ridiculous that it happens this bad that it should actually be in the manual as a procedure for firing 530s. This will not always work, as just as often, loosing lock will happen a second or two before missile impact. HOWEVER: Since last patch everyone is complaining about not even seeing targets ... Some are at 12 o clock, same alt and even VISIBLE through cockpit but radar sees nothing. Got much much much worse since last patch. Pretty soon if this keeps up the Mirage will only effective when carrying Magic 2s.

Looks like you are right. But noway, no how have I EVER got a track with a lower flying AC at 16nm out while flying even at 20K with a 20 degree antenna!, I have to lower my antenna almost to bottom limit to even get a simple track. Also why does the min/max numbers change when moving TDC. The radar doesn't chase the TDC, so the numbers should be constant at level flight.

I dont have time right now but I will do some test runs and follow up with the math.

Well not really what I was trying to explain, but anyways. We both know it is wrong. 4 lines = 12 degrees up and down 2 lines = 6 1 line = 3 degrees. So when moving antenna up and down what do the hash lines on the left side of the radar screen represent ? 2%? So from 30 000 feet at 2 lines scan sweep, (which is only 6 degrees lower than horizontal plane) and lowering antenna down a has mark or two should NEVER translate to the cone pointing under the earth as the RDI cannot extend that far enough to cause it to be pointing underground with such an extremely small offset at such an altitude. Regardless of the delay, it should never remain in the negative at that alt at that sweep angle at 40 kt range.

Sorry I meant target is at 32500 feet. But why is the cone between 3k and 24k? How is it tracking the target? Also why dows the min/max cone range drop in the negatives when you point antenna slightly lower than level? I understand what "should be happening" but the data output to the HUD is all wrong.

should be is referring to angle off the nose.. in this case the cone is 3 to 25 degrees. As you can see his radar antenna is slightly elevated. Also In the photo his alt is already 32500 feet so it would not make sense that the cone is between 3K and 25K with antenna pointing up slightly. Now I have experimented myself and there is definitely something wrong with the display cone min max. I believe it is supposed to display the cone at TDC range but something is messed up. Eg I am flying at 30K flight level, ant centered and yet my cone is displaying 29/28 max/min. When I do get a lock the target is outside the TDC cone values. ei the target is at 14k but the tdc vales show 21/19 at lock. Also if you lower the antenna, at any altitude you will find your cone to display negative values with only a slight decrease in height. Something is not right with this display. If it is displaying min/max alt of cone then we shopuld only need to raise lower ant a % of a degree either up or down to get the full range, but in game that is not true as sometime I need to lower the antenna almost to the bottom to see targets below me even though the display is something like -34/-60.

nice! Can't wait for it! I still get that glitch where you touch down rear wheels at low speed and front wheels bounce off the runway sending you into a vertical spin.