Air Force

Only a Visual Glitch It's a visual bug only. It's any other aircraft, AI or a multi-player, the fire continues on even after it's been put out internally. It also makes you or a damaged AI more visually observable to other players. But no, there's no fault in the damage modelling, but only a glitch in its visual representation to others.

It's been fun reading this topic, albeit ALPHA does show some language deficiencies, which may come across as rude. But even overlooking these, he's still being irrational. He's obviously concentrated on the MiG that he flies primarily. Making the R-77, or any other missile for that matter, not give a launch warning in SST would require a complete redesign of the current system, which took 20 years to develop. In DCS, for simplicity and fairness, the SST launch gives a warning and so it should remain so. To summarize, the facts are as follows: TWS2 with R-77s on MiG-29S against 2 targets does work great. The second target is marked with a cross (+) and both missiles track. This is assuming all the conditions are met, like no background ECM noise, etc, but it does work well, especially well with medium PRF. :) The bug of TWS2 giving a launch warning prior to R-77 going active is admitted. The launch warning should only be received within 15km or ARH seeker range. But should the lock warning be given still or TWS2 should be like TWS on F-15C but only 2 targets? Again, for game's sake and fairness, the latter should be implemented. There's NO such bug as getting ARH warning from over 15km, period. ALPHA's observation of such a warning is false or misinterpreted.. The SPO Beryoza in DCS would never show an ARH missile from farther than its seeker's strength. The EOS detection range is being tweaked, at least the gyro-free is fixed. On idle, head on, the EOS loses targets quite consistently, outside the 15km. OLS-27/29 should not show exact distance to target at over the laser range finder limit, which is 15km and 10km respectively. The range must be guessed if farther, or compared with data-link. However, so should not the A-10Cs RWR show a laser warning (L) from EOS over 10-15km. So, ALPHA did not bring anything new to the table. He made a mistake of misinterpreting ARH warning on RWR from over 15km, which is not possible, and is not a bug in DCS. These bugs are admitted: EOS max range and stationary/cold targets lock needs fixing. TWS2 gives lock/launch warning, and should not, for the simulation fairness. Changing SST lock/launch behavior for ARH or SARH is too big of a game changer and will not happen, it has been perfectly great for many years. The rest is debatable and is not a fact. P.S.: Do not eat an R-77 for lunch. ;)