Tiger-II

https://www.flightglobal.com/defence/beijing-celebrates-new-year-with-jf-17-j-20-progress/135976.article

If you do actually own the product, then I'm sorry for assuming you to be another Jeff basher. The SD-10 discussion here has been pretty wild ever since release, not least because "Blue Air" pilots were getting their asses handed to them by the first properly modeled modern Red Air. The RADAR in the Jeff is based off the APG-68 (hint: the US helped them develop it before pulling out of the program). This is an even better RADAR than flown in the F-16 (APG-66). I would hope a modern fighter like the JF-17 had a much greater resistance to notching than you're suggesting.

JF-17 is awesome! Those double pylons are draggy, but if you're ready to fly a bit slower (as written above) she's a great aircraft. She's got longer legs than her fuel load suggests, as long as you keep out of AB! If you learn to manage your energy, she'll do more than she first appears.

I drag them to the deck and defeat them kinematically. Flying behind tall objects works pretty well, too.

Just add more route points? AFAIK there is no way to navigate to a route way point on a course except the course created between points. There is a bearing pointer on the HUD though, so you could fly that like you would a bearing pointer on a VOR.

True heading is entered in both modes, however if it is not entered in FAST during alignment, the alignment will be out when it enters NAV, and the system will drift much more rapidly. In GC mode it is required.

The default key is "T". The aircraft systems do not recognize smoke pods which is why you can't control them via the weapon system. You need to check: * Gear up * Aircraft not on the ground * System is in NAV * Master arm OFF

:( Been a while since I flew the Shark, but IIRC yes, it's the same. I'm not sure if it is correct for the Ka-50, but certainly for the JF-17 it seems wrong for the ELEVATION map to be all blue, as it gives zero indication of terrain height! The better question is: what does the real JF-17 elevation map mode look like? As written above, I'd expect either TAWS-style relative height coloring, or a map that looks like the elevation map in the mission editor (the TAWS presentation would be the most useful in this situation).

Even guessing somewhat accurately could be problematic, legally speaking, due to how US classification laws work. The guidance logic is, IMHO, more important than the raw missile physics. This becomes even more important when discussing SAMs, as they don't all just fly straight towards the target, and it consequently affects defence strategies and missile evasion.

Lighting has been OK for me, but no VR. I seem to recall there was an issue/technical reason for VR having that object you speak of. Try a forum search.

As well as motion, Deka are working with what they've got to bring their weapons as close as they can to accurate performance, even if it means bending the numbers to strange values. The end result is what counts.

In DCS I sometimes get a black square flicker in the top left of the picture, but this is related to my AA settings and happens with any module randomly.

Looks correct to me. The SMS stores page doesn't care for symmetry between different weapons, and as we don't have FBW in the roll axis, the FCC won't magically correct this for us. Welcome to manual trim!

It'll be something in DCS. Just because other software works doesn't mean this will. Does it happen with other *modules* is the more interesting question. If yes, then it's a DCS problem.

I think it might be this simple.

:thumbup: Best reply in the thread. I thought it was known that Deka are working with official sources? I guess not. Instead of asking Deka how realistic their data is, how about asking ED to fix their missiles? Even this would work as a temporary fix.

Why do I sense another Jeff basher? Was the RADAR in STT when you tried to break lock?

How do you mean? The current map is all blue, all the time, making it useless. It should be shaded different colors based on relative altitude, AFAIK. All blue is certainly incorrect.

Right now it's a beam-rider, which the real BRM-1 is *NOT*. This is the difference currently, for the reasons stated above.

Map draws based on strength of signal return. Buildings return strong signals, water will be pretty weak/weakest, so they range from bright green to black. The rest of the picture is interpretation by the human mind. GMT uses a filter. Static objects regardless of type will return a signal at a certain frequency range but parts of the signal will have doppler shift due to relative motion, so the RADAR will only show those areas. Most of the picture will be black with some noise. GM is like MAP but with a filter so the signal is reduced below the noise floor with only the stronger returns being painted. This is why some objects appear and others don't.

I observed a similar thing. This is a different problem from the elevation bug.

Change it to nose/tail. I seem to recall this is a bug of the weapon.

What you're looking at there is completely broken guidance logic.

Are you seeing the same thing?

:music_whistling: By posting it in the open they'll think it's lie and ignore it!