AeriaGloria

It should make the radar itself more immune to chaff and glint. Right now we can’t really see how glint or chaff might be sending into memory mode for a second or two.

I have no problem posting tracks. I just thought it was “Bugs and problems” not just “Bugs.” In addition I was trying to find a post that already had tracks posted. But appears to be removed or merged, and all I wanted to do was add detail to this post that has a track. I wasn’t trying to report an issue, and that post was here. Also. Half or more then half of the threads on this first page of “Bugs and problems” have no track, so sorry if the enforcement seems uneven.

I looked over your post again, and don’t know how many of these issues your still having after the hot fix. I have a video where I go over specs of every mode, for example notch of head on increases from 230 to 325 kmh steadily from 20-60 km. Scan rates of pursuit mode is 3.7 seconds at all ranges. Idk how you counted it but the most sure way is to count the radar bars on the HDD. Count how fast it goes through 1-2-3-4 and that will give you scan time. It seems vertical scan radar is still heavily work in progress. I wonder if people sometimes fall into 50 kmh same speed filter. You can also disable notch by being 5 degrees or more below target, though I haven’t tested it. Also, head on should have minimum 5 km range before it breaks lock.

18 km service ceiling shameless self plug Most efficient climb for BVR technique

Well ED said it was intended for an external base rangefinder, which basically is Soviet speak for moving a circle to match the wingspan. Thing is MiG-29B technical manual can be wierd. It gets HMS symbology wrong and few other things are “different.” I love it all the same, it’s chapter on coop mode is a one of a kind, but I would look for other sources personally that it was actually integrated in all production aircraft and MiG-29b tech isn’t just saying that because it was intended and dropped at the last moment. It’s almost like the MiG-29b tech writer is a technical genius who didn’t spend a lot of time around people flying it lol.

Hello, I could swear we had a nice thread about this topic here recently with a track and everything. I’ve looked everywhere and it seems to be gone. Anyways I’ve done some testing, takes 10-15 degree angle to lock a target flying at 1200 kmh. Or a 45-60 degree angle to lock a target at 1500 kmh. I would love to hear from ED why the radar does this. I saw it in the manual so I know it’s valid, but it also never stated if it was a “no lock or detection” kind of limit or something else. Anyways cheers

The plan was to have it range like a circle to the targets wingspan apparently. But the plan never went through and you were stuck using target size dial with funnel. This is MiG-29B tech manual right?

What we need to find evidence of is not the 9th document saying “it has a radar blanker!” Becuase ED agrees with. ED’s premise is that the radar blanker can’t sufficiently deal with MPRF/HPRF from the factory. That’s what we need to find evidence for if we want things to change. Or otherwise some bulletproof SME evidence.

Hey guys try turning on AP/AJ anti jamming switch. It makes a huge difference or I have just been very very lucky in recent shots. Perhaps when they chaff or roll around causing glint it helps the radar keep the illumination on target.

Let me re iterate. Documents saying that the SPO-15 has a blanking circuit for the radar is agreed upon by ED, and it does not disprove their reasons for it not working. It is no longer any use quoting technical docs saying “SPO-15 has a radar blanking mechanism,” becuase that is not what ED is saying is the problem ED is saying the blanking circuit was designed in 70s for LPRF and CANNOT HANDLE HPRF. It is not able to properly see and blank HPRF pulses. Quoting docs saying “it has a radar blanking circuit!” Is literally no use to quote the post in case people forgot “As for synchronization with radar, SPO-15 features a synchronization circuit on board 51, but it was designed for older radars such Sapfir-23. The principle of operation is the same as in older SPO-10, the receivers are blocked in rhythm with own radar's pulses. It cannot handle CW or HPRF signals (which trigger CW circuits anyway, followed by them being disabled completely in all channels once HPRF is recognized), so if they are emitted the affected hemisphere is shut down completely. According to electrical schematics for the aircraft, the N019 produces a single signal wire, which is used to block forward hemisphere, so that SPO can be left on and at least the rear hemisphere remains usable. Radio equipment manual confirms this. Full synchronization would require additional signals, so even if Cartridge 51 was modernized it would also require additional changes to wiring and to radar itself. Additionally every single channel in forward hemisphere on both boards #54 would need to be modified, so only CW signals were blocked, which is not avoidable. Failure of this system would cause the device to be flooded by own radar, making it completely unusable with radar on.” Feature's a synchronization circuit! Wow! The problem is their research shows it doesn’t have enough wires and the circuit is designed for LPRF and not HPRF/MPRF/pseudo CW.

Same as ARBS on Harrier

It is telling you you could enable KMOD if you want. Once you got closer there was no need. You will only see this active jamming symbol.

How? Ergonomics isn’t only HOTAS. Soviets had a department of psychology look over the cockpit and make recommendations. They recommended to use round dials and only use tape for fuel. All your radar stuff is together. All your weapon stuff together. Pylon selection above throttle. Everything you need in combat is easily reachable by the left arm without moving in your seat. Your instruments are grouped together logically. It is vast improvement over all MiG aircraft before it

I don’t know about peak power, and the N-001 is basically a larger N-019, but average power of both radars is identical. “Hey it’s ‘Operational validation and testing by MOD to get it approved for service’ day” MOD: “Why doesn’t the RWR work when the radar is on? Can’t this be fixed??? How does this happen after all this time and money????” MiG: “uhhhhhhh. I guess we just didn’t think it a priority! Should we fix it for service entry sir?” MOD: “I mean if you think it’s low priority……. Why not……. It’s only a defensive system!”

This is the one MiG-29 manual it’s mentioned in. in Su-27 manual it says it is 5-8 signal strength of type X. So you would think if you had a higher priority lock that it would show that instead.

The beam is also 3.5 degrees wide.

It is KMOD ranging and can be turned on by target acquisition depress. turn with 30-60 degree bank until radar diamond or IRST circle reaches the wing tip of the artificial plane silhouette on your HUD, then reverse turn so it touches other wingtip. After 8 seconds you will have a one time range with estimated closure based on radar mode or TWS switch position

Yes, what you mean same function? It is just anti jamming/interference mode

Either I’ve been lucky or putting the AP/AJ switch in AP has massively improved my r-27 hit rate

Sure, but please not original fc3 SPO. Just give it launch warning and be used with radar. With RSBN correction the nav system also doesn’t need fix taking, the most it will be off is about 800m but no more becuase of the constant RSBN updates.

Well what’s the question? SPO?

An axis working -6/-4/-2/-1/0/1/2/4/6/8/10? Ten positions?

I’m trying to make tracts to make a bug report that it does not fit the 0.5-0.85 probability of kill given in manuals. I need atleast ten R-27 shots for this

Read far enough back in this thread. You are not getting launch warning. Treat every lock as possible launch

It’s only from 30-45 degrees off nose it locks only r-73. Get lock and slowly move nose away and you will likely see it eventually. That being said it seems slightly bugged this patch