Pavlin_33

As soon as I get a chance, I will create one.

As you can see from the screenshot, there is a discrepancy between FPV shown on the HUD (correct one) and the B-scope (shows descent when level):

Hi @Mike_Romeo, here's a video. You can see that the pod looses lock just before impact. The curious thing is that the target actually gets destroyed - every time. It's just that I don't get to see the explosion . Happens on MP 100% of the time and almost never in SP.

I am not sure if this is a bug or if I am doing something wrong, but when I fly online my targeting pod seems to loose its lock and reset couple of seconds before bomb impact. This happens even when I do a gentle turn after bomb release. In single-player I am able to consistently hit targets using the pod and there seem to be no issues there. Even if I just fly over a target without banking, the pod's gumball does that snapping movement but stays on target. My engagement is between 12k and 18k feet and doing 300 to 400 KTS. In MP, however, it seems to just snap back to nowhere at some point. The only difference between online and MP attempts is that in MP I start the aircraft manually. Maybe I am missing a step?

This setting is very important and it defines the center point of your search area. According to that and in combination with the expected target altitude it will slew the antenna to search different parts of the sky:

Ah, only now I read it. Ok so probably the issue was the side slew

I had the same issue. Then I gave up on locking and now I just place the cursor at the target - works pretty well.

MiG-29B, switches from 0.25Hz to 2Hz at 1500m. Depending on the target aspect, meteo conditions and state of the laser the measurements are available from 200m to 6.5Km, for airborne targets.

Unfortunately this bug is still present in MP. My buddy got shot down by AI fired Aim7. It's as if it has a combined SARH/IR seeker.

Just in case it was missed, I am creating a bug report reference here:

I can confirm. The Shkval display is completely useless as you can't really see anything from a mystique glare, even though in reality it has a glare shield around it and even though, in my case, the sun is shining from above. At some 15km distance I can see nothing on the screen - zooming in through the HUD is more beneficial.

This part applies to DCS? If yes, does this mean that the lock would have worked if I moved the scan zone to center?

Yeah some things are better and some worse in DCS than the real airplane, but that's not the point. The issue is that it can't lock, but it can detect. There's no max detection / max locking distance for the EOS. Real EOS can track up to 15km in a look up, ie. against the sky.

Was this noted some where? I could not find it the change log.

The other day I could not achieve a lock using EOS on a high and cold M-2000C. There was a strong return (4 bars), but the system could not lock the target. I am not able to provide the track as it's corrupt for some reason. This happened in multiplayer. First attempt to lock: Last attempt to lock: Outside view: P.S. Mirage was accelerating through trans-sonic speed range, so I am fairly confident he had his burner on.

I haven't played the mission, but what is the target's speed? Su-27/33 reticle used to start jumping around at high speeds.

I will send you a mesaage on Discord. Sorry, there's no way tonight

If it makes you feel any better, MiG-29 has the same thing. At high speeds, its roll-rate drops significantly. It's what happens in real life also.

There's no specific day, we usually text each other on Discord when ever available, but it's almost always after 20:00 CET.

My self and one other person fly quite often Su-27 and we don't suck too bad either (10 yrs in the Flanker). We are Europe (CET) based. Pop me a message if you are interested.

It should be this one here: Would be amazing if they shared this publicly with the rest of us.

Unless I missed something, we've already concluded (here on forums), that the Flanker is slower to accelerate than a heavier RL Su-30 in that acceleration video, so yes it is underperforming, it's just a question by how much. Since DCS Su-27 is capable of reaching above M 2.0, I would guess that the rate at which engines produce max thrust is the issue, and not the available thrust it self.

This is why FC3 jammers have a "warm up" period.

Also it looks like it's coming from breaking the sound barrier and not from maneuvering.