AeriaGloria

Yeah, Mi-8 manual says the same thing. So does Ka-50 manual. It seems like from the crash that I linked, the Russian got complacent and tried it with Mi-28 and small salvos and got punished for it. I wish the video of it was still around, but they weren’t doing large salvos. Maybe 2-3 small pair launches, then crash I would be more surprised what you are trying to do with rockets below 100 kmh? They aren’t very accurate or have good range in a hover, and can’t use the Mi-24s amazing speed

Human gunner? As human I have no issue moving sight. There is 10 second delay after turning on observe doors before gyro spins up and you can move the sight

No, just not designed for night flying. Perhaps the bright - sim switch by the top of the switches by your left shoulder, it is next to buttons to make Ri-65 Rita repeat or test herself. Those usually dim or brighten warning lights slightly, but don’t think it would affect things As you said, you would have to turn the whole thing off. I’m sure in reality they would need to use stickers or replace the light with a filter, but the amtough answer is whe it was designed in 1972-1974, it was simply not made for night ops

It’s meant to be used zoomed in, but as you figured out can be used either way. Just not ideal, it’s meant for ranging while targeting for ATGM attack, which you do in narrow FOV (7 degrees) why you say that? At 22 degrees?

Here is a track. I tried to start various dives/climbs, and enabled roll/pitch and altitude channel when only at a stable pitch, trying to minimize as much pitch channel movement as possible from attitude hold/compensation sensors From 150-300 kmh, could not see any noticeable change. Perhaps it is too small to see or the test isn’t correct, but I expected it to be noticeable since Mi-8/17 documentation including ED manual says speed hold should be good for +/-10kmh holding, and for Mi-24 this value is +/-5 kmh. In Mi-24’s case, the speed hold causes the pitch channel to deflect 100% at just a +/-6.6 kmh difference from the speed it’s turned on at. Most other channels between Mi-8/24 appear to be identical, roll channel attitude hold holding a 12.5 degree difference from set attitude, compensation sensors using 40% lateral cyclic to create 100% deflection at attitude turned on, and altitude channel causing a 100% deflection when only a 10m difference from initialized altitude, yaw channel heading needing a 7 degree difference for 100% deflection. The largest outlier being pitch attitude hold which is 3x more aggressive in Mi-24, 5 degrees vs 15 degrees. But its compensation sensor is also identical between Mi-8/24, causing 100% pitch channel deflection for 50% stick movement. So for speed hold, I expected if not a similar value, to be within a similar ballpark. Here is a track kzspspeedhold.trk

Interesting, I’ll try it out

Also, if you notice, the gap in the central crosshairs (where missile is guided) is 0.5 mils, same distance as the height marker for a 2.5m tall target 5 km. So you can use the gap also for 5 km range ID on a 2.5m talk target Also. The plus signs (“+”) around the sight are 0.10 mils high and wide. So if the 2.5m talk target covers the top half or bottom half (0.5 mils), it is at 5 km. And if the 2.5m target covers the whole cross, it is at the half the distance, 2.5 km, which is your optimum range for accuracy and avoiding gun fire. Yes, sometimes you will have to move the sight around to get an accurate range finding. This is also why I like to use the crosses below it, it is closer to center crosshairs, and at long range you often want the missile to fly slightly above the target to make sure it’s smoke doesn’t obscure your view, then lower the crosshairs on target after 2-4 seconds. The sight display and the controller you used is basically taken from an IFV/APC, has about similar zoom as a good tank sight and has equal stabilization as pre modernized T-72. So seeing how people aim in tank games like steel beasts might help, but as Miki said, no need to be exact. Your Shturm/Ataka will fly okay from low height and speed up to about 6-7 km. Use it enough, and you will be able to “feel by eye” without needing the height markers so much.

Anyone got speed hold to work at any time? I know it is intended to engage at the same time as altitude hold, and manuals have it supposedly being effective enough to hold you within +/-10kmh However, if I taxi along a runway, keep all my controls the same, but change speed with Wheel brakes and/or collective, I cannot get pitch channel to move even after a 100 kmh speed difference I know it uses the pitch channel, and the pitch channel is also influenced by cyclic movement from the compensation transducers, so I performed my tests engaging altitude channel when my cyclic was in the needed position and not moving it. I can upload a track shortly, but wanted to see if anyone else had this experience or if it is a long known missing feature

Not sure what you’re posting a log for or what your title means, but you might have better luck in the Russian forum Не знаю, для чего вы публикуете журнал и что означает ваш заголовок, но на русском форуме вам может повезти больше.

No. If you’re using NVG, it’s basically a “feature” to have to fight to anything at night. Would be nice as an option. Just can’t expect too much at night

