AeriaGloria

Yes that would make sense. I have noticed the dynamic “floating pipper mil seperation” changing with range since then. Good find. I’ll take a look at the mission

After a quick test you are correct. It seems all milliradian function was removed. In order to have your range CCIP pipper have the correct miliradians for stadiametric range finding, you have to actually dial in the correct range and meter distance. i presume this helps alleviate some guesswork in real life. But it is interesting and took me a while to figure out how to make it work. I wonder how long it has been this way?

I will get back to you when I have tested. Becuase before this patch it should have the two behaviors depending on auto/man switch of the sight, or perhaps I have it wrong and it’s the auto range switch on the weapons panel that does it

Have you tried flipping the sight to manual mode? Becuase only then does it become direct mil setting. There is two distinct modes of operation here depending on the position of the manual/auto switch for ASP-17. One that allows you to do stadiametric range finding from 0-3500m when switch is in manual, and when in auto as you say is more of a meter adjustment.

It is just a multipurpose gauge that says Km/base in case it is used in an aircraft that needs it’s for km and not base/span. The knob adjusts the mil seperation of the floating pilot pipper lines. In manual mode it will be 1:1 mils from gauge to sight. In Auto it will automatically adjust the mil seperation of the floating pipper lines so that at range it should frame your target. For example, if I set my base range to 7 mils, length of a BTR-80. In manual mode there will be a 7 mil gap in the middle of the floating pipper crosshairs. In auto, it will change size with range in such a way so that if I attack a BTR-80 from the side, and range is accurate, the pipper should perfectly frame the BTR-80. One way this can be used, is to see large errors in range due to terrain elevation delta messing up the CCIP. So you can see if it’s range is too short or long, and have an additional visual cue for range in addition to the range arc from 12 to 3 o’clock on the the pipper. So, ignore the “Km” label, as it only controls mil separation of floating pipper

Have you tried a postion to the left/right? There have been issues where the stops on the dial don’t totally align with the needle

If your gyros are broken, your Raduga system must be off for 3.5 minutes to fully settle gyros. It will then need to be turned on again and wait another 3.5 minutes

It should be the same for Shturm/Ataka, periscope must be pointed no more the. 17 mils from boresight. If it’s been changed it’s not accurate

It won’t just fire when you get time? Isn’t “little left/up/right/down” just a recommendation to have a clear path for the missile?

So had you taken a hit and had your pylons damaged?

Yes, by turning while guiding a missile with 10-25 degree bank you can evade a lot of shots. The manual recommends don’t turn more then 20 degrees in bank when periscope is on. I have had some issues when banking at 25-30 degrees so I stay at 20-25 max when periscope is on. If your gyros are screwed up indicators are the floating reticle not being centered when gyros first spin up after opening doors. And when Petro is searching you often can’t scan left and right but only in one direction. So, it’s completely normal and expected gameplay to have to hit the down short buttton for the Petro menu to close the periscope as soon as possible so you can properly evade by banking more then 25-30 degrees The pitch limit is also 25-30 degrees, so watch that

Why do you think the same isn’t true for the 29? Just becuase there hasn’t been a mid air collision that took off a wing and the pilot landed safely doesn’t mean it’s just as capable in that respect. It should be even more capable considering the body lift part of the design. I think the body contributes something like a quarter of the lift. For the FC3 Su-27, it is known that it actually has too much drag, and under performs in sustained turns for instance As far as this thread is concerned I wouldn’t pay it much attention. If you look at OP it seems they didn’t take into consideration that it is a twin engine airplane. And did their napkin math using only one RD-33 engine. This being the internet those that are well aware it has two engines we’re happy to argue about MiG-29 thrust when in fact there has never been an issue or reported bug with its thrust that has to do with its power since the new flight model (that I can remember being an issue)

This can sometimes happen if your wings are shot. If so you will see visual bullet holes in the wing. When pylons 1/4 (ATGM 5-8) don’t work that can be confirmed by the pylon loaded lights on the weapons penal.

I have only noticed flares even when I took chaff. But maybe I’m missing something. It’ll flare when a MLRS passes you, don’t think he cares about guidance much

This manual is unclassified and open for public use, from the Cold War Air Musuem for their Hinds and acquired by FOIA. It has addendums for Mi-24P, but is very maintenance/technical focused. For example it is very detailed on describing the electric system https://mudspikefiles.s3.dualstack.us-east-1.amazonaws.com/original/3X/7/a/7ab064a7f951b9f0325354f257f5e58c571936d6.pdf

Turn off control helper, it is interfering with your inputs

Unfortunately only have electronic copies. Have thought of printing them out for personal use however. I can say from reading the whole thing that it is not much different from any other Mi-24 manual. There a gun-specific warnings regarding firing limitations, and of course weight is different and all, and there is no sections on how to use KPS-53 gun turret sight system.

