Vatikus

Here is track, what it looked like, and my settings I do not have any mods, I've reset the installation. My grfx card is 1070 with latest drivers. glass.trk

Mig15 has big problem as well

I did a test as well... it is a bug. DCS SA3 launches 5V27 missile which has ceiling 18km.

13.VLS Vati - mig15

It depends on which missile... but most systems use 5V27 which has 18km max. alt. The F117 in '99 was hit at 8km altitude for an example.

you can find guncam stills from mig21 which have f16, f15, f14, f18, mirage, mig29, etc. with piper on them. Does that mean mig21 is best? ;)

We do not have enough data to know how is the exact type treated by the SPO. All we know is that these types share the same light indicator. What we also know from the manual that SPO will inform the pilot that he is inside the missile wez for the type by flashing light on the signal strength/range indicator lights strip. So by these mechanics.. as you said, X -> F, and wez light, pilot can get the SA regarding range. Also by rate of change of these lights, pilot can get SA regarding the closure rate... Combine that by GCI which cannot be separated for Russian fighter/interceptor, pilot would not be clueless.

SPO15 should be able to point out radar type.. F14 fall intro a indicator group of F14, F15, F16, F18 & Phoenix missile (similar as US rwr which groups mig29 and su27 family under 29)... you would also get an indication of radar range, ratio of range change and missile launch range... in real SPO15 that is... in DCS we have, of course, nurfed version.

I fully understand that radar should not be all seeing eye, etc. Thing is, in dcs m2k lock drops as well in high aspect angle with plenty of closure.

Since there are dozens of bugs regarding radar display, we cannot be sure if these are isolated only to the display representation.

I know Cmptohocah, as I said "if they knew they had missile incoming"... There were pilots who did evasion maneuvers and evaded 120 and 7. There was zero use of chaff as 29A does not have it. p.s. Since you are from Serbia, you can read yourself L-18 manuals. Well worth it. Cheers from Slovenia :)

The rotary switch has multiple actions. It also controls the Dmax launch zone, ie. besides the fuze setting on R27. Regarding the settings... small is for drones and missiles, medium is for fighter size f15/16, large is for bomber size b1/f111/b52 However to expand the topic regarding chaff... I find it quite interesting that mig29A did not use chaff catriges at all. The manual speaks only about flares. This explains also why Serbian pilots only used (if they knew they had missile incoming) maneuvering for defeating aim120 and aim7. Using doppler radar pretty much lowers usage of chaff.

GGTharos, fuze setting is from manual.. it says, if target is using chaff, set it to medium to avoid triggering off the chaff cloud. It's not something I made up.

in mig29 manual it says that chaff can drop lock in look down from rear hemisphere... rest should not be a problem. And the R27R1 only needs to have proximity fuze settings on medium size target, to lessen chance of fuzing on chaff cloud. So if you have lock, there is no way R27 should go for anything else but locked target.

Well said sedenion. If I look from my own experience, it took me a lot of time to dig out "RTFM" from various sources to be able to use M2K and of course, in the end to find out that I am hitting a wall of bugs which due to no proper manual are hard to notice as you do not have anything solid to compare to. This is false. ED's store does not list M2K as an early access, nor is STEAM. By this, I, as a customer, am taking ED's stance over fanboi apologism.

Or simply numbers ... i.e. during '99 Kosovo air campaign , there was a shortage of aim120, so there were mixed formations of f15c with aim7.

i'll just leave this here ...

Look, I never wrote that M2K is abandoned and that it will stay in the current state forever... I understand just fine what was the RB statement. Fact is, there is/will be no progress available for M2K for unknown time table. This is what is making users uneasy and they have all right to be, as you have yours to be ok with the current state. Again, as I said it before, I see the culprit of the problem in ED not RB as they are the one who allow this type of work -> not enough manpower to work on multiple projects at the same time, resulting in hurting the development of the released module.

This. It is that simple. Some of us like early access. I think the frustration is more in the line that there is no final product YET as developer switches to a new project. I see this more as ED's fault than 3rd party developers, as ED should had better QA policy for the modules. As of now, we have bunch of half made products with no guarantee that they ever will be finished. It's a mess which only ED can fix.

I was flying a MP with F5... and was in fight vs. AI enemy F5. What happened was that as I have seen AI infront of me being hit by a missile which was shot from the ground and at the same time my plane exploded... After checking the tacview file (screenshots attached), it showed that Stinger which hit AI gave all damage to me.

PAK-FA software testing...

No, both switches act the same

The ball moves, so it is present. Problem is that there is no effect by abusing sideslip (ie: w/ fast roll), except blackout :noexpression:

Golo, what manual says is that autorotation starts if there is sideslip or/and near 0G coupled with high roll rate. This does not mean that what we have now is super correct, but what we had was even worse.

Real mig21 has roll stabilisation up to 70deg. I have tried it and I can keep past 45deg ok... The problem I see is that if I roll inverted there is no more clutter as it was before... also clouds do not effect it anymore :/