That being said, always thought it would be fun to have the fire warnings actually transmit over radio

If you mean in game audio messages, I do not know, but I believe most sounds are encrypted anyways. If you mean the list of audio messages translated in Cryllic/English/Spanish I’ve given, I have a folder in my phone where all my Mi-24 material is organized

Control helper option will only harm you Pedal trim won’t hurt you by fighting autopilot, in fact you can set Microswitch to also trim pedals For maneuvering flight 99% of the time I suggest either keep Yaw channel off to keep it simple, or keep Microswitch pressed to keep it in dampening/stabilization mode (you can use toggle or momentary bind). I set my Microswitch logic to “automatic off,” so I only have manual control instead. By default your Microswitch logic is in “disable by return to center,” where Yaw channel is in heading hold when pedals are within 9% of center or last trimmed spot. But since in helicopters sometimes you need to turn with pedals close to center, it will still mess you up unless you use Microswitch bind, go to “automatic off” for manual Microswitch control, or turn Yaw AP I like the effect of yaw channel with Microswitch pressed becuase it is in a “stabilization mode” that helps you maneuver smooth, but most people will not even notice it and can just keep Yaw AP off until you want to fly straight if you want to keep it simple

That is rotor pitch, not wash out/twist where the pitch of the blade changes along its length

I see, there is a table for bomb drop from pilot seat, but it is very limited due to only 17 degree depression of ASP-17V pipper and no timers the Mi-24P with laser sounds great. Apparently the laser had a radiation marker in the second cargo cabin window it was mounted on, but I have found no pictures of it or mentions other then Afghan accounts, and no mentions of what happened to them or where they are now. So while it may have existed. I doubt it could ever be implemented in DCS as we have nothing more then recounted memories as far as I know

According to tables Gsh-23 does have larger bullet drop then YakB (YakB does have higher muzzle velocity),but I have no idea what you mean about it having shorter range then YakB In the manual documentation for Mi-24V, it is recommended for operator to not open fire until around 1-1.3 km. The Gsh-23 also has HE shells that are useful at long range where the AP/API 12.7mm shells of YakB would lose their effectiveness from slowing down In addition, the manuals for Mi-24 stop at 2 km for YakB, and stop at 3 km for Gsh-23 the same as most rockets and 30mm armament. Better ballistics? Sure. Gsh-23 being shorter range than YakB? I don’t believe that. If you mean accuracy, Gsh-23 is a relatively accurate gast gun and the YakB is a Gatling gun with quite large spread and rate of fire to saturate an area. If you are having trouble hitting things with Gsh-23 with Mi-8/L-39 from long distance I don’t blame you, but does not make it shorter range then YakB In the end, we have BlackShark, if ED ever wanted to make an upgrade/separate module it shouldn’t be difficult to make both V and VP options, as they should only differ in the turret. The KPS-53AV is limited to 2 km range either way These same Afghan war accounts we are reading here have a passage where it is said “GUV pods were taken only under threat of punishment” and that the Gsh-23 was an extremely welcome upgrade, able to destroy targets that even S-5 couldn’t As for bomb sight using KPS-53AV, luckily I am not the one in need of convincing but maybe if official documentation won’t convince zero crash, war memoirs might

It’s been two years, it’s not a directly important piece of equipment to the to ground mission, I think we’ll be okay waiting for them to put all their effort into the most realistic implementation For all we know, SPO-10 new modeling could come out next patch. The newsletter didn’t say it was far away, but mentioned it with Petro updates we got last patch

I reported similar issues here https://forum.dcs.world/topic/299549-rwr-signal-frequency-for-lockscan-modes/#comment-5139568 https://forum.dcs.world/topic/299547-rwr-tone-does-not-change-with-range/#comment-4956255 In a newsletter a few weeks ago ED announced that they are Re coding SPO-10 to be more realistic, adding many new features that haven’t been in DCS before. So it’s safe to say that you don’t need to worry, soon we will have the most realistic SPO-10 in a consumer simulation “The updated SPO-10 RWR will consist of four channels with completely independent processing, the same as in the real system. The radar detection calculations are physics based, they calculate the radiation pattern of the transmitting source, the sensitivity of the receiving antennas, and the transmitting power of the emitter. This translates to detecting low-power radar emitters and shorter range and vice versa. Detection range will also vary based on bearing to the emitter source. For certain radars, the range can also be judged based on how frequent the detections are. The system will now only detect emission sources within the operating frequency range of the RWR. For instance, early warning and search radars and some other radar types will not be detected.”