Uboats has already said they would do it if possible, but information on its very complex guidance and triple seeker system is very hard to get and model. Hopefully it may be a possible upgrade one day, would make a second use for the AKG pod

Sent a message

The first mission seems very difficult with the new weather. I just skipped it, would be nice to have it fixed

Yes, they are in the rocket lofting chapter of my weapons guide, find it here. There are tables for the S-5KO and S-8KOM. Since 8OFP2 was never used operationally and OFP tables aren’t in the wild, it is up to experimentation. Using the same techniques outlined for 5KO/8KOM lofting I wrote some basic numbers for S-8OFP2 that should get you in the right ballpark. Since they are the only true HE rocket, they are your best bet and despite the weight have more range lofting then the others.

I love you Harli but maybe give it a break. ED has made it clear the intended functionality in DCS is to have it the way it is but with not screwed up Petrovich text. Wether the pit is compatible in real life or not

Sorry I meant to also add picture of the note on the front page of the repo You can always pull the numbers from the repo yourself, I can’t find ED R-3S but I can find Magntiude 3 R-3S. Cx_pil = 0.001, D_max = 7600, D_min = 900, Damage = 26.75, Diam = 127, Escort = 0, Fi_excort = 0.5235, Fi_rak = 2.6175, Fi_search = 0.08725, Fi_start = 0.2094, H_max = 18500, H_min = 100, H_min_t = 10, Head_Form = 0, Head_Type = 1, KillDistance = 5, Life_Time = 30, M = 75.3, Mach_max = 2.2, ModelData = { 58, 0.35, 0.049, 0.082, 0.01, 0.001, 0.55, 0.8, 0.8, 0.7, 1.2, 0.13, 0, -1, -1, 2.8, 0, 0, 0, 1000000000, 0, 0, 7, 0, 0, 0, 0, 0, 0, 13570, 0, 0, 0, 0, 22, 21, 0, 0.5, 1000000000, 1000000000, 0, 30, 0, 1.19, 1, 2, 6, -8, -1.1, 10000, 2700, 14500, 4500, 7500, 1800, 2500, 0.55, -0.01, 0.5 }, Name = "Redacted", Nr_max = 16, OmViz_max = 0.349, PN_gain = 3, Range_max = 15400, Reflection = 0.0182, SeekerCooled = true, SeekerSensivityDistance = 7500, X_back = -1.374, Y_back = -0.081, Z_back = 0, _file = "./CoreMods/aircraft/MiG-21BIS/Entry/Aw", _origin = "MiG-21Bis AI by Magnitude 3 LLC", _unique_resource_name = "weapons.missiles.R-3S", category = 4, ccm_k0 = 0.66, display_name = "R-3S - AAM, IR guided", exhaust = { 0.9, 0.9, 0.9, 0.5 }, name = "R-3S", shape_table_data = { { file = "r-3s", fire = { 0, 1 }, index = "Redacted", life = 1, name = "r-3_s", username = "R-3S" } }, sigma = { 3, 3, 4 }, t_acc = 2.45, t_b = 0, t_marsh = 0, user_name = "R-3S - AAM, IR guided", v_mid = 400, v_min = 140, warhead = { caliber = 127, concrete_factors = { 1, 1, 1 }, concrete_obj_factor = 0, cumulative_factor = 0, cumulative_thickness = 0, expl_mass = 10.7, mass = 11.77, obj_factors = { 1, 1 }, other_factors = { 1, 1, 1 }, piercing_mass = 2.354 Here is R-13/13M1, files are identical Cx_pil = 0.001, D_max = 15000, D_min = 300, Damage = 28.05, Diam = 127, Escort = 0, Fi_excort = 0.698, Fi_rak = 2.6175, Fi_search = 0.08725, Fi_start = 0.2094, H_max = 20000, H_min = -1, H_min_t = 1, Head_Form = 0, Head_Type = 1, KillDistance = 5, Life_Time = 60, M = 90.4, Mach_max = 2.5, ModelData = { 58, 0.35, 0.1, 0.1, 0.02, 0.04, 1.2, 1.2, 0.8, 0.7, 1.2, 0.29, 0, -1, -1, 5, 0, 0, 0, 1000000000, 0, 0, 6, 0, 0, 0, 0, 0, 0, 8280, 0, 0, 0, 0, 61, 60, 0, 0.5, 1000000000, 1000000000, 0, 30, 0, 1.19, 1, 2, 5200, 0.63, 0.53, 0.75, 59, 1, 5000, 1, 0.2, 0.6, 1.4, -3, 0.5 }, Name = "Redacted", Nr_max = 35, OmViz_max = 0.43625, PN_coeffs = { 2, 4000, 1, 15000, 0.3 }, Range_max = 20000, Reflection = 0.0182, SeekerCooled = true, SeekerSensivityDistance = 7500, X_back = -1.396, Y_back = -0.081, Z_back = 0, _file = "./CoreMods/aircraft/MiG-21BIS/Entry/Aw", _origin = "MiG-21Bis AI by Magnitude 3 LLC", _unique_resource_name = "weapons.missiles.R-13M1", category = 4, ccm_k0 = 0.66, display_name = "R-13M1 - AAM, IR guided", exhaust = { 0.9, 0.9, 0.9, 0.5 }, name = "R-13M1", shape_table_data = { { file = "r-13m1", fire = { 0, 1 }, index = "Redacted", life = 1, name = "r-13_m1", username = "R-13M1" } }, sigma = { 3, 3, 3 }, t_acc = 5.1, t_b = 0, t_marsh = 0, user_name = "R-13M1 - AAM, IR guided", v_mid = 460, v_min = 140, warhead = { caliber = 127, concrete_factors = { 1, 1, 1 }, concrete_obj_factor = 0, cumulative_factor = 0, cumulative_thickness = 0, expl_mass = 11.22, mass = 12.342, I won’t do R-27 as there are 4 variants, and R-77 also. But it’s easy enough to go to the datamine https://github.com/Quaggles/dcs-lua-datamine and get the numbers. Anything in new API is in missiles and old API in rockets, and some information won’t correlate between the two. And even for the rockets category many numbers like H-max and D-max are just estimates/encyclopedia things, and have no effect on performance.

If you read the notes here, https://github.com/Quaggles/dcs-lua-datamine Fi_rak is FOV of the seeker. The number is in radians. However as you see there is 4 different values starting with “Fi” that all relate to FOV. So I think what you’re seeing is the Fi_rak figure only needs to be set to 360 degrees (except for Magic 1)? And the actual FOV is represented through the other Fi figures All aspect detection only depends on two figures, “seeker sensitivity distance” which is the distance to detect a tail aspect Su-27 in MIL power, and “seeker cooled: true/false.” If seeker is cooled, then it acts as all aspect. Depending on seeker sensitivity figure, depends the range that lock-on occurs ( comparing seeker sensitivity and cooling to heat signature of target and any aspect modifiers on top of it) It seems you also mentioned that PL-5 has less drag then AIM-9M but I don’t think that’s the case. If you are looking at Cx_pil value, that value only controls that drag that the weapon causes when loaded on the airframe. The drag that occurs when the weapon is released is totally different, these numbers likely being in the model data string, which you can also decipher with the notes on the Quaggles GitHub repo page. You said you couldn’t find R-60, there are two, also, whenever warhead is predefined, it can be found in warheads section As you can see, magnitude 3 R-60 has cx_pil of 0.001, while ED one is 2.18, does it have 1/2000th of the drag? It’s becuase of the way the MiG-21 is coded, that every cx_pil of 0.001 adds a drag index of 1 to it. You can see other things like higher max G and warhead and higher countermeasure resistance that actually make the R-60 better then the R-60M within range. ED R-60M , Cx_pil: 2.18 D_max = 4000, D_min = 200, Damage = 8.75, Diam = 120, Escort = 0, Fi_excort = 0.79, Fi_rak = 3.14152, Fi_search = 0.044, Fi_start = 0.35, H_max = 20000, H_min = -1, H_min_t = 1, Head_Form = 0, Head_Type = 1, KillDistance = 3, Life_Time = 20, M = 43, Mach_max = 2.5, Nr_max = 30, OmViz_max = 0.611, Range_max = 12000, Reflection = 0.03, SeekerCooled = true, SeekerSensivityDistance = 10000, exhaust = { 1, 1, 1, 1 }, name = "P_60", sigma = { 3, 3, 3 }, t_acc = 5, t_b = 0, t_marsh = 0, Warhead: 3.5 kg Magnitude 3 R-60 Cx_pil: 0.001 D_max = 7200, D_min = 300, Damage = 15, Diam = 130, Escort = 0, Fi_excort = 0.698, Fi_rak = 2.6175, Fi_search = 0.08725, Fi_start = 0.349, H_max = 24000, H_min = -1, H_min_t = 1, KillDistance = 3, Life_Time = 23, M = 43.5, Mach_max = 2.5, Nr_max = 40, OmViz_max = 0.5235, PN_coeffs = { 2, 4000, 1, 15000, 0.3 }, Range_max = 11200, Reflection = 0.0182, SeekerCooled = true, SeekerSensivityDistance = 7500, ccm_k0 = 0.66, display_name = "R-60 - AAM, IR guided", exhaust = { 0.9, 0.9, 0.9, 0.5 }, sigma = { 3, 3, 3 }, t_acc = 2.5, t_b = 0, t_marsh = 0, user_name = "R-60 - AAM, IR guided", v_mid = 600, v_min = 200, expl_mass = 6,

Noticed the Raduga doors missing. Will get that a track/photograghy later