Let me explain:
I have the scope stabilization set to F and the reset to H
When I’m in the scope, if I press F when my scope is not on a radar capture target, the scope will shift to the captured target.
If I press F when the scope is looking at the captured target, I gain control of the scope.
At the same time, as I see, I can press F while pointing at another target and the sight will follow it (but the indication frame will not appear, which is probably a bug).
At the same time, if you have the stabilization point set, the radar will not move the sight itself when it catches a new target
If I’m 3-person, pressing F doesn’t move the stabilization point to the radar capture (I find this very convenient), but pressing H resets the aiming point and immediately puts it on the radar-captured target.
I am actually pressing sight stabilization in the videos I posted, but it keeps resetting to the locked target on TWS
It seems like to me, that while on TWS slaving, this is what normally is supposed to happen when you press the sight stabilization key:
1a. Sight stabilization to ground
1b. Target track direct lock
2b. Target track lock with movement (this mode will limit how far you are able to move the gimbal to the original target, while tracking said target)
3. Unlock (3b. if TWS is on, this will force the TGP to default to the TWS lock) Passive feature: The TGP will “remember” the last known location you 1a., or if you were in 1b. or 2b., it will default to the last remembered location
But the issue right now seems to be:
If do #1, then lose gimbal, then it starts acting in weird ways where I am unable to break free from #2b and #3b
The core issue being with sight stabilization is that I am unable to cycle between the three, or it will automatically go to #3b, hence why the TWS mode seems overly aggressive. But like I said, being able to unlink your TGP from TWS would alleviate this issue entirely.
That’s only because you’re in mode #2b (Target track lock with movement (this mode will limit how far you are able to move the gimbal to the original target, while tracking said target) which becomes a major issue if your TGP decides to lock a plane much further away
Yes, that was the issue I was addressing and I personally think it’d be nice if the targeting didn’t reset to the TWS outside of the shkval (or whatever TGP) angle, or it was much less forceful.
As CAS, you do pull a lot of evasive maneuvers that forces you to lose track lock, so I was a bit shocked when I found out that your lock doesn’t stay in place because it prioritizes slaving to the TWS radar.
But again, you and other users have made it clear that it was a feature that was already present in the live game so it is what it is until the devs decide to change or refine it.
I think it should work that way, since without radar lock your stabilization doesn’t reset when you turn away from the target
I’ll report on this, as well as a couple of interface flaws in this mode that I’ve noticed (no square around the target accompanied by TGP while you have a radar lock)
From what i have read they have advance a lot in GaAs and GaN. But even Byelka need a upgrade to GaN. By StealthFlanker calculations Byelka its as powerful as IRBIS (not a bad thing). But its a 13yo radar/tech. They are also researching ROFAR radars. But there is almost 0 new info on that.
Dunno how feel about this. With Su-30sm not been the best climber or R-77 state.
the aircraft is clearly not at complete zero airspeed
the Su-30SM received no engine upgrade while being heavier than the base Su-27 model, a plane that doesn’t achieve a 1:1 TWR on full fuel loads in the first place
you trying to use this video to prove an even heavier aircraft that generates the same thrust should somehow have a higher TWR just makes you appear an imbecile
