randomTOTEN

I've done some more experimenting, and thanks for being patient as I tried to help you. I think at some point in the development process, the flight model and stability systems of the Hind changed (I'm sure they have). What I think has happened is that the Hind begins the mission being out of trim for straight and level flight. I apologize for suggesting you weren't following the mission correctly, I think that might have been a replay issue (or it might have been an actual user error, you never answered if you fired a missile from the rear seat). I also asserted that we control a basic AI flight model when we are in the front seat. I don't think that's true anymore. I think the AI is using the same flight model we use in this case. When the lesson is unpaused, I believe the Hind is badly out of trim. This means that Petrovich does not have enough control authority to properly fly the Hind. Specifically, he seems to be limited in his ability to make control inputs (probably to make his flying smoother). When the lesson unpauses we are in a climbing left rotation, uncoordinated. When the instructor asks you to hover, Petrovich increases the power for hover flight. Combined with the out-of-trim condition, I think this demands more right anti-torque pedal than Petrovich is desigened to apply, so he looses directional control and we spin to the left. If, immediately after unpause, I use the Request Control command (default "C") to take the flight controls from Petrovich (I'm flying from the front seat). I use this moment to stabilize the helicopter in forward level flight, and re-trim the controls (cyclic and pedals). I believe this allows Petrovich to have enough authority to properly function. I then give control back to Petrovich ("C") and enable the compass rose HUD. The lesson continues normally and I'm able to complete it. Here is an example of me also loosing control. Hopefully it doesn't show the weapon mode problems you had in your first post. https://drive.google.com/file/d/13AYesiD8fgwADk3fhxGGsFRYzpid28jE/view?usp=sharing

When Greben system is placed into mode ZK, here should be a light on the KM-2 to warn the Copilot (bottom left). Thanks.

The dial indicator on the KM-2 (top of instrument) acts as an independent gyro, when I don't believe it should. KM-2 takes heading information from the Induction system (flux gate compass) and combines it with a correction value called variation/declination to output a "true" heading value which can be used to align the gyro system. Or any other declination value... allowing for "grid" navigation. My understanding is that the face of the KM-2 then has the purpose of informing the crew what alignment signal is correcting the gyro orientation. There should only be 2 modes of operation. ZK, in which the declination setting is the only value (flux value excluded) and so the indicator should always equal the declination value set at the bottom of KM2, without exception. The other option is mode MK, in which MH(magnetic heading)+/-MV(magnetic variation)=TH(true heading). In the supplied track, I enter various values of declination, align the gyros using both ZK and MK, and make a series of turns. At the end, the helicopter has a MH of 270, variation value of 0 set using mode ZK, yet the KM2 indicator shows 090. This is because as I turn the helicopter, the KM2 indicator rotates like a gyro, despite the flux gate being removed from the equation. It should have no idea that anything is turning. The indicator will then "slave" when pressing the Greben Match button. But what's it being matched to? Only the value entered at the bottom of the instrument. It should have been indicating that the whole time. This is a difficult thing to describe, I understand there will be some confusion on this. But it operates very strangely right now, and isn't agreeing with the tests I can find online. Thanks. KM2 acts like gyro.trk

After alignment (or hot start), Greben gyro system corrects at the high speed only. It behaves as if the "Greben Match" synchronization button is stuck in the pressed position. Consider the following test; It's currently not necessary to press the AGREE (Greben Match) button. The system will pass this test because it is always in high rate mode. It should not pass the test. Track attached. Greben stuck high rate correction.trk

Horizontal switch in rear cockpit: "P-38. 'Greben' mode ZK/GPK/MK" When viewed directly, left clicking the switch moves it right (aircraft forward, right when viewed directly), right clicking it moves it left (aircraft rearward, left when viewed directly). This is a minor annoyance, as I feel the reverse interaction is more natural. Consider another horizontal 3 position switch on the same wall panel, "ARC-U2 Switcher Compass." Left click moves the switch left (ac rear), right click moves the switch (ac forward). This feels more natural. Thanks.

This is a UI problem. It's difficult to use the Greben-1 or perform any tests because this knob is so slow. On my Caucasus test mission, the magnetic variation is listed at 7.1° East. Using my mouse wheel, it takes seven clicks of the mouse wheel to change the declination value one tenth of one degree. To input the entire 7.1 degrees needs FOUR HUNDRED AND NINETY THREE clicks of my mouse wheel. I counted. I probably miscounted a little bit because it took nearly five hundred mouse wheel rolls to put in seven degrees. Seven. Lets say you want to try the click and drag method. Pulling your mouse cursor completely across the screen (horizontally) results in about three degrees of input. About the same vertically dragging. The 3d model knob has what appears to be 10 ridges, or about 36 degrees between them. I takes those seven mouse clicks to rotate the knob by a single ridge. Please increase the speed of this knob!

