RedPanda

Thank you for your reply. I was thinking I can drop these once the pipper line goes solid. In your way it still fell a little short but the sub-munitions are able to cover the target. Maybe the computer didn't calculate the trajectory of the sub-munition.

The CCIP pipper does not work with MK20 cluster bomb right now. It does not indicate where the bomb will actually hit. The bombs fell short. Inaccurate Pipper for Mk20.trk Mk20 CCIP.miz

AI 052B / 054A launches YJ-83 at friendly ships in the same group. The spacing between 2 ships is about 10-12km so there is no way that the missile hit a friendly by accident. And they often get destroyed by each other's YJ-83. YJ-83 friendly fire.miz YJ-83 friendly fire.trk

I think what you set there is the desired speed at passing way point 1. Click the left arrow on the way point selector to select the start point. You can change your initial altitude and speed there.

Deka developers are not being very active these days...

Currently PL-5EII slaves to the radar only at its first attempt: If the missile seeker lose track of the target (For example, when the target aircraft cuts off afterburner), the seeker will return to the center and will not slave to the radar again (Unless you break lock and reacquire the target). (In my test I used seeker cage/uncage button to simulate the seeker losing track) PL-5EII slave issue.trk PL-5EII.miz

Hi uboat, Thank you for your reply. Also I would like to know if there is any plan in the future to implement the wing deployment animation and dive angle settings for the LS-6 bombs.

This bug is quite unusual. When the LS-6-500 bomb is still on the pylon, it is a normal-looking LS-6-500. However, once it is released from the pylon, it transforms into an LS-6-250 bomb. The LS-6 bombs are also lacking wing deployment animation. LS-6 bug.miz LS-6 bug.trk

CM-802AKG now ignores the cruise altitude settings and flies straight towards the target. The missile also gains a massive speed boost after it started its engine. The speed was 979km/h when it dropped the intake fairing. The speed went all the way to 2260km/h the second its engine started. CM802AKG Bug.trk CM802AKG.miz

The cold launched Mach 100 issue has been resolved. However, it now also misses targets because it goes for a very high trajectory (peaks at around 55,000m) and losses control in the extremely thin air (fins ineffective above 30,000m). Its control fins could not pitch the missile downwards and the missile often fly over the target which is a few kilometers below. Since the missile can't go down on its own, it basically goes for a ballistic trajectory and thus can go insanely far. First HHQ-9 was launched at 130km The first HHQ-9 hit me, going Mach 2 fully cold, at 223km HHQ9.trk

Replay track file added Replay track file added

The current HQ-7 is the very much ineffective in game mainly due to accuracy problems of its missile. It tends to miss even on an aircraft that is simply flying straight. It took 4 HQ-7 launchers (2 Radar guided + 2 Optical guided) 14 HQ-7 missiles to bring down 2 F-5E flying straight towards the SAM battery. The flight trajectory of the missile also seems weird and unrealistic. After miss the target, the missile will loop around and try to hit the target from the back. Some missile even could do a couple of loops before it ran out of energy and hit the ground. Please revise. HQ-7.trk

The Type 730 CIWS on 054A frigate faces the wrong way and I am sure it does not point its gun to the chimney in real life.

This post contains 2 bug reports concerning the behavior of the GB-6 glide dispenser: The first one is the Undershooting issue of GB-6 SFW: its submunitions hit the ground before the target. I have noticed other reports about this behavior but to this date I tested, it is still glitched. The second one is about open altitude of the standard GB-6. It seems the GB-6 will always open and dispense the submunition at the default altitude of 295 regardless of the set height, while its glide path is adjusted for the requested open altitude. In other words, GB-6 will overshoot and undershoot according to the different set open altitude. GB-6 overshoots with 750 open altitude GB-6 slightly undershoots, 150 open altitude. GB-6 SFW .trk GB-6 150.trk GB-6 750.trk

It is already turned on. On the central MFCD you can see it is in Type 1 Jamming mode.

I remember that the KG600 jammer pod has the ability to range a rough distance between the aircraft and the radar source. But recently I found that all the radar signals on my RWR always stayed on the rings. That does not provide any ranging information like before. Is this a bug or what I am missing?

This post contains two bug reports. And both of them are recorded in one trk file. 1. WMD-7 visually looks to the opposite direction that it should be looking. 2. GB-6 (basic clusterbomb model) overshoots when you enter a larger open altitude. The larger number you enter, the more overshoot it will produce. Also, it didn't release the submunitions at the set altitude. dcs.log Bug report.trk

I never fire the missile until I am 2 miles away from the bandit. 3 miles is too far for PL-5E to hit. To me PL-5 is just a cheap solution to shoot down easy targets, drones, heli, etc.

I lost the server track file. But I managed to recreate the problem. At first I could get a lock for more than 10nm. And as you said, he might reduce the engine output so I lost the lock. That make sense. But after the merge, I was on his tail, he was full afterburner, and PL-5 could not get a lock at such close range. I knew some early missiles have launch G limits. PL-5 may have it too? Here's the video:

Head on in first case, rear aspect in the second. I understand that the target gives a smaller infrared signiture from the front but why would I get a tone at 8nm and then lost it? Shouldn't it be a constant tone once locked on? In the second case, the F-4 was flying rather high and not aware of my approach so I popped up and on his tail. I cannot get a tone till almost at gun range. I suspect there is something off with the code.

Yes, and it was slaved to the target.

PL-5 seems hard to track targets. I am wondering if it is broken or that is what it is. Me (JF-17) were fighting AI F-4 and F-5 in server yesterday: The first case is I fought the AI F-5. The initial altitude was around 15,000 ft. I got a tone at 8 nm but that's too far so I held it. Then the tone was gone and didn't came back until it was 0.4nm between us. I fired the missile but it was too late. His shells hit me first. The second case was I managed to sneak behind a F-4, at around 25,000 ft. I was on his tail and cannot get a tone till I get close to 0.8nm. Many times the missile drops the lock just before I pull the trigger, and it goes stupid. I don't think a modern Fox-2 should act like this. It is so frustrating that it cannot lock on targets under my eyebrow.