Dugong

Yeah i can't quite tell if it's me or not! Does the gain do anything? PRF mode switch doesn't seem to affect the range and i'm not sure which of the switches on the radar panel are actually modelled and which are just animated but don't do anything.

It seems the detection range for very large fighters like SU-27/34 in same altitude or look up situation is 30km +/- 2km, is the RDI actually this bad? Huge aircraft such as TU-142 & C130 seem to be detected at 100km.

Is it finishing the 21 after an astonishing 3 years in early access? No, thought not :P

I figured it out, pressing Rshft T and it works, but pressing a joystick button bound to the very same command doesn't work for some reason.

when one uses track IR? I've tried various combination of controls but can't seem to get it to work, what am i doing wrong?

Happens for all modules and selecting/deselecting 'scale GUI' doesn't fix

A few missing features to add; correct modelling of the BLG 66 cluster bomb Implementation of the BAT 120 and BAP 100 weapon systems

Indeed, it's made me decide to hold off on purchasing the Harrier because i expect the same thing will happen to it, they'll put a hold on development and bug fixing to concentrate on the Tucano or whatever. It's a shame because they started off really well, but months are turning into years for various 3rd parties. I'm just glad that ED themselves release there own modules pretty much complete.

I'm saying it can happen at ALL altitudes, relative altitudes and angles, but im testing without jammers. The only constant is the detection range is ALWAYS 30km.

I do think there is a bug with the M2000 radar, it's performance seems to be very variable with the exact same scenario. I set up a couple of missions so i could repeat the exact same parameters in terms of enemy aircraft, altitutdes, approach vectors etc. And sometimes the RDI behaves as you would expect it to, detecting out to 60km ish. But at other times it absolutely refuses to detect until 30-33km. It's the fact that it always seems to occur at this 30-33km* (* based on inaccuracy of measuring distance with ruler in f10) that seems like it's an intermittent bug, and there is a hardcoded detection zone at 30km (ish) where probability of detection = 1, and outside this zone sometimes the radar flat out doesn't work.

You seem to interupt every single bug report in this exact same way, to some of us these bugs ARE a problem! Please change the record, we get it by now.

There is a bug where sometimes the radar will just completely refuse to turn on, i usually get it in multiplayer, but thankfully it's reasonably rare.

I think this module has defacto been abandoned by the devs. There was a brief flurry of activity just after the announcement of the liquidation of the Leatherneck Studio as a legal entity and the formation of Magnitude, but since then little to nothing. And this comes after the mig-21 was barely worked on for 12+ months whilst the viggen was developed.

Indeed, not to mention - terrain avoidance mode - hud brightness controls - rwr brighness controls - BAP 100/120 - radar memory - radar panel switchology - replace belouga placeholder with a properly modelled solution. After so long after release, my goodwill towards RAZBAM is rapidly draining away, and future modules from RAZBAM have gone from a definite buy to a will not buy.

So i've come back to the mirage after many months away from DCS in general and i'm having massive problems with the radar dropping contacts. Is this still a bug or am i doing something wrong? When this happens there isn't zero speed differential, and the target isn't notching, but it frequently seems to happen approx six seconds after locking. It's often impossible to relock if i've pickled as the targets don't reappear on the scop until well after the 530 is out of paramters

Has there been any progress on this? It's been 2 months since CptSmiley acknowledged this as a bug but it's still a problem in 1.5. Has it been fixed in 2.0/2.1?

Yet in the post you quote, he says whilst the yaw and pitch are good the ROLL is not and still needs work. Did you even read it or did you get as far as the word 'good' and let your confirmation bias take over?

I don't understand your question, but 0.4rad per grad is from Polish air force technical manual. Thank you for the insult, but if you want planes nerfed to your personal preferences and lack of ability i suggest you go play world of warplanes. FYI testing is recording video and playing back in video editing software so EXACT time of roll can be established. I suspect the ACTUAL issue is one of angular stick deflection vs distance movement at grip point in the real aircraft vs joystick. Joystick grip to pivot point is only a few inches, but real flight stick is a couple of feet, thus if you deflect both sticks say 10 angular degrees, your hand has moved only mm with the joystick, but inches with the flight stick. This makes joystick feel more twitchy, but the solution was not to cut the roll rate to HALF the real thing.

Flight model by peer pressure is not the way to accurately simulate a flight model, yet that's exactly whats happened here. The real aircraft is capable of between 0.2 and 0.4 radian/second roll for every grad of aileron deflection throughout it's flight envelope, with the 0.4 peak being at around 0.75mach and 15k feet alt. That is a roll rate of in excess of 400dps. The max i can now get in game is 215dps, the last patch was circa 350.

and yet it seems that's exactly what they've done in this latest patch, just lowered the maximum roll rate instead of dealing with the inertia issues.

Yup i think this module is definitely worth a purchase. Fun to fly, challenging to go up against F15c/SU27 but still a competent adversary, surprisingly it actually has a reasonable level of effectiveness in air to ground as well, which should be even better when we get the BAT & the BAP.

I've had a search around the forums and can't find an answer, does anyone know when we'll be getting the above along with the properly modelled Belouga? Thanks

Yes but angular deflections of steering cue are still much larger

Indeed the modelling of the ASP is catastrophically bad, i think the only mode it works correctly in is Manual/Rockets. The weapon selector is also wrong for all AA modes. For those who can't read Polish,In AA mode, every press of the release weapon button will fire a missile. The chart shows the release order of the missiles depending on the position of the SAR/IR selector (column 6, SS=IR, RNS=Radar, dowolne=any position), and the position of the weapon selector (column 5). It can be seen that the release logic is not too complex; the IR/SAR switch is the selector with the primary priority, the weapon selector knob the second priority and missiles are always released in pylon pair order. Note that the pylon numbering in the attached manual is from left to right, not the 3-1-2-4 convention

I get that impression from watching the vid as well, currently i have to zoom fully into the HUD to get a reasonable indication of the steering cues, i find it impossible to gauge from the normal view FOV.