did you fire the missile from the rear seat, using Petrovich? in your track it shows that failing because the canon was selected. It could be a problem with the track.

The AI isn't perfect, part of learning the Hind is learning how to "fly the AI." Since it appears that all we're doing is giving commands via the Petrovich menu to the native DCS AI pilot engine. You were never asked to "go as the gunner." Your tutorial broke because something in your controls (or you) switched to the GSh 30-2K auto-canon, which disabled the gunner sight, and broke the training. It was at this point you jumped to the front seat and messed around with the AI commands. You never gave any sort of direction/heading command, which seemed to confuse the AI, eventually resulting in a loss of directional control, and you getting frustrated and ending the training mission. My suggestion for having a good experience with the training is to do nothing else except what you are told to do. Unless you already know what you're doing. PS, interesting enough the track does not record the status of the periscope shutters, so your missile attacks were completely blind to me. Otherwise the track worked great.

I use a twist stick and the keyboard and can get around a packed carrier no problem. The free caster makes it turn arguably sharper than the Hornet in NWS HI.

Just keep practicing. It's going to feel like a long road and then it will start to click. You're getting the "return pre-contact" call because the operation is timing out. I suggest practicing flying formation with the tanker to build skills. Really, that's all you're doing when you're AAR anyways, just there's a hose involved.

I can tell you from some quick testing there definitely is a "sidewinder growl" of sorts on the L-39ZA simulation. Not saying who's right, or what is true. Just reporting my experience from testing. Because I own both the L-39 and Mi-24, and I was curious.

So what? What you describe is pretty much exactly that issue...

I assume it's because you don't know you're doing it, and thus repeating it every time...

In the hind video the lock tone is intermittent (slow beeping), but on the L-39 it's steady with the R-60M.

I also suspect you broke the gunner sight.

...please...

I don't like how badly blurred the rotor hub is on the Apache.

600 Knots Indicated, as much Mach as you're willing to handle. That's assuming this same configuration: It's on page 289 of the manual.

It was exactly the problem I knew it would be as soon as I downloaded the track. You did not monitor the main rotor RPM. Thus, you failed to manage it.

The audio is cut off too. Doesn't read all the text displayed on the screen.

Would be a nice detail to see corrected. Thanks for finding it.

Mission loads with 0 canon rounds for GSh-30K. Rear cockpit rounds counter reports full load of 2x125 rnds. Track Thanks, 30mm Counter Bug.trk PS: Can't scroll down the counter wheels, only scroll up (increase rounds value). Not sure if that's intentional.

I would fire all my ATGMs first. Considering I knew this was the situation, I would bring 8xATGMs as a starting point. I would look at my weight situation (and the flight distance) and I would decide if I would even consider carrying anything else. Vs more fuel. After all my ATGM's were fired, and if there were still targets, I would assess if it's too dangerous to use the canon or any other stores I had decided to bring. If the targets left were still Tanks and AAA/SAM (or were still heavily defended), then there's really no point getting shot down trying to use anything else, and I would RTB. You can also stay on station and use Petrovich as reconnaissance for your teammates until you all departed, or you reached your fuel limit. I recommend approaching at an offset angle, then when you are ready to attack turning in, getting a quick line up, shooting, then breaking off. I suggest "jinking" (erratic flight path) to spoil their gun solutions. Watch that you don't overdo it and kill your speed. Use terrain/buildings/trees for cover/concealment. Those are AAA. Use the ATGMs.

Hi! I don't own the Apache. All I can say is that I love the Hind! Responses might be a little 'off the cuff' (how I'm feeling today). ahh, the "DCS Meta." Let me guess: all sitting together in a big open field, not moving, not guarding anything strategic. Just sitting there... Yeah the DCS Meta. Wonderful. With DCS damage models, my meta is rockets are for troops, guns are for vehicles and equipment. I would have chosen the gunpods (12.7mm) or the 30mm. They work great for trucks and supplies. Not supposed to be standoff. Let em loose on a squad of enemy troops. This gun is amazing, you'll figure it out. Long straight in line up shots are not what you want. Don't give the enemy the opportunity to hit you. ATGM, that's what they're for. Well, if you still just want to live that life, my suggestion is to bring your 8 ATGMs, fire them, then go home. I bet your friends are doing the same thing in their AH-64s. Bet they don't even bring rockets and never fire the gun. Who's fault is that?

You don't need to be afraid of VRS when in forward flight and at low power. Drop the collective fully if you need to.