AeriaGloria

If the blanker removed becomes default option so it shows F category signals within 25-40 km and other signals as secondary beyond that range with radar on, I think many people will be happy. Make the ME triggerable option the ability to have the blanker on, or atleast make it click box option In normal spawn tab without setting up a trigger

Did you select a lower resolution cockpit? It seems the low and medium resolution cockpit has English ILS. I do think it’s “F” symbol for friendly is cute though Вы выбрали кабину с более низким разрешением? Похоже, что в кабинах с низким и средним разрешением используется английская система ILS. Мне кажется, что символ «F» (friendly) довольно милый.

The last SPO post in mini updates has many references to own radar showing as X category on SPO. That 100% means that per limitation in manual it should show F category signals within 25-40 km with radar on. It is just matter of tuning off CW reception AND it would still show other X category signals as green secondary threats, which will be obvious if we get secondary threats of no other category. So even beyond 25-40 km we will still have the green dots to see with radar on. And T category signals on primary and secondary threat within 25/40 km. Personally it seems to me that ED should make this default and make having the blanking wire be the ME trigger able jtem becuase this could make so many happy to atleast have radar show 4th gen threats at close range.

Very jealous! What do you think of MiG-29 human interface/weapon controls ergonomics now? Any revelations?

here “Additionally, the SPO-15 failures will be added as triggerable in ME, with the blocking failure separated from the general processing failure, to demonstrate what happens when this system fails” I believe what this means is seeing radar emissions on SPO from removed blanker. здесь «Кроме того, сбои SPO-15 будут добавлены как триггерные в ME, при этом сбой блокировки будет отделён от сбоя общей обработки, чтобы продемонстрировать, что происходит при сбое этой системы». Полагаю, это означает, что на SPO видны радиолокационные излучения от удалённого глушителя. last post

At the risk of making people sick of me making the same post how about the information that per Su-27 manual it’s equal power radar and similar SPO antenna placement shows as X category 7-8 bars on SPO. And according to ED manual limitations of SPO it says that when MPRF/HPRF F category signals are detected, it shuts off all CW (X category) reception. ED has said in latest SPO-15 info post that they plan to make option to remove the front hemisphere blanket so it will show your own radar X category emissions with radar on. Therefor when 4th gen fighters approach close enough that their radars go from being recognized as a flashing X by SPO-15 to properly identified as MPRF/HPRF (F category), it will then show the F signals instead of the own radars X category emissions when your own radar is on. This will happen at 25 km for F-15:18 and 40 km for F-14/16 so only close range but far enough that I think ALOT of people are going to be happy with it, as it’s close enough to short and evade most AIM-7/120B shots Like I said before it’s possible this could be a much much smaller thread if it was released with such a configuration

This might get better when the front aspect blanket is removed. According to Su-27 manual, whose radar has same power output as MiG-29 and similar SPO pavement, it shows as X. And according to Ed manual SPO limitations, upon receiving F category all CW/X reception is shut off. Meaning that when a 4th gen is within 25/40 km (25 km for F-15:18 and 40 for F-14/16) it should show on RWR with radar on (when the blanket is turned off as an option).

Defect? A defect that lets me see F category signals with radar on…… if my theory is right…….,

I am very curious though I understand we will have the answer eventually ”I would love to hear from developers or someone about when the front hemisphere blanker is removed as an option as was said in the most recent SPO-15 post, IF the device may still show F category signals at less then 25-40 Km ranges with radar on becuase of the limitation where once correctly identified as HPRF/MPRF all CW signals are excluded, and Su-27 radar shows on SPO-15LM as 7-8 signal bars of X category (since Su-27 radar has same power output as MiG-29 radar and SPO antenna placement isn’t too differentso I assume MiG-29 radar shows on SPO similarly) so would thus exclude own radar signals when F category (MPRF/HPRF) signals are found, since 4th gen fighters go from X category (CW) to being correctly identified as F category (MPRF/HPRF) at 25 km (F-15/18) or 40 km (F-14/16), and the ED manual lists this as one of SPO-15LM’s limitations to ignore/turn off CW reception when MPRF/HPRF is correctly identified. This would mean the option of the blanker removed is nearly a perfect middle ground for all users and perfectly realistic” ED manual under “Device Limitstions- -. Additionally, when an HPRF type is positively identified, the continuous wave detection circuit is shut down preventing detection of actual continuous wave threats - this needs to be taken into account when operating in an environment with both 4th gen fighters and Hawk batteries present”

I mean aside from radar synching and no launch warning ( which ED said they might add as an option), what is daunting about the new SPO-15? Aside from those two things, it’s realism makes me very happy, I understand that’s not everyone, but it still often tells me more info then old one. Like F category when a 4th gen is close, flashing X when medium/long range. Missile range estimate, and showing secondary threats as they actually scan me rather then all the time so I can tell their mode. Even elevation indicators give you clue about the range to the enemy if they are working or not.

Well what do you all think of this It is written in ED manual of limitation where upon correctly identifying a F category signal all CW signals (X) are ignored Su-27 radar shows X category 7-8 bars on SPO, and its radar is same power output with antennas of SPO in similar position behind and to the side ED said recently they will add option to have blanking of front hemisphere removed as it was on many production models If so, with the above limitation, will it not upon identifying a high pulse repetition frequency HPRF/MPRF (F category) signal then shut off the display of the X category signals from Own ship radar and show F category as priority if nothing else non CW is higher priority? Что вы все об этом думаете? В руководстве по ограничению от ED написано, что при правильном определении сигнала категории F все сигналы CW (X) игнорируются. РЛС Су-27 показывает 7-8 полос категории X на СПО, и его РЛС имеет ту же выходную мощность с антеннами СПО, расположенными аналогично сзади и сбоку. ED недавно заявило, что добавит возможность отключения глушения передней полусферы, как это было на многих серийных моделях. Если это так, то с учетом вышеуказанного ограничения, не будет ли он при определении сигнала HPRF/MPRF с высокой частотой повторения импульсов (категории F) отключать отображение сигналов категории X от РЛС своего корабля и показывать категорию F как приоритетную, если ничто другое, кроме CW, не имеет более высокого приоритета?

I would love to hear from developers or someone about when the front hemisphere blanker is removed as an option as was said in the most recent SPO-15 post, IF the device may still show F category signals at less then 25-40 Km ranges with radar on becuase of the limitation where once correctly identified as HPRF/MPRF all CW signals are excluded, and Su-27 radar shows on SPO-15LM as 7-8 signal bars of X category (since Su-27 radar has same power output as MiG-29 radar and SPO antenna placement isn’t too different) so would thus be excluded when F category (MPRF/HPRF) signals are found, since 4th gen fighters go from X category (CW) to being correctly identified as F category (MPRF/HPRF) at 25 km (F-15/18) or 40 km (F-14/16), and the ED manual lists this as one of SPO-15LM’s limitations to ignore CW when MPRF/HPRF is correctly identified. This would mean the option of the blanker removed is nearly a perfect middle ground for all users and perfectly realistic

Yes. It’s one thing that non blanked SPO might be able to show other signals, but it’s another thing entirely if F category signals make it ignore its own radar completely and are shown as priority! To me and I would think for many pilots is a huge revelation about the usefulness of non blanked SPO, that it’s not just “super strong signals” but signals from 25-40 km! If this “limitation” is not a typo or a mistake, it changes the game I think quite a lot. If MiG-29 had originally launched like this, I think this thread would be much much shorter and the amount of complaints and talk about SPO much less

Well, if my theory is right, when the front hemisphere blanker is removed it should atleast show F category with radar on either as priority or secondary threat, as well as everything but medium range Sam (X-Hawk) and CWI (P). However F category only happens at 25-40 km range, so has that limitation It will make it feel less blind with radar

I think I was wrong about blacker removed, I re read this section on li its limits It says if a MPRF/HPRF radar is positively identified as F category it shuts off all CW signals shown on display! So if it’s really like Su-27 and radar shows as X category 7-8 bars, when we get F signal it will cut out the radar signal and show F as priority provided nothing non-CW is higher in the priority ranking! This would be pretty freaking awesome becuase it would mean SPO-15 would outright show F-15/18 within 25 km and F-14/16 within 40 km with radar on! And as a priority threat possibly! Also means the yugo pilots could’ve seen F category at close range! please tell me this is true and I’m not reading it wrong or crazy or something. I am so PUMPED if this is true, 25-40 km is all we need in 80s to protect ourselves! Su-27 manual “When the RLPK and L-006LM operate simultaneously, false information may be displayed on the L-006LM indicator (displaying bearing marks 10, 30, 50, 90 from the left and right, type X, power gradation up to 8, marks B,CAPTURE).” If true, that’s enough range to be as good as synchronized in my book! Please tell me I’m not imagining things! I would be so happy

