OpticFlow

The radar on that picture is Cyrano II from Mirage IIIE, the label on it is wrong. Cyrano IV on F1 looks like this:

According to some sources, the new engine is used on P2 and later models: https://www.af.mil/About-Us/Fact-Sheets/Display/Article/104557/aim-9-sidewinder/ http://www.ausairpower.net/TE-Sidewinder-94.html

Both the AIM-9P and the AIM-9P5 have incorrect values for engine thrust and time. In DCS, AIM-9B, AIM-9J and AIM-9JULI all have 2.2 seconds boost stage time and 17 800 newtons thrust. The AIM-9P and AIM-9P5 models also use the same engine (Thiokol Mk.17) and one expects to see the same stats, but instead they have 3 seconds and 18 800 newtons thrust, which is 44% more total impulse. Correction: The AIM-9P5 uses different engine: Hercules/Aerojet SR.116, but I couldn't find any stats for it. For reference: 1. Description of the Sidewinder variants: 2. The in-game stats: https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/rockets/AIM-9P.lua ModelData = { 58, 0.35, 0.04, 0.08, 0.02, 0.05, 1.2, 1.2, 0.5, 0.4, 1.2, 0.29, 0, -1, -1, 3, 0, 0, 0, 1000000000, 0, 0, 8, 0, 0, 0, 0, 0, 0, 18800, 0, 0, 0, 0, 1000000000, 30, 0, 0.5, 1000000000, 1000000000, 0, 30, 0, 1.19, 1, 2, 0, 0, 0, 0, 0, 9000, 4000, 4000, 0.2, 1, 1.4, -3, 0.5 }, https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/rockets/AIM-9P5.lua https://github.com/Quaggles/dcs-lua-datamine/blob/master/_G/rockets/AIM-9J.lua ModelData = { 58, 0.35, 0.049, 0.082, 0.01, 0.001, 0.55, 0.8, 2.5, 0.8, 1.2, 0.13, 0, -1, -1, 2.2, 0, 0, 0, 1000000000, 0, 0, 8.45, 0, 0, 0, 0, 0, 0, 17800, 0, 0, 0, 0, 1000000000, 40, 0, 0.8, 1000000000, 1000000000, 0, 30, 0, 1.2, 1, 2, 9, -11, -1.4, 10500, 2800, 17000, 5500, 6700, 2000, 2500, 0.55, -0.01, 0.5 }, The key to read the ModelData parameters: ModelData = { 58 , -- model params count 0.35 , -- characteristic square (характеристическая площадь) -- параметры зависимости Сx 0.04 , -- Cx_k0 планка Сx0 на дозвуке ( M << 1) 0.08 , -- Cx_k1 высота пика волнового кризиса 0.02 , -- Cx_k2 крутизна фронта на подходе к волновому кризису 0.05, -- Cx_k3 планка Cx0 на сверхзвуке ( M >> 1) 1.2 , -- Cx_k4 крутизна спада за волновым кризисом 1.2 , -- коэффициент отвала поляры (пропорционально sqrt (M^2-1)) -- параметры зависимости Cy 0.5 , -- Cy_k0 планка Сy0 на дозвуке ( M << 1) 0.4 , -- Cy_k1 планка Cy0 на сверхзвуке ( M >> 1) 1.2 , -- Cy_k2 крутизна спада(фронта) за волновым кризисом 0.29 , -- 7 Alfa_max максимальный балансировачный угол, радианы 0.0, --угловая скорость создаваймая моментом газовых рулей -- Engine data. Time, fuel flow, thrust. -- t_statr t_b t_accel t_march t_inertial t_break t_end -- Stage -1.0, -1.0, 2.2, 0.0, 0.0, 0.0, 1.0e9, -- time of stage, sec 0.0, 0.0, 8.45, 0.0, 0.0, 0.0, 0.0, -- fuel flow rate in second, kg/sec(секундный расход массы топлива кг/сек) 0.0, 0.0, 17150.0, 0.0, 0.0, 0.0, 0.0, -- thrust, newtons

Target is probably the one marked with 1 on the HUD, well below the horizon, so seems like it does loft.

Ah ok. Then maybe use a steeper dive angle (it would give a flatter trajectory)?

Once you've found out a suitable combination of dive angle, speed and altitude, you can get the gunsight depression by going into active pause at the release point. Once in active pause, you can pickle the bomb, which would fall down to the ground and explode while your aircraft would stay frozen in the air. You could observe the bomb impact point and adjust the sight to match it.

It still works, but only the ground attackers (A-10A, Su-25(T)) support it.

Yes, it's still there.

Apparently not while it's tracking with the IRST. It's described in

If you press the radar toggle button while tracking a target with IRST, that would IFF the target without actually alerting it on RWR.

Rejoice, the 530D has been improved in multiple aspects,

True that, just added two PL-12 to my MIG-29S for the experiment! @pauldy find your Su-27.lua in Saved Games\DCS.openbeta\MissionEditor\UnitPayloads and add whatever missiles you like to the loadout.

Btw the J-11A has the R-77, no need to modify anything to use it.

Generate performance charts (or at least the data series in a convenient format) from the in-game flight characteristics of the player controlled aircraft so that we can compare them with each other and know their relative strengths and weaknesses in flight. For example: Sustained turn rate and radius vs. speed Max. climb rate at given altitude vs. speed Speed range vs. altitude Acceleration in level flight vs. speed Fuel consumption rate vs. speed

Excellent work, thank you very much for this mod!

Just saw this chart you've posted few years ago, Seems like there is a long way to go from the 33 deg on the indicator to the stall AoA (the solid black line on the first chart), especially at slower speeds... Seems to confirm the article in the original post. Or is that only MiG-21F too?

Are we playing the same game? After AIM-9X and R-73, the Magic II is the best turning short range missile in the game, has better flare resistance than the R-73 and probably same as AIM-9M. It's range seems more limited than those other two on paper but I never had it run out of juice even when I get impatient and launch it at longer than the indicated max range. In dogfight range the missile is a killer, almost always scored a hit when I launched it.

More than 400 "fatback" Izd. 9-13 were delivered that didn't have R-77 capability. Only 16 Izd. 9-13S with R-77 capability were delivered.

Interesting article. But the DCS MiG-21bis doesn't match the stall AoA described there. It stalls at exactly 33 degrees indicated regardless of the speed. Just tried flying it in circles at 350 km/h on afterburner (on deck). Slight wobble begins at 28 degrees indicated. Sudden stall at exactly 33. According to the article it should stall at more than 10 additional degrees at that speed.

One smooth landing --

I bought the complete FC3 pack because I wasn't sure what I was going to fly, but I was imagining the Su-27 and the F-15C. About a year later, I'm flying mostly the MiG-29 and occasionally the Su-25. So my advice is to wait for the 50% discount and get the entire pack.

Thanks for the info! Seems like the range scale of the locked target is in KM, which means there is a bug in the current implementation because the indicated range is incorrect (around 20% more in my example).

I couldn't find info in the manual what the units on the horizontal scale in the radar scope mean, but they look pretty close to KM. However they are slightly off, is that bug or the scale means something else? Here is a screenshot to illustrate what I mean: Target is locked, distance to target from the in-game labels is 8.7 km, distance mark in the scope is slightly more than 10, say 10.5 units.

Would be nice to link the radar and the RWR screens brightness to the HUD brightness, like on the MiG-29. That way we can dim them all for night flying or brighten them up during the day.

It works exactly like this in the game. After take off, level out, engage AP Attitude Hold and proceed to do your flying. The plane goes where you put the velocity vector (on the HUD) and you don't need to touch anything besides the stick X/Y axes. Don't touch the trim buttons at all. You could also use this mode for air refueling, it's smoother with it on.