Kercheiz

I'm pretty sure you have triggered the auto-stop bind. Please send a .trk file if you can reproduce

You might be in CAN or MAG mode, they override the selective jettison. You need to be in stores/neutral mode.

M1.02 is transsonic, it's not enough for being elligible to the "supercruise" club, especially with virtually no loadout.

You can send us the dcs.log.xxxxxxxx.zip from the corresponding date in your Saved Games logs folder. Each one corresponds to a crash

Just search for "thump sdef" in games files

Radar and TFR on standby, means it's most likely a 3D rendering bottleneck. The F-15E is quite detailed.

Optimizations are ongoing. If you still have the issue and if it's reproducibly correlated with turning on radar or TFR, please notify here, we are interested by some tests.

Optimizations are ongoing. If you still have the issue and if it's reproducibly correlated with turning on radar or TFR, please notify here, we are interested by some tests.

If anyone still has non-HRM radar related performance issues, please notify us here. I'm having a look at this and already optimized it quite a lot internally. To know if it's radar related, just check it's fully correlated with having the radar and/or TFR on. If setting radar and TFR to SBY does no instant improvement, means it's something else, like rendering.

Yes, I would say so. I know the game (I made the radar) and not the real world use of 4 bar IFF, though.

Those are obsolete, they aren't used at all.

What do you want to do?

The actual reason, is the coating on the glass is designed to reflect only the wavelength of the HUD projector (green) at the exact view angle and maximize transmission. This causes the transmission to be slightly tinted by the opposite color (purple) and this is an angle dependent effect.

The IFF antenna has a much wider lobe than the main radar antenna. In most cases, with 2 bars, it will be enough to cover the whole radar volume and even more (it will often pick IFF returns from contacts that are either above or below the radar scan volume). The advantage of 4 bar is more about interrogating contacts more to increase the probability of getting a return at the limit of IFF range.

It's only working in the raw LPRF mode, below 10NM. Just press the TDC control the same way you lock a contact

If you exit GUNS master mode while your radar is locked, you are not exiting GUNS radar mode but STT radar mode. In that case, the search elevation is not zero, but the last known target elevation. GUNS master mode and GUNS radar search are two different things even if the second is commanded by the first one. You can be in GUNS master mode and STT radar mode. For resetting elevation to zero you need to switch in and out of GUNS mode fast enough to have no locked target.

Could you share a video? What does it display?

There is a known issue with old mission files. A flare/chaff limit might be stored inside the file and you can't edit it. Try deleting the aircraft and adding a new one, this does fix the problem.

You can right now switch to OpenBeta and have it working. Stable is discontinued at next update, and there will be a single version from now on (which will be similar to OpenBeta without the name)

Being skeptical is a good thing. We have the duty to be skeptical on any non sourced anonymous user input on a forum (that's why I am now), especially given how DCS users are emotional about things. Mirage 2000 data is classified, so you will not get any figures on this forum. Then please give the same attention to the following statement by someone from RAZBAM (me) "The M-2000C FM is good enough to be used in current FF module" If both FMs are good, the +30% afterburner thrust increase between M53-5 and M53-P2 might explain a lot of things. Thanks...

Could you cite your sources please? There is as far as I know a single source telling this, the 1988 IAF tests that are story-told by a MiG-29 IAF pilot. If that's your only source, "plenty of comparisons" and "plenty of pilots" is dishonnest, so I'm interested if you have more (but I doubt as this kind of exercises has been extremely rare). That story is told by a MiG-29 expert, so maybe it's biased? Pilots are sometimes very biased (and this includes Mirage pilots). Then, it's also known that in 1988 the Mirages 2000 had the old M53-5 engine which has very large thrust difference (-15% dry, -30% AB, from memory, to be confirmed) with our own M53-P2. And finally, if this was true (Citing the articles : "The MiG-29 outperforms any 4th gen aircraft in instantaneous turn rate"), the MiG-29 DCS flight model, from the FC3 era, is maybe not 100% accurate, if we do the same comparison between the DCS MiG-29 and other DCS 4th gens. We don't do flight models by reading stories and trying to reproduce them against other DCS modules, but by focusing on the aircraft we model, and only this one.

Additional keywords : "td" for the TD/TOP feature (acceleration cues to achieve time to target) "rho", "theta", "dnorth", "deast" for direct BAD delta coordinates instead of using a marker BAD

The front seat light was fixed for next update.

Thanks, I will ask about that light to SMEs. I was not aware about a light in the front seat, but only the back one. So remember : OBSTACLE AHEAD is an alarm. Danger in the aircraft path. This requires a flyup. OBST right/left is a caution signalling an obstacle not directly in the aircraft path. This advises you to avoid turning on that side.

I will recheck the INS and UPDATE sync part more closely.