The manual actually warns to make sure it’s off when CPG takes control!

The very same manual also says “ command to activate the quasi-surveillance mode (QSM)- the SQM 1 command. This command generates a signal for generating radiation by which the radar is switched on for emission. In addition, the Pkvo = 1 flag is formed, according to which the format of the coverage area No. I is selected (as in the case of instrument guidance, when d> 55 km (see Chapter 3). Control of the center of the coverage area of the RLPK complex is carrie out according to the target designation of the KOLS station.” So it seems to me that this scan pattern used with GCI below 55 km in PPS is “slaved” to the KOLS target, and the radar pulse at the center is recorded. It also later gives a table and shows quasi scan having the same 20 degree wide 10 degree tall scan as the less then 55 km PPS GCI scan. Perhaps it was easier to re use the GCI scan pattern the code instead of pure slaving. Im sure it was also chosen since it is the smallest scan pattern. But you also see the quasi scan/55+ km scan take 2.4 seconds, which must be rounded when manuals also say that quasi scan takes “3s” between updates. Unless it is actually taking 0.6s to process, I’ve seen a lot of rounding in MiG-29 manuals (I’m sure many of us have seen some say 9 degrees is when LEF are extended instead of 8.7 degrees). В том же руководстве также говорится: « Команда на включение режима квазинаблюдения (QSM) — команда SQM 1. Эта команда формирует сигнал на формирование излучения, по которому РЛС включается на излучение. Кроме того, формируется флаг Pkvo = 1, в соответствии с которым выбирается формат зоны обзора № I (как в случае приборного наведения при d> 55 км (см. главу 3). Управление центром зоны обзора комплекса РЛПК осуществляется по целеуказанию станции КОЛС». Поэтому, как мне кажется, эта схема сканирования, используемая с наведением на цель ниже 55 км в ППС, «привязана» к цели КОЛС, и импульс радара в центре регистрируется. Там же позже приводится таблица и показано квазисканирование, имеющее тот же обзор 20 градусов по ширине и 10 градусов по высоте, что и обзор ППС на цель менее 55 км. Возможно, было проще повторно использовать схему сканирования на цель Код в режиме ведомого управления. Я уверен, что он был выбран еще и потому, что это самый маленький шаблон сканирования. Но вы также видите, что квазисканирование/сканирование на расстоянии 55+ км занимает 2,4 секунды, что, вероятно, округляется, поскольку в руководствах также указано, что квазисканирование занимает «3 секунды» между обновлениями. Если только на самом деле обработка не занимает 0,6 секунды, я видел много округлений в руководствах по МиГ-29 (уверен, многие из нас видели, что некоторые говорят, что 9 градусов — это когда LEF выдвинуты, а не 8,7 градуса).

One technical question ED has said they would add an option to remove the blanking wire since most MiG-29 seem to have been that way after early production Now Su-27 manual says it’s radar shows up as X category 8 bars on its SPO, and I assume MiG-29 is the same as its power output is the same and placement similar. My question is this, the SPO-15 has a weakness where if it gets a CW signal, even CWI, it shuts off reception of all other CW/CWI signals. However, if a MPRF/HPRF radar is close enough for the SPO to detect the pulsed nature of it and correctly categorize it as HPRF/MPRF, it would still show it correct? And, I assume, it would show it over a weaker X signal, as the F category can only be recognized at a signal strength more powerful then X when MPRF/HPRF is recognized as flashing X. If so I would expect the removal of the blanking wire to make many people happy as it would show “F” signals within 25 km for F-15/18 and 40 km for f-14/16. For me, this is not much different then having the radar synchronization we would like! The only thing that could be better is having it be a DTC option in case the mission creator doesn’t do it In such a situation it would still be our responsibility to check when SPO switches from showing our radar to another, unless they are in a different mode then our own radar. However, if I understand the threat priority correctly, it might not show a F category in search over a X category in track. In such case, it would only show the F signal when in track mode and our radar In search if F category is truly lower priority then X (since it is said that priority goes in the order of categories left to right P Z X N F C.) In such a case it would still only show your radar as priority in track mode. In such a case, we might still be able to recognize its presence in search or track as a secondary threats in ours would only illuminate the X light and not the F light.

Here are some graphics I have made to show FOV of certain sensors and about SPO-15 It is different for PVP F-14 online, there is shows X+F category within about 40 km

It is odd It is as if originally only the lines at moment of radar ranging pulse were there. Then later they got range arrow to show with radar ranging and show measured closure for the 3-3.5 seconds after a pulse. But then left the original line implementation with the range arrow! If you turn IRST COOP on, even on ground the radar is pulsing every 3-3.5s even if it’s technically not radiating the light is going off and I assume it is in proper “equivalent/dummy” mode. It keeps doing this then when locked in IRST actually turns on. I’m sure you have my graph, in Helmet/OPT and vertical scan the radar is constantly on for STT within 10 km in a close combat mode, even though it won’t automatically lock in vertical scan until laser range (which has up to 4s second delay since laser is pulsing every 4s)

Why would this not be radar in catch up when you have the right switches set (brake forward and EKV)? You say it didn’t work that well in practice? Почему это не должно быть догоняющим радаром, если у вас установлены правильные переключатели (тормоз и EKV)? Вы говорите, что на практике это работало не очень хорошо?

Yes, but from what I read in manuals don’t you need guidance forward and radar in EKV? Or is this only for when on ground? Да, но, судя по тому, что я читал в руководствах, разве в EKV не нужны передний привод и радар? Или это нужно только на земле? Also interested if you ever used TP BB while rolling towards target and not still, in DCS the target needs to be practically stationary on ILS screen Также интересно, использовали ли вы когда-нибудь TP BB при движении к цели, а не при ее неподвижности, в DCS цель должна быть практически неподвижна на экране ILS. What is interesting we have quotes like this that make it sound like radar is slaved to TP in Coop TP leading, but this very same manual later says that quasi review actually uses the same scan pattern as Lazur long range guidance, a 20 degree wide scan, and only measures ranges when radar and TP coincide. This is where the 3.5 second scan/update rate comes from Интересно, что у нас есть подобные цитаты, из которых следует, что радар подчиняется траектории движения в кооперативном режиме, но в том же руководстве далее говорится, что квазиобзор на самом деле использует ту же схему сканирования, что и система дальнего наведения «Лазурь» — 20-градусное сканирование, и измеряет дальность только при совпадении радара и траектории движения. Отсюда и частота сканирования/обновления в 3,5 секунды.

1 is the range of selected fox 2 weapon, the short thick one Also, it marks each radar range with a line. Those are the lines that appear from your range arrow every 3 seconds. If you look on tele light panel and look at radar on light on the bottom right of it, you will see that these lines are generated at the range arrow every time this light comes on radar switch position doesn’t matter, IRST COOP will always force radar into pursuit mode, and radar ranging will always be a certain scan pattern with about 3-3.5 s update rate.

Well most people call it CCRP. The only difference is if the depression for the bombs at point of pressing trigger is more or less then 12 degrees. The ED manual doesn’t call it anything, and the official combat employment manual only calls it “bombing when target is in invisible zone” or alternately “bombing from horizontal flight” for the pitch up after holding trigger. There is no real “official” name for it. Either way, I hope my post helps.

Do you mean CCRP? You put reticle on target, hold missile launch (weapon release(, then keep the vertical fin of the aircraft HUD datum pointed at the reticle on top of the HUD. The range scale will turn into a second countdown until bomb release and give you tone 1 second before release. Additionally, you can pull up to loft bomb farther. If you pull up at 4-5 G, the aircraft HUD datum fin will extend and touch the reticle making it easier to line up with reticle perfectly. That’s all that’s needed, enter OPT, place reticle on target, hold weapon release, and keep flying straight or pitch up making sure your HUD fin is aligned with the reticle on top. To do this accurately, you really need to set target altitude in DTC to be close to correct and set your QNH on your altimeter to the briefing QNH If pipper moves up screen, you are close enough that it’s in CCIP mode now