BlackPixxel

You mean that the DUBL should be the standard mode, or that TAKT should be removed completely? There is enough footage of the TAKT mode on real Su-27, so it should definetly not get removed.

The HUD Duplication function is already implemented into DCS. There is a keybind for that in the Su-27 systems. Then you will see the HUD repeated on the HDD, just like in the DCS MiG-29.

There is a keybind for that already.

When can we expect to see this change? It is highly appreciated! While still not fixing the individual issues themselfs, it will avoid them under many circumstances and overall improve the R-27 alot! Regarding the R-77, will it receive loft when it gets the rework or not? Not sure if usefull information can be extracted from it, but here is some footage from the MiG-29 HDD on the ground, in what I believe is the built in simulation mode for air intercepts. The R-77 is selected, some DLZ can be seen. Engagement parameters seem to be unknown though.

You don't have to leave canon mode to lock the target again. Just look at the target and press the lock button. Just because there is no helmet sight circle does not mean that it is not active. Same with vertical scan and canon mode. You can re-lock the target without having to go out of canon mode.

Since you are also in this thread, I would like to come back to the topic of the roll limitation on the Su-27S with N001. (I hope you don't mind me writing in English, you can answer in Russian!) You say that the limitation is there. Did you experience this behaviour directly (by rolling the aircraft beyond 120° with the radar in RNP/DNP)? Or is it something that you say based on the manual of the Su-27, or training? One of the MiG-29 manuals has this in a section about the R-27ER: It warns the pilot of exceeding roll rates of 30°/s or 60°/s, depending on the version of the missile, during the radio corrected phase, especially when doing a barrel roll. Such a barrel roll is hardly possible without the aircraft going inverted, so here it does appear to be possible to maintain the radar lock. From some MiG-29 pilots, for example Fighter29 here on the forums, I also heard that there is no maneuvering restriction when the radar is in automatic tracking mode. Having the radar reset to search mode when exceeding 120° roll angle would greatly limit the potential of the plane, especially when it comes to evasive maneuvers while illuminating a target for the R-27R/ER. All you could do is fly left or right, but a rapid descent by rolling over and pulling on the stick would be impossible.

The bladegrips/rotor hub might have a velocity slow enough for the radar return to be part of the ground clutter. Just because it has a RCS of 2m^2 does not mean that it can be detected and tracked when hovering close to the ground. There are much bigger reflectors down there.

Cool feature! Is this already in DCS? Does it affect only missiles with the new autopilot or every radar guided missile?

This can be related to the barometric altitude. When you roll so far that your altitude indicator in the HUD switches from radar altimeter to barometric altitude, it shows 0. The aircraft thinks that you are at or below sea level, and you cannot fire. I think it happened when taking off from some of the higher airfields on Persian Gulf, and then flying below the airfields altitude. I think the solution was to manually adjust the barometric pressure setting (there is a keybinding for that). Everything that makes the aircraft more realistic is welcome, but if only the bad things get implemented then we don't end up with a good representation of the aircraft either. For this particular issue it is not perfectly clear how it should be. Especially with the MiG-29 manual mentioning that barrel rolling while guiding R-27ER is possible, but the roll rate during the radio correction phase has to be within certain limits.

Why is it only implemented for altitudes below 1500m AGL in DCS? Why is it implemented for the MiG-29 at all?

Yes, I always count to three while holding the nose up trim. This allows for a consistent and straight takeoff.

On the other hand I heard from 2 MiG-29 pilots that such a limitation does not exist on the MiG-29, but still it will lose lock when going inverted in DCS. And neither of the two aircraft should lose lock when rolling with the close combat modes, in these modes the radar is no longer roll stabilized and its roll axis is locked. Still you will lose lock when rolling in close combat modes in DCS unless you are within 5 km to the target.

In DCS it is pretty much this 16 km, for most if not all active missiles.

To understand what he is talking about, why don't you hop into one of the DCS PVP servers during the evening and give the Su-27 a go? Or even a MiG-29? You will quickly see how useless the R-27ER is. Not because of kinematics. Not because of real life limitations. Simply because of of all the bugs and issues that work hand in hand to turn the R-27ER into the worst missile in the game. We have: #1 All FC3 radars have too low detection/tracking ranges, greatly hurts Su-27 and MiG-29 already low detection and tracking range #2 Incorrect safety maneuver causing unnecessary turn and energy loss depending on the roll angle of the fighter #3 Lack of variable PN guidance during the radio correction phase, causing unnecessary energy loss (could be easily implemented by adding variable PN that ends at 25 km) #4 Su-27/MiG-29 INSTANTLY transition into pure OLS lock instead of extrapolating, causing much worse SARH guidance compared to aircraft that don't even have OLS. #5 R-27 goes pure on last target position during breaks in target illuminations, where it should just keep its current lead heading. This turn causes energy loss. #6 When the radar switches off, the R-27 will turn away from its current heading into chaff that is not even illuminated. Chance of that loss of radar lock greatly increased by #1 and #4. If I am engaging another player from a much superior position with much higher energy state, then I still have a very low chance of killing him. Not because his Aim-120 and Aim-9X are better in real life, but because the performance of my missile and radar is plaqued by bugs and incorrect implementation. Because of all these issues, it is extremely frustrating to use the Su-27/MiG-29 in multiplayer. The only way to get kills is with the R-27ET, because once this missile leaves the rail it is free from all the guidance issues.

Noone is asking for the R-77 to be equal to the the Aim-120B, but once the R-77 gets loft they should at least be somewhat in the same ballpark and allow for head to head engagements. The higher speed and altitude of the russian aircraft vs. the F-18 for example could even result in the R-77 flying further in some cases. In your example the launch parameters are very different.

The radar might show the correctly extrapolated track, but the missile itself will not go towards the extrapolated position. The missile guided from a radar in memory/extrapolation mode of the radar will fly towards the actual target.

I don't know if it would make much of a difference. If you notch the missile, you will very often notch the aircraft radar as well anyway (which has a wider notch gate). Still it would be interesting to see. But for a proper implementation, DCS has to rewrite the radar memory mode mechanic from scratch. Right now memory/memery mode will receive the actual position of the aircraft for X seconds after losing the lock, which would result in the missile being 100% notch-proof for X seconds. Instead the radar should actually extrapolate, and its track should deviate from the actual target position, especially if the target maneuvers. Also, INS inaccuracy of the missiles has to be considered. The midcourse corrections work so well, because the missile activates its seeker quite far from the target, where the angular error is quite small. If it would now lose the target and fly by INS + midcourse correction for another while, then it might be that at the target location received from the datalink it will not find a target, because the position of the missile is off due to INS drift. So it would indeed be nice to see this implemented, but ED has to be very carefull not to make it too simplified, as this would make it more powerfull than it should actually be.

You don't have to reset the Shkval for slewing to datalink targets or for deleting datalink targets, pressing the uncage button is enough.

This is just for the R-27R.

One of the MiG-29 manuals has a table with the proximity fuze settings in it. It goes from closure speeds from 150 m/s to 2650 m/s. And here is what appears to be an upgrade for the R-27 fuze from the Ukrainian Radionix. You can see the same specs of 150 m/s to 2650 m/s.

Does your interpretation of the range chart take into account that the radio proximity fuze of the R-27 needs to have a minimum closure speed of 150 m/s with the target to work? (Propably so it can get a proper doppler return to determine the moment it passes the target) So at the rear hemisphere range in the chart, the missile has to fly at least 150 m/s (540 km/h) faster than the target, otherwise it could destroy the target with a direct hit and the contact fuze.

+1 The Su-25 nose wheel breaks so easily, even when slowly rolling over the grass. This should not happen.

I mean nothing happens in terms of no structural damage. The rudders deflect alot, at that speed it should have consequences as in the modules with a properly done damage module.

Great event as usuall, very enjoyable!! It really looked like red is going to lose, but the ROSS guys and other other remaining ones did an amazing job and defeated the blue ones! The massive Huey minigun fire really hit the FPS hard. maybe going back to 2 or 3 objectives would help to spread the helis over a wider area, resulting in less bullets in near proximity to the players. This could help with the framerate.

Why should it be wonky with RCS? It is set in the config to 3 m², there is nothing magical about it.