Anything I can read about the banning of large caliber rockets? I know they restricted use of S-24 on Su-25 for smoke ingestion, and that S-25 rocket on Mi-24 didn’t work out, but haven’t heard much else about the banning of large caliber rockets

I don’t know what you mean about 160 kmh, but from 200 kmh to max speed there is a pitch up behavior called “Podkhvaht (pick up in Russian).” If you exceed the G limits set in the manual, it basically causes an aggressive mush/rotor stall that requires you to move cyclic forward and reduce collective 1-3 degrees to recover It is described in many army manuals, but you can get the gist of it from this video It basically happens when teaching 0 AOA or positive AOA at high speeds, which causes up flow through the rotor disk and thus causes a rotor stall. Coincidentally, to Create maximum lift the wings are installed at a 19 degree angle, and stall at around the same angle. So when you hit this 0-positive AOA region, the wing also stalls. If you notice, the wing isn’t directly below the rotor, but behind it. This means that as it creates lift, it also creates a nose down force that helps you need less forward cyclic in forward flight. But when that wing stalls, the nose down force it was creating mostly goes away, increasing the pitch up tendency of the now stalling rotor The manual places a heavy speed restriction on this, the faster you are the more you should limit G. In my experience in DCS the speed you are doesn’t effect the G that this effect happens, but does increase how sever it is and how much effort it takes to recover At low weights and altitudes this is around 1.8 G. If extremely lightweight and near sea level 2 G is the absolutely maximum you could ever pull without this “cobra” effect happening As you go to 1000m, you might be limited to 1.6 G, and once you are at 2,000m or above more like 1.4 G. If you are fully loaded (11,500 kg), even being low to the ground you are often limited to 1.6 G just out of weight. It has been tuned recently and is less aggressive, but still happens around these G levels. While the normal reaction is cyclic forward, and you do need that, reducing collective has the greatest effect as it increases the angle the rotors can be without stalling. You will often notice just a 1-3 degree decrease in collective will snap the nose back down. As a preventative, you can even reduce collective beforehand. At max collective it is worst, 12-14 degrees is good middle ground, and below 10-11 degrees the effect starts to stop being sudden and basically goes away unless you force it. So keep an eye on G meter and collective pitch, You will hear the blades start to flap as this occurs It is good to be conscious that wether you are in a fixed wing or rotary wing, in a level turn your G has a direct relation with bank angle. If we consider 2 G the limit, this means that at low altitude and weight your absolute bank angle limit in a level turn is 60 degrees. At more medium weights and low altitude, for a 1.8 G limit, you are closer to 55 degree bank angle limit. At higher altitudes and weights, where you are limited to 1.4-1.6 G, you may only be able to bank 45-50 degree in a level turn. It is for this reason there is a 45 degree bank angle limit in the manual for peacetime and the aerodynamics section warns that any level turn with bank angle above 45 degrees begins to become unsteady and hard to perform. I hope that helps, cheers

Not a bug, it was in the change log when introduced. Under 100 kmh, the smoke ingestion from rockets created a chance of engine compressor stall. It won’t happen for every S-5/S-8 shot, but if you use volleys or larger rockets it certainly will. It’s also implemented on Ka-50/Mi-8. Just ascending can reduce it, but really you need to be above 100 kmh to stop it. This is reflected in real life documented that gives speed limits for every rocket launch of 100 kmh to max kmh. It even caused a Mi-28N crash in about 2007-2008 when they were firing S-8 at about 50-100m altitude, had compressor stall, and crashed into the ground. https://aviation-safety.net/wikibase/66316 https://russiandefpolicy.com/tag/budennovsk/

I don’t see how a laser could be added, but there is a few real life options that I would love to see implanted It is not graphically shown in the module, but in reality there is a SPU-8 intercom on the cabin roof and a ASO-2. Dispense button by the door on the left. I always thought it would be cool to have such options in cargo cabin/door gunner seat, but I understand why they were not implemented

The top chart is very symmetrical weapon loading, for S-24 compatibility for example, go from S-24 vertically/horizontally (to it choice) until it intersects with the weapon you desire to load it with. For example where S-24 and GUV intersect, it says in orange “Only GUV.” You can notice that, GUV pods only work with other GUV pods. They are not compatible with anything else on the 5 main pylons. The outer wingtip pylons that are only for ATGM are compatible with anything, loadout restrictions only apply to pylons 1-4 that are hanging under the wing. UB-32 and bombs have similar restrictions, becuase UB pods use a bomb rack. This is why S-8 pods have less restrictions. S-13 doesn’t work with anything You can branch out from pre set loadout to a certain degree, but you will need to be aware of these restrictions These charts are from the English quick start guide, and there is an English translation of the Russian guide on user files that has some more information also

