Flying too fast up high trying to pull high g maneuvres.
It happens mostly at medium and low altitudes
As far as I can see, the radar will receive some changes in 0.41.
In MPRF, the power will increase from 600 to 800 watts, the half-sensitivity angle will decrease from 4 to 3 degrees.
Spoiler
In НPRF, the power will increase from 600 to 1200 watts, the rest will change as in MPRF
Spoiler
And in different modes, the beam height will decrease by an average of 30-40%.
But I did not see the main thing - a change in the scanning pattern like on PIRATE.
Anything on the bug that sometimes you can’t switch radar lock, nor fire missiles with the FGR.4.
Have these changes been implimented on the live?
Just took the Typhoon for a test drive and it still appears to struggle to hold any kind of TWS lock other than using the smallest width - the same scenario the F-15C doesnt struggle at all at medium width TWS
The one where you get stuck in MEM track or the one where you are stuck in IR track after locking the parget with PD?
So with this potential raft of changes - presumably aimed at ‘fixing’ the radar - perhaps it wasn’t all of us being collectively paranoid about the Typhoon Radar being a bit funky?
The radar def had some problems, these changes seem to fix some but still miss some big ones, and the nerf to the vertical scan volume hurts.
I dont think anyone who was pretending the radar was fine really knew what they were talking about.
Vertical scan nerf hurts, we are now going to be even more vulnerable from threats below.
Depends - I think we’ll have to wait and see how much of a difference it makes in actual gameplay. I usually have the radar on manual elevation control anyway to sort of ‘jockey’ the scan to where I want it - possibly a workaround if the scan rate is slower in the vertical axis.
The main problem I had was in it constantly losing locks of that in any other aircraft (Tornado, Gripen, even the Phantom - the PHANTOM) I felt I would not have. The effect is that I spend more time trying to make the damn radar do what I want it to than actually flying the jet. Which is the complete and total opposite to the Typhoon radar system IRL - which managed to reduce the workload on the pilot to the point that you no longer needed a second-seater to juggle all the radar black magic.
I’ve also had one or two cases where I’ve hard-locked from TWS mode and the AMRAAM has refused to fire. Possibly a packet-loss issue but I’ve never had it happen on any other Fox-3 on any other aircraft?
No thats a bug the game has a few aircraft that suffer from it
The TWS and hardlock is atrocious right now.
Depends if Gaijin test these fixes or just roll them out and hope that solves the issues.
IRST need to be removed from Auto-switch
untill AMRAAM would be able to launched by IRST
The phantom is a stealth fighter idk what you are going on about, shouldn’t be able to lock it. /s
Might have a bug report to write, but I could also be wrong on how they are meant to function.
Paveway IVs. Currently, if you drop them with laser off, they’ll go to their designator marker on GNSS just fine. If you enable the laser, they’ll swap from the GNSS target to the laser target just fine. But if you then turn off the laser, they just fall out of the sky like a dumb bomb. Is this correct behaviour or should the GNSS target be updated/they should guide via IOG?
i mean, once you switch to laser it probably clears GPS data. once you turn off laser, it isnt being guided at all, since it is basically just a Paveway III with GPS, and according to gaijin Paveway III doesnt have IOG, you may be right, you probably are right, but gaijin wont change it.
My guess is because the lock switched to an IR lock, rather than the regular lock.
It’s been a problem for all planes with IRST for a few months iirc.
Wierdly, I dont think i’ve had my radar in the Typhoon do it once yet.
This was also observed on AASMs. I would encourage you to bug report it, I would contact Flame about this.
Yep, shall write one tomorrow.