Dugong

So is it just me or does the Rs-2us not working as intended? The only way i can get the thing to launch is to lock on in standard radar mode exactly as per the R3-R. If i try and use it in fixed beam mode it will never leave the rail.

strange because in MP i can't locate targets even at 5km altitude, and when they are occasionally detected at 30km, they disappear from the radar scope as i close in. Maybe the new MP netcode is cocking things up.

Unfortunately the devs seems to have given up on answering 90% of questions nowadays, but if it helps i also use MSffb2 and occasionally have a problem (in all modules) where even though i click the 'swap axis' tickbox the setting does not apply itself in game which causes the pitch axis ffb to apply on the roll axis and vice versa. It usually fixes itself after unticking the box, restarting the game and ticking again.

Same here, it can take two or three attempts to get on to a server and it seems to be worse the more populated the server is.

Nice one Bill, exactly the issue i'm having. Snark, it doesn't seem to matter how long you wait, it only picks them up inverted or performing a very steep (non inverted) dive.

Similar to this bug report? https://leatherneck-sim.mantishub.io/view.php?id=315

Yes, the enemy plane can be a few hundred meters or a few KM in front, cold, hot or flanking and radar cannot detect it!

I've already stated what i feel the problem is , 'radar detects aircraft at long ranges 20-30km, but the targets disappear off the scope at closer ranges than this whilst they are still in the scan zone of radar' & 'diving towards earth in a not inverted dive causes the contacts to show up again, which was the behavior of the radar in a previous bugged state' if the above isn't really clear, please say so. I don't see the problem in asking the dev if this is intended behavior or not.

Well Cobra, can you tell us how it's supposed to work, then we may be able to determine if it is just a bug, or a realistically terrible radar.

Yeah i suspect the radar might be bugged again. I seem to pick up targets at 20-30km and then they disappear as i get closer, even though i can easily see them visually. Also the radar seems to pick up targets when i perform a steep (non inverted) dive towards the earth, which IIRC was a symptom of a previous radar bug.

It seems like half the time the R60M's are totally dead, as in they will not lock anything at all be it friend foe or the sun, happens in multiplayer only .

I've updated to the 15/07/2016 patch but i prefer the headtracking from the previous weeks version. Is there any way i can get the headtracking back to last week, any lua. file or similar i can copy from elsewhere?

This weeks patch seems to have royally cocked up my trackir view, the default centre view is now looking at the bottom half of the hud glass with the top cut off, whilst the week before was absolutely fine (though other people seemed to have the opposite problem where the default view was pitched too far up) Is there any lua files or similar i can copy from an older version to fix it? Many thanks

Belsimtek seem to manage pretty damn well without crashing anything, then again they do have a lot more experience with 5 or so top notch modules under the belt so far.

I would guess (hope) it is more coding difficulties than lack of information, we've had quite a few wildy different flight models so far since i bought the module and IMHO it was the 1.2x version that felt the best (apart from the stores fell off the pylons when you even thought about touching the stick :megalol: )

I just copied my old headtrcker.dll from my 1.53 version to 1.54 and TrackIR seems to behave exactly as before.

Yep, i also have the bug that once turned on it won't turn off, or maybe jammer does turn off but power light remains on? The 'illuminated' light also doesn't light up when painted by enemy radar (this is how i interpret it to work from the DCS manual description, maybe i am wrong?) I'd also be interested to know if the auto-dispense feature will be added as it is very useful on the A10.

I'm currently running the 1.5 open beta, but i now want to run the stable branch as well due to the fact that the recent OB has messed up my track ir and ffb and a number of modules. But, i've only got a few activations on the mig 21 left and in the past i've had to activate the mig every single time when running multiple branches due to the bug, and can't afford to lose any more.

Ditto bkthunder, although the cockpit & textures are pretty much the best in game, the FM and systems moddelling is making me lose faith also. We've had 4 or 5 differently feeling flight models so far, and stuff like the ASP has not worked realistically in nearly 2 years.

Yup the dampening button is the lock button, got changed in a patch a while ago as before that the lock button would unlock the target if pressed again. Can you elaborate on this? I don't have the L39 so not sure how it's supposed to work.:thumbup:

It appears with the new ARk-5 preset methodolgy as described here: http://forums.eagle.ru/showpost.php?p=2609542&postcount=6 the switching from far to near beacon always results in the near frequency being 2khz out from the correct frequency. I tried this on numerous airfields and the system only switched correctly for one airfield (though i forget which now)

Thank you for these, they are really excellent!

These hit the nail on the head for me, especially the Flight Model. There seems to be a weird jump between normal flight & stalled wing where the physics model bugs out, indeed i've managed to get trapped in the state where it appears the airflow has no bearing on the flight model whatsoever. The asp is also a major sticking point, though it kind of half works true to life in some modes, and let's not forget the weapon selector and IR/Switch which in real life are preference selectors, not absolute as we have in the sim (this makes dogfighting much harder than it needs to be). And the worst of all ;) the radar contact symbols are still inverted! despite being fixed, supposdley many months ago

Just tested the 21 RWR against the F86F and guess what, 80km detection range as well, something is most certainly wrong!

Yes, but the click sport is quite small and fiddly to hit. Yes the behaviour seems very simplistic, i'm hoping for a massive patch for the Mig21 soon! :)