So, the SPO-15 has less signal processing than western radars so it doesn’t get infinitely variable signal detection angles or range calculation, and that’s totally fine. But it’s a huge issue that it’s IRL advantage over western RWRs of the same era, that being target elevation, isn’t modelled in game. And, though it doesn’t have range calculation, it does have signal intensity, which would still be useful information (especially with fox-3s coming soon).
In the dev server, they accurately modeled the functionality of the SPO15 RWR in the Su-27 cockpit, but I don’t know why this feature was removed in the live server.
I hope they model the fact that you cant use the SPO-15 alongside the radar on the MiG-29 and Su-27 as well, would be a great balancing factor for the R-27ER, and would be realistic
“When the RLPK and L006LM are operating simultaneously, it is possible to display false information on the L006LM indicator (displaying bearing marks 10, 30, 50, 90 on the left and right, type X, power gradation up to 8, marks B, N and CAPTURE).
To determine the actual situation, it is necessary (if possible) at the stages of searching and detecting a target to set the IZLUCH-EKV-OKL switch on the RLPK control panel to the OFF position for 5-10 seconds.”
It isn’t a malfunction, its a specific design limitation of their radar/RWR system, and I’d argue it very much should be modelled. Russian players having to decide between using their radar and being blind to their RWR or vice versa would be a great way to balance out the oppressive R-27ER as well.
This isn’t a case of “your final drive has a 15% of shearing, leaving your tank undriveable”, or “high AOA maneuvers have the potential to cause compressor stalls”. This is “if you turn your radar on, your RWR will not work, as the radar will interfere with its function entirely.” Its not a random occurrence, its a known inability of the system.
It would also increase the value of the MiG-29SMT, as its radar and RWR would work at the same time.
It is not a design limitation, the cycle of operation ensured the RWR would only receive signals in between the aircraft’s radar pulses. On the Su-27SK such thing could’ve been caused on very rare occasions by the fact it uses a degraded export variant of the RPLK-27 Myech. There has been no other report on this aside from German and Ukrainian MiG-29 pilots and the only possible reasoning would be shoddy maintenance of the radar links which could’ve led to desynchronization of the RWR and Radar cycle.
@Gunjob isn’t it you that has the official russian Su-27 manual that states the radar and RWR cannot be operated simultaneously? I know someone has it, and ive read (and laughed about) it before, but i dont remember exactly where it is atm.
Edit: found the comment with the excerpt at least:
Hello,
the claim that the person is a fighter pilot is really irrelevant, their profile on the DCS forums doesn’t even mention this.
Regarding what you sent, first and foremost SPO-15LM is not used on the Su-27 or Su-27SM, therefore Fighter29’s excerpt is useless to the discussion.
Same goes for the Su-27SK manual that gunjob mentioned, Su-27SK uses a different, downgraded suite than either flanker in game, not only that, it mentions it as a possibility, not as a guaranteed occurence.
As for the SPO-15 base model, the operation cycle is programmed in a way that the RWR system only temporarily pings in between radar pulses when both systems are operational thanks to a synchronization unit.
MiG-29 mechanics have verified this in response to the German MiG-29 vs Tornado BVR mock combat where similar claims were made regarding RWR operations. This issue only ever appears when the radar links in the system suite are broken due to insufficient maintenance, a well maintained fighter does not experience these issues, which precisely translates to the game, all vehicles are in perfect condition.
