Muchocracker

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.

At true 90 degrees it's in the sidelobes of the 50-70 degree antennas even though it's in the mainlobe of the really low gain rear hemisphere antennas. Im not at all surprised the ranges are that low for detecting an MPRF waveform.

There is only 1 A/A WYPT reference on the radar page and that's the top left. You're thinking of the SA page, which already does exist and gives both BRA and BE for selected targets on it.

Intended change, previous behavior was inaccurate for our hornet.

SILENT mode does not "shut down" the transmitters and receivers like standby. In SILENT the receiver is still active and will do Angle Only Tracks and passive ranging (IRL, not implemented). The "ACTIVE" button is part of the QUICKLOOK function (also not implemented) that does some pseudo phased array trackfile update stuff. The radar just isn't doing constant transmitting with the Raster volume search pattern and is still able to transmit command links to in flight aim-120's. So this is correct function.

This has been an off and on issue for many years espeically with the normal antiship harpoons where they will just go off in completely different directions between clients or client-server. We've stopped using them in vCSG-3 at this point because of it.

When AUTO INT is turned off interrogations will only be run on the L&S automatically. But if you're setting the friendly as L&S them there may be an issue with outside of STT. Will do my own testing. I do have to ask tho, are you playing with Link-16 not turned on? This would be the only time a problem like this would turn up for friendly aircraft that i see.

And like i said in the next sentance, reacquired late. Missing under because of glint induced aiming errors. In the third track the missile oscillates up and down when the target isnt doing a similar maneuver. That's indicitive of the missiles aim point shifting.

I'm talking about LITENING, not ATFLIR.

reproduce it and post a trackfile please

distance missed doesn't make it a bug. And the aim-7 is not on the same advanced model yet.

Marine corps hornets use it as their primary TGP. It's within the timeframe standard ED has set.

Missile is losing the target to chaff while beaming in almost every track. Then reacquires super late and misses under likely because of target glint. I don't see anything in these tracks to suggest a bug.

Okay, so it should be easy to present evidence to prove that the blanking circuit installed on SPO-15LM's for 9.21A mig-29's can handle the HPRF waveform then