So after some testing i currently see some problematic things with the current dev server build for the Rafale
1: with the TV sensor fusion, if you use tws, it will override your MAP MARKER if you are doing some air to ground strike. So you have to choose between losing situational awereness with your radar off (or another mode), or hoping to NOT catch something on your radar before and during dropping AGM or BOMB. Since the TV sensor will prioritize the radar target.
Possible workaround: create a new type of marker which difference Map marker from pod marker (one is red, the other is another color), and/or create a new view, to difference TGP from the TV sensor?
2: The 140x31 scan bar is problematic to use if the target is not at the same level as you, in TWS the radar will focus on the target which will create this problem, if the target is below or above you. Which make you lose WAY too much situation awereness. In this case, the TWS is not adapted for an AESA radar.
Possible workaround: a rework of tws for a specific use of AESA TWS? so TWS can stay at level while updating the target position time to time even if the target is too low or too high.
3: The current locked target displayed on HMD look like more a workaround instead of real display of locked/tracked target. If you look closely, they are currently using TGP marker “MRK A” as a reference point but you can’t still see multiple target in your HMD, only the one focused by the radar in TWS.
We are far from the same level of the Typhoon HMD, to display multiple tracked targets. (Still a very nice addition)
For reference: Typhoon Hmd multiple tracked targets vs Rafale not able to display multiple tracked targets
Spoiler
4: The current scan rate (speed scan) is abyssal for 140x31. I did lose with an AESA radar, a target (even with the new update of scan bar : 1,2,3,4 to 1,2,3,4 instead 1,2,3,4 to 4,3,2,1.), just because the scan rate is too slow to manage the 140x31. Is an AESA scan rate speed is this “low” in reality?
Possible workaround: with the current speed scan, it will be great to have other options as 140x16 aka 7 vertical bar to scan (we already have a 30x16 and 70x16) scan or/and a 140x3 aka 1 vertical bar to scan (same as mirage 120x3) will be a great option for this.
5: Again still the same issue (eurofighter has the same issue too) The first scan in TWS has an high chance to not pick up a target even in Head-on, in many case you need still at least 2 scan in the same area for
Possible workaround: Again a scan with “XnumberX3” (a one vertical bar scan: for exemple 140x3 120x3 70x3 30x3) will nullify this problem, as a short band aid. or for the longer term fixing the TWS with multiple vertical bar
