Dugong

I certainly wouldn't bother, even on sale. DCS is supposed to be a hi fidelity flight simulator, the Flight model of the 21 is terrible and it's unlikely to ever get it right. Since i bought the module in 2014, it's had 20+ variations on the FM, all of which we were told were correct but they can't all be can they? It's clear LN/M3 just don't have the coding prowess to pull it off. I just dearly hope that when the Mig23/27 comes out, it's done by ED or BST.

Use the manual backup gunsight, it's much easier. The computed gunsight is badly modelled.

Mmm, it doesn't seem too clever to fight what is a civil offence by comitting what is, in many countries, a criminal offence. And then go on to admit it is madness, at least pretend it got in there by mistake when you get called out for it!

Yes i've tested winter and it would seem that the only variable is time of day, not season. In winter 11.59am i get the same lock range as summer at 11.59am. It would seem that there is a simple modifier table implemented where; 7.00am = lock range *.36 10.00am = lock range *.57 midday = lock range *1 etc It seems to have nothing to do with actual visibility and actual light levels, and again, gain and brightness controls of the shkval don't seem to have any effect.

Okay i just tried a mission with BTR-80, outpost, Grad and Zsu-23 as targets at two different date time settings the results are; June/ 11.59 am Could lock all targets at 9.7km except for the grad which would not lock till ~7km (which is weird as they were parked next to the BTR-80) March/ 10am Could lock nothing but one outpost at 9km (strangely could lock one outpost but not the other) Ground targets only became lockable at ~5.7km In both instances targets were crystal clear on the TV display.

But it isn't this. When the bug occurs, the radar will absolutely refuse to see the target at all under ANY circumstances unless a special mode is selected then deselected; ergo bug.

Indeed, you must be patient, M2000c is 2 years old and still far from being finished. Harrier people are lucky.

That's all well and good but it also happens at VERY short ranges, like 1-2km at times. I can clearly see my opponent, but my radar can't regardless of PRF mode, regardless of aspect angle and regardless of velocity delta. However flicking the special mode on and off makes it work, suggesting it is actually a bug.

Yes i also have this problem and as Tom says it does seem to be random in occurrence. It's clearly a bug and i have noticed that switching to radar special modes will always (if in range) pick up the target, even when the std mode doesn't.

I've got an intstall of 1.5.8 OB and 2.5 and it seems to be exactly as bad in both versions. Max lock range seems to be about 5.5-6km and sometimes as bad as 2km. Actual contrast doesn't seem to be taken into the equation.

Really good work on the Su7 FM, feels very nice to fly. Also how cool are those airbrakes! Only bugs i noticed was mer-6 on center pylons don't work, always ends up with hung stores and cannot switch out of bombing mode after that.

I wouldn't call what amounts to the bare minimum to be allowed to continue to sell the module in 2.5 'a major update' There is a growing discontent, and your latest patch has further broken the radar guided missiles, the cockpit lighting, the ASP, and the nuke doesn't actually appear to be fixed. 1 step forward, 2 back.

Lowering preload radius helped with stutters for me.

It's probably down to the limitations of DCS's hitpoints based damage modelling and the fact that ground units are either fully alive or fully dead with no inbetween. In reality the sidearm has a small warhead and would rely on shrapnel passing through computers/wiring/generators etc to render the radar inoperative. It isn't going to be 'blowing' it up.

Visuals only? No mention of bug fixes and correcting systems functionallity, it's not looking good is it.

Thanks rudel, i was always frustrated that i couldn't move my head to look close at the switchgear in the blackshark, this has fixed it perfectly.

Is it possible to know which is the correct version to use? I have found a 371mb package, a 433mb and a 431mb. The 433mb works but the weapons can't be fired. The 371mb only seems to work as an AI aircraft. Are the weapons supposed to work or are they for show only? Regardless of all that, thanks to the modders who made this, it's really cool and the FM feels great!

Ditto the above, there are an absolute shed load of information regarding the quantitative and qualitative aspects of operating the systems and flight model and it's very clear the LN implementation is doing a very very poor job of simulating them.

I do not care for negative rep or not, i don't even know what it is. I'm just querying why this individual always tries to quash the narrative, is this not a 'discussion' forum? He does not seem to like discussion. Does he actually work for Razbam?

Does Esac_mirmidon work for Razbam, every post he makes seems to be telling people there is no bug where there clearly is, or no problem or generally defending Razbam to the hilt?

Same here, copying the bin file does nothing?

Yeah doesn't work for me in 1.5.8.x either

This still appears to be bugged. Very occasionally it works for a reason i cannot fathom. But most of the time no mouse control of the kord is possible when using track IR.

This bird looks seriously interesting in a convoluted kinda way (more to learn is good!) but i'm a little concerned over how good the FM is, because i know HB consists of some LN/mig-21 devs, and the mig-21 FM is quite frankly awful. Can anyone put my mind at easy, or not?

There is ABSOLUTELY a bug with the trim system. I have tested it by locking my joystick firmly in the pitch and roll axis so absolutely no input is possible. EVERY press of the trim button causes a pitch movement to be commanded in the direction the pitch is currently biased towards, either positive or negative, thus continued pressing the trim button will either plough you into the ground or do a backflip. There is no commanded input shown on the controls indicator nor the ingame animation of the joystick but the pressing of TRIM DOES COMMAND A PITCH INPUT (i believe erroneously) Hopefully Sithspawn can escalate this as a confirmed bug. One can only partially get round this by the cheat of disabling in game FFB and using SIMFFB and unmapping your in game binding for trim, but you can ONLY use flight director mode like this. The Shark flys like a dream using this workaround.