Sure of course. Honored to have someone with your experience here. Hopefully giving the trigger conditions for the most common ones above helps. Usually those “check electrical panel (rotor rpm below 88%)” and the “lower gear (IAS below 70 kmh and below set limit radar altitude)” When you first turn it on the sound you hear is usually the hydraulic low pressure alarm. And Atleast with the fire alarms, you have a panel telling you exactly what’s on fire atleast. Sometimes I like to turn my tank 1/2 pumps on/off at shutdown just to hear the audio warning for it or jiggle the controls to hear low hydraulic pressure alarm I’m sure there will be a English option eventually Sometimes I also put the Russian translation into google and hear the TTS of it, so I can more easily recognize the alarm when it comes on

We you can piece together the important/common ones, the ones for oil pressure/metal chips/vibration never happens usually If rotor rpm is at 88% or below: “attention to electrical system panel” If below 70 kmh IAS, under set limit altitude of radar altitude, and gear is up: “lower gear” warning plays If below 240 L in tanks 1/2: “low fuel (toplivo) remaining” If tank 1/2 pumps are turned off/fail: “service tank pump failure” If test button is pressed: “audio warning system operational” If fire” fire aboard helicopter number (bort), attention to annunciator,” then you get warning for specific component that is on fire also Hydraulic system below certain pressure, can be triggered by moving controls after shutdown: “main/aux hydraulic system failure” Here is a possibly incomplete list: FIRE ABOARD HELICOPTER No... ATTENTION TO ANNUNCIATORS (БОРТ N.... ПОЖАР. ВНИМАНИЕ НА ТАБЛО); DANGEROUS VIBRATION OF LEFT ENGINE (ОПАСНАЯ ВИБРАЦИЯ ЛЕВОГО ДВИГАТЕЛЯ); DANGEROUS VIBRATION OF RIGHT ENGINE (ОПАСНАЯ ВИБРАЦИЯ ПРАВОГО ДВИГАТЕЛЯ); MAIN HYDRAULIC SYSTEM FAILED (ОТКАЗАЛА ОСНОВНАЯ ГИДРОСИСТЕМА) AUXILIARY HYDRAULIC SYSTEM FAILURE (ОТКАЗАЛА ДУБЛИРУЮЩАЯ ГИДРОСИСТЕМА); EMERGENCY FUEL RESERVE (АВАРИЙНЫЙ ОСТАТОК ТОПЛИВА); LOW OIL PRESSURE IN GEARBOX (МАЛО ДАВЛЕНИЕ МАСЛА В РЕДУКТОРЕ); SERVICE TANK PUMP FAILURE. CHECK FUEL RESERVE (ОТКАЗАЛ НАСОС РАСХОДНОГО БАКА. ПРОВЕРЬ ОСТАТОК ТОПЛИВА); AUXILIARY SYSTEM OPERATES (ДУБЛИРУЮЩАЯ ГИДРОСИСТЕМА РАБОТАЕТ); LEFT ENGINE FIRE (ПОЖАР В ОТСЕКЕ ЛЕВОГО ДВИГАТЕЛЯ); RIGHT ENGINE FIRE (ПОЖАР В ОТСЕКЕ ПРАВОГО ДВИГАТЕЛЯ); FIRE IN MAIN GEARBOX COMPARTMENT (ПОЖАР В ОТСЕКЕ ГЛАВНОГО РЕДУКТОРА): FIRE IN COMPARTMENT OF APU AND TANK No.3. (ПОЖАР В ОТСЕКЕ АИ-9В, БАКА Ne 3); LOW OIL PRESS. LEFT ENGINE (ДАВЛЕНИЕ МАСЛА МАЛО. ЛЕВЫЙ ДВИГАТЕЛЬ ); LOW OIL PRESS. RIGHT ENGINE (ДАВЛЕНИЕ МАСЛА МАЛО. ПРАВЫЙ ДВИГАТЕЛЬ); CHIPS IN LEFT ENGINE OIL (СТРУЖКА В МАСЛЕ ЛЕВОГО ДВИГАТЕЛЯ); CHIPS IN RIGHT ENGINE OIL (СТРУЖКА В МАСЛЕ ПРАВОГО ДВИГАТЕЛЯ): CHIPS IN TRANSM OIL (СТРУЖКА В МАСЛЕ ТРАНСМИССИИ); ATTENTION TO ELECTRIC SYSTEMS PANEL (ВНИМАНИЕ НА ПУЛЬТ ЭЛЕКТРОСИСТЕМ): REPORTING SYSTEM IS OK (РЕЧЕВОЙ ИНФОРМАТОР ИСПРАВЕН).