Muchocracker

You have another conflicting input somewhere, likely an axis. Look in your controls bindings.

From the most recent wags video https://youtu.be/HyiWR8UYfS4

Target could also be falling within MLC of a spectral line and the scenarios in your tracks are set up just right that the closure rates fall into it. Theoretically there shouldn't be a hard maximum detectable velocity limit with MPRF signal processing but soviets seemed to have always done things differently. Could be many reasons why they imposed one.

And that's why we ask for more clarification, guy. It could or could not have anything to do with the blanking circuit itself but some other part of the system. We need the dev to give us more detail on their reason and what information they used to reference it. I said the thread was looping back to the "circuit exists" point. Not the later *actual* point of debate. We all know it has a blanking circuit.

The system having a blanking circuit and sync with the radar was never in dispute. Idk why the thread keeps looping on this. The debate is if it's able to handle blanking with HPRF waveforms or not. And assuming for a second that this is true. As far as im aware it's still being disabled when the radar is transmitting in MPRF, and has not been mentioned by the devs as being incapable of handling it. So this portion is at least can be concluded to be a bug and should get corrected. If newy can get some more clarification from the team on why the blanking circuits cant handle HPRF signals that would get great. Then this debate can actually be productive and the right sourcing can be found to prove or disprove it. Otherwise this is just going to keep going nowhere.

Against what system? What waveform? Does it use pulse compression and long/short integration periods? Imo expressing RWR interception ranges as ratios of radars detection ranges just doesnt work all that well.

Please read the manual

Because as i explained before, if the target is at true 90 degrees it will fall in the sidelobes of the 50 degree sector antennas. This makes that sector very insensitive to an emitter in that area. Combined with the low gain of the rear hemisphere antennas and the fact that both sectors have to independently detect the target at the same time to trigger the 90 light. This is why it triggers are very low ranges. They are not "merged" together or provide a boost in detection if that's what you're trying to get at. The system doesn't work that way. ED has said as much that the 90 degree sector is much weaker

Not in DCS.

Unverifiable anecdotes dont really prove anything. Neither does declaring a bug exists without evidence or principles based reasoning.

Auto is interlieved PRF for each bar in the raster search. It has nothing to do with the lock mode functions.

The entire point of the new SPO-15 model was laying the ground work for a higher fidelity RWR simulation across the entire game. ED has said it numerous times. You're acting like it's a permanent unique implementation that will never exist elsewhere.

OFP 21x isnt what is modelled. That's way newer.

Idk what you're talking about "inputs" https://www.digitalcombatsimulator.com/en/news/2025-07-12/

Have no reason to believe that the proper antenna gain patterns aren't modelled considering all of the statements made by ED through the whitepaper and other places like the interview answers in the flyandwire video.