RBE2 appears to have 2 upgrades proposed. One with the same architecture but probably some form of GaN implementation starting with the later F4 standard, and one redesigned radar, the RBE2-XG, fully utilizing GaN and with multiple improvements such as detecting and jamming simultaneously, for F5 standard
Tried to put a post on dev server discussion regarding the addition of exocet and stuff if anyone cares to add to it. Exocet could be provided to Rafale if it were added. Sea Eagle is being added on Hawk according to news, so the argument against exocet from the prior rafale thread no longer stands.
Also could be provided to Etendard IVM (french+argentinian), Super Etendard(french), Mirage 2000-5’s (through the greek one mount)
Yeah, been wanting Super Etendard to have it for a while.
@Mathll Would you believe they came up with a new argument to avoid exocet?
Lore accurate Rafale F5
for now, yes.
F4.2 is currently undergoing it’s earliest trials.
All ESAs got this radar change but this is a nice change for the Rafale since it really relies on HMD/ACM locks for firing off MICAs.

Kifir crying in the corner.
We don’t talk about that one.
Those are some oddly specific numbers lmao
They are probably derived from other values + floating point errors I guess ?
What is cas20 pattern
One of the ACM patterns
Combat Air Search 20, its one the ACM patterns from Blue Vixen, I think it was copied to a few radars;
The 20 is supposed to denote the max range in NM. So 20NM/37KM
Does the Sea Harrier FA2 even get CAS20?
There’s a report for the different ACM patterns of the rafale. Hopefully they’ll get implemented instead of copy pasting other modes as a generic stop gap.
Hello,
I’ve been having an issue for quite some time now where the TV sensor on the Rafale won’t slave to the radar target, whether it’s a hard lock or TWS mode, it just doesn’t seem to follow the radar lock.
When I take it into a test drive and set the radar to TWS mode, it initially works fine, the TV sensor slaves to the target as expected. But if I switch it off and try again, it completely stops working.
Is this just happening to me, or are others experiencing the same problem?
use the “deactivate target point” keybind

