Are you sure the notch values for the N019 in-game are those you listed?
Going by the config file for the N019 (assuming I understand it correctly):
MPRF search is 100 m/s = 360 km/h
MPRF track is 40 m/s = 144 km/h
HPRF search is 50 m/s = 180 km/h
don’t know what the HPRF track is as the format was changed this update, but if we go by the previous values, it is 50 m/s = 180 km/h
@MiG_23M it appears they did some changing on the flight model for the f15’s already today?
Didn’t mean to reply to you @Grimtax :P
I don’t see any changes but I’m not home yet
No FM changes at all for 0.19
That’s what I thought.
I used Width under dopplerspeed and divided by 2. Look on MPRF search, 100m/s. I would say thats the bandwidth of the filter. The only way to test is to grab the plane and have someone just go slow as possible.
The code on one radar is not always the same for another. Best way to test is just flying it
while the changelog says it was changed it appears to be unchanged yet, maybe a dev accidentally put the F-15 changes on an earlier patchnotes
This could be the case. There are no FM changes in 0.19 update.
well the goodnews is that it seems the F-15 flight model change should be coming very soon, since it seems internally it was already fixed and will come in the next patch or so
Could also be in reference to my first report about it underperforming at low speeds, who knows. Need more information.
No FM changes to F-15 in 2.33.0.19
Lies no changes on 0.19 only on 0.20 which is in dev
only what changed, fuel flow 1100kg/min => 770 kg/min on sustaned turn on 0.62M
Its funny how a much more complex thing, imo, to fix without messing other things up is made in a few days. Hard to get it right to manuals specs if they available but then other stuff which is literally a single line code change with bunch of proof is simply not done
Makes you think
cries in AIM-54C T^T
IRL N-019 radar
In the game before 2.33 we had hard notch filter in both PD track modes.
Since 2.33 notch filters were removed for both modes. But for MPRF track mode doppler speed and range ambiguity and how this ambiguity affects ground clutter effect on the radar is not modelled. Now in MPRF in look-down cases the track is lost for “notching” targets. IRL in MPRF track mode target returns and ground clutter separation by range is possible, but not always due the range ambiguity.
Well said, I did not know the rejection closure rate of MPRF was around ±150-190 km/h. Pretty cool and good to know.
Notching, or drastically reduced closure rates of a supermaneuverable Su-27.
(If GJ would please stop limiting the alpha at speed.)
I was just looking at the changes to the Leclerc for 2.33.0.20 (not yet live)
While looking, I noticed that the F-15’s are getting changes to their flight model
Credit to Gszabi:
I only understand that the Oswald efficiency number is being increased by 0.1 (0.65 → 0.75), but I don’t know how to intrepret the other values being changed.
Edit: Also noticed the RateMaxLoadFactorMax being increased aswell by 1 (11 → 12)
the main changes are:
MachCrit5 0.4–>0.35
MachMax5 1.0–>0.5
MultMachMax5 1.3–>1.5
MultLineCoeff5 0.05–>-0.6
MultLimit5 20.0–>1.2
basically now the induced drag curve (basically drag that occurs during maneuvering) starts at mach .35 instead of .4 then peaks at mach .5 instead of 1.0 and the curve ends at mach 1.5 now instead of mach 1.3
what this does is now the most induced drag occurs at a much lower speed instead of a much higher speed, so expect inferior energy retention at mediumish speeds but better retention at high speed. Ofcourse the F-15 already retains p well at high speed so to ensure that it doesnt straight up gain speeds in mouse aim turns instructor was loosened to pull harder to ensure that doesnt happen. Retention at high speed likely feels the same now but AoA and turnrate should both be better now as a result.