AeriaGloria

Not reused from 23. But same indicator is reused in other places.

Okay, so, the difference as Miki said is trim button in Hind resets AP, so you fight the attitude hold AP as you pitch down and then trim and the extra cyclic to fight the AP is no longer needed as trim button centers attitude hold. I really recommend against using trim hat too much, look at right control + enter screen. You will hit the maximum limit of the pitch AP MUCH MUCH faster just using trim hat. Trim hat is meant for small adjustments. When your pitch AP hits its limits, it can no longer stabilize you or dampen your movements. I talk about it in my video on the Pitch/Roll AP and I give 3 different solutions to the “uncommanded pitch” after trim phenomenon. It slightly depends on your kind of stick, with FFB I prefer just rapidly trimming 2-3x. If you watch this, it will explain everything

It is the whole reason S-24 points down. It caused a Mi-28 crash IRL. As someone else said. Launch from 100 kmh or higher

So I guess no way to make it say “Check Ekran” lol I wonder if the mode of using OPT cursor to align INS by pointing it at waypoint was removed for 9.12A?

Sooooooo SPO-15……..

The only part that should work with ILLUM is each sensor picking up the lost lock of the other. And fully implemented coop will force radar to MPRF

What bug? It’s supposed to work with radar in dummy.

Radar: IRST locks when it can. Only mode with IFF TP scan: beyond laser range it does ranging in scan mode. And pressing lock a second time will transition to Radar STT. Laser range changes Radar to STT. Enemy RWR shows search radar until radar STT. Vertical scan modes: Selected mode locks as primary sensor and other in background as secondary. Full Radar STT. IFF only in radar vertical scan. Helmet: Both try to lock at same time, first to lock is primary. Radar STT. Each sensor will pick up lost lock of other if possible. Firing/selecting Fox 1 enables radar. If Radar is primary changing SUV knob to IRST mode changes IRST to primary if it has lock.

It’s not supposed to, it’s working in close combat mode I posted an updated graph. You have to understand that HMS mode is bugged right now. If you learn how it works now you will be messed up when fully implemented. Right now radar does not work beyond 30 degrees from nose unless you already have lock. Once implemented, it should work for the full 60 degrees range of the HMS. Right now IRST gets lock (up to its 30 degrees range slew limit) and radar is secondary. When implemented both should try to lock simultaneously and whatever locks is primary, allowing you to lock with radar from 30-60 degrees. I really tried to make my Graph easy, you don’t want to try and decode what the manual says! As my graph says, any close combat mode? Full radar STT. Within laser range in any mode? Full radar STT. Radar is only not STT during TP scan beyond laser range where it does ranging in scan mode. And pressing lock a second time will transition to Radar STT. Each sensor will pick up the lost lock of the other if they can. That is basically it I tried to make my graph account for every scenario. In laser range? STT, IFF only radar mode. Outside laser range? I show that IFF works only in radar mode and TP scan works as I said above. With my graph I’m trying to show if radar is STT or not, IFF, and enemy RWR for each mode (if necessary, as mentioned in laser range they all work the same). As you can see with my graph, the only appreciable difference between modes is TP/IR scan outside laser range, and that radar gives IFF. There are small differences (vertical scan chosen mode is always primary, in HMS first one to lock is primary), but is essentially the same to the user.

No. Unless Ralt has a circuit breaker to turn off

You sure you aren’t seeing the dampener operate?

Makes sense!

Okay have a list of limits here Bombs - Mach 0.8 KMGU - 900 kmh, 30-500m level release altitude Rockets - Mach 0.8, flight time above 900 kmh is limited by wether pod has heat protection or not interestingly, it also says that KMGU does not require the brake/retarded switch forward.

No not at all it’s completely innacurate. There is real manual, I can link it in a bit

I was also confused why Wags set target hieggt in his AG video.

Updates to be accurate to this patch Edit: damn forgot to put in that you need radar in dummy/EKV to get radar secondary work (such as radar ranging in TP search)

Yeah. I half enjoy the difficulty of the MiG and half actually crying lol. Yeah, maybe combat manual meant something else about symbology only showing up at 1600m

Yeah just wierd your baro alt is changing range

It just seems there are two factors it takes into account 1. following the target with pre designation 2. movement of pipper compared to pre designation You can tell pipper isn’t exactly moving normally after pre designate. I had a time I pre designated a moving vehicle on a road, the vehicle made a sharp 90 degrees left turn after the pre designate. I put my pipper on it ( within the 10 second limit) and my bullets we’re just the tiniest bit off.

It shouldn’t care about altitude setting, the only methods of air to ground ranging are laser and radar altitude, it does. It use radar. Understand once the laser is activated (dive of 10 degrees) it stays on for 30 seconds no matter what. And will afterwards stay off for 32 seconds no matter what.

I believe he is mistaken, mixing it up with salvo fire

It’s not a button. It’s simply a bind to simulate pressing through the AOA limit which takes about 17 kg of force.

I have also seen Mach 1.5 limits for the centerline tank. Which is about where you jettison it in my profile/recommended manual profile as well. I have never seen g limits for ground weapons, only speed limits. For example it seems no faster then Mach 0.8-0.9, I’m a bit too lazy to look up exact limits right now. One issue with S-8 is detonation of the rocket motors from aerodynamic heating.

Thank you that clears up why! After you release lock, is it reasonable that it’s also comparing the spot you pre designated with current pipper position? It seems to atleast do this for motion compensation, as you move the pipper it lags as if trying to provide lead for a moving target in the direction you move your nose. Giving the impression that it’s harder then normal to move the pipper