BlackPixxel

Trackfiles from Multiplayer F-14 at 100 km: 5 bars from full (correct value) F-15 at 100 km: 7 bars from full (correct value) F-16 at 100 km: 5-6 bars from full (almost as strong as F-14) JF17 at 100 km: 3 bars from full (much stronger than F-14) F-18 at 100 km: 3 bars from full (much stronger than F-14) Obviously the signal strength values for F-16, JF-17 and F-18 are incorrect at the moment and need to be fixed. F-14.trk F-15C.trk F-16.trk F-18.trk JF-17.trk

In multiplayer, the SPO-15 shows very wrong signal strengths. An F-18 is much stronger than an F-14, a JF-17 is even stronger and even a F-16 is as strong as a F-15C. This makes the SPO-15 very ineffective, as even distant JF-17 or F-18 will show with full signal strength and mask closer and more dangerous threats. In singleplayer the signal strengths are very different and appear to work correctly (at least for the F-18 ).

In multiplayer, the SPO-15 shows very wrong signal strengths. An F-18 is much stronger than an F-14, a JF-17 is even stronger and even a F-16 is as strong as a F-15C. This makes the SPO-15 very ineffective, as even distant JF-17 or F-18 will show with full signal strength and mask closer and more dangerous threats. In singleplayer the signal strengths are very different and appear to work correctly (at least for the F-18 ).

In multiplayer, the SPO-15 shows very wrong signal strengths. An F-18 is much stronger than an F-14, a JF-17 is even stronger and even a F-16 is as strong as a F-15C. This makes the SPO-15 very ineffective, as even distant JF-17 or F-18 will show with full signal strength and mask closer and more dangerous threats. In singleplayer the signal strengths are very different and appear to work correctly (at least for the F-18 ).

Trackfile showing the bug(s) Here is a trackfile showing the issue. I spawn at high altitute and fly with special afterburner mode for about 9 1/2 minutes. Then I land and spool down. Bug #1: I cannot repair, even though I have used special afterburner mode and my engine lost almost all of its special afterburner lifetime. To be able to repair, I add additional damage to the plane (ripp of canopy). Now I can repair and do the repair. I take off again and go full afterburner. Bug #2: After just two minutes my special afterburner mode as well as the normal afterburner mode stops working. The special operation mode timer is now completely used up, because it has not been reset by doing a full aircraft repair. Only if I would land now with the damaged special afterburner mode I would be able to do a full reset of the special afterburner operation timer. Please fix this! A repair should reset the special afterburner timer, and I should also be able to repair a partially used special afterburner timer. SpecialAB_repairBug.trk

In the russian forums are several MiG-29 pilots critizising the DCS MiG-29 flight model. They say it is very easy to land in real life.

If I understood it correctly R-27 (and R-77) will receive a drag change to their current FM next month, as a temporary "fix" until the complete overhaul is done. I hope ED does not delay the proper CFD & autopilot update for the R-27 to much, but I am afraid they will.

The special afterburner mode (Shift + E) has a limited operation time. When the time was completely used the mode no longer is available. The engine can be repared on the ground by the repair menu. This resets the operation timer, and the mode works again. But: If the mode was only partially used, and there is still some operation time left, then the repair on the ground will not reset the timer. Repair should completely repair the aircraft, and so even a partially used special afterburner mode should be fully repaired. It would be very nice to see this fixed. Thank you!

What conditions? Propably the typical 900-1100 km/h @ 10.000m, which would give it similar range as an unlofted 120.

Thank you for the clarification.

I am talking about the Fox-1 bug: https://forums.eagle.ru/showthread.php?t=253434 Maestro wrote multiple patches ago that it was fixed and just not merged yet, but as the Fox-1 still have this bug a few patches later I am wondering if Maestro wrote about a different bug?

Just an example: detection range lookup vs JF-17 is 65 km. JF-17 can launch on you way before that.

The R-27 in DCS is not even reaching the effectiveness that you intend for it, because Fox-1 are BROKEN on the Flanker (On any other plane as well, but it only really shows on the Flanker because of the OLS integration). Any time that the lock transitions from radar to OLS, the R-27R/ER will go for any chaff that is in the air. And this lock transition happens during basically every shot. For example because of small lag in multiplayer that makes the target stutter for a splitsecond reducing its radial speed to 0, or because our radar instantly switches to OLS when the target turns through the 90° line instead of still painting the target using the OLS angular coordinate or extrapolation. Or because of the bug that makes the lock switch to OLS whenever the radar was in extrapolation mode at the moment that the target becomes visible to OLS even when the radar lock is already stable again. R-27R/ER is a piece of shit because of the Fox-1 bug. And it has been for years. And nobody at ED gives a f*** about it. And then you come and say because it is an old missile. This is not the reason. The DCS Flanker fans can deal with old missiles that are not as effective as their opponents arsenal. But they cannot deal with a bug that has been rendering this missile completely useless for YEARS. When will it finally get fixed?

There are two states, afterburner on or off. So even on the ground with a fresh plane without an engine running you can be tracked by heaters in DCS. Very primitive modelling.

Even if the range was correct it would not see jack s*** compared to everyone else. It will still be fired upon before even seeing the bandit on radar.

Looks like the target went outside of the seeker gimbal limit. Also, it misses by alot. Proximity fuze range is just a few meters.

We now had multiple patches, and it was still 'forgotten' to be merged. When can we expect it?

I agree, it is very hard to read now.

R-73 is using a crossed array tracker, which according to Wikipedia ( :) ) should be very good at rejecting flares. Additionally it has a small FOV, which makes it less likely for flares to be seen by the seeker or minimizes the time for which the flares will be seen by the seeker. Don't claim that the R-73 has no CCM just because you want it to be shit in DCS.

I hope ED does not take this thread serious. You got killed by a heatseeking missile, and instantly made this thread so that the next time you can have it easier. Imagine if everyone did that after they get killed by Aim-120, Aim-54 etc... ("OMG chaff spam did not work, ED please fixx!!!") Instead you could focus on how to properly defeat a heater in DCS, which would include not showing the rear of your aircraft to the seeker for example.

https://forums.eagle.ru/showthread.php?t=253434 Please fix the Fox 1 chaff bug. It is not acceptable that this bug that makes Fox-1 missiles useless is still not fixed after being known for over 7 months. I bought the standalone Su-27, Su-33 and MiG-29 modules, and I cannot properly use any of them because of this bug.

More than half a year later, still not fixed.

In STT it is not fixed, it propably works as it does in DCS. (But there it selects the scale automatically, player controll does not affect it anyway) In the obervation modes it appears to be fixed.

Another one of the green dots shows up when you deploy the dark HUD filter glass. So at least 3 dots in total. One on the HUD, one on the HUD filter and one on the canopy glass above the frame.

Can we at least expect the fix for the fox 1 chaffbug in an earlier update?