they could’ve balanced this by reducing the amount of rails you can mount.
the current implementation juts screws everyone over
it might be balanced for the jets that carry 4 rails but aircraft that carry less (or loadouts that result in less carriage like bombs and such) just mean you’re completely screwed, even more so than aircraft without BOL rails
Some ppl have mentionned the ESA radars ingame already have a priority track mode implemented on them, with the radar updating targets even when the beqm isnt on them specifically at very short intervals. I havent looked into this much myself yet, but might be an avenue to look into.
If the claim is accurate, we could get P-track, and by extension a much better radar much quicker.
Yes, they update the targets that are within scan zone every time they switch bar.
if anyone can interpret the .blks here are the two radars (to see if there’s anything definite regarding the AESA updating targets):
https://github.com/gszabi99/War-Thunder-Datamine/blob/master/aces.vromfs.bin_u/gamedata/sensors/uk_captor_m.blkx
https://github.com/gszabi99/War-Thunder-Datamine/blob/master/aces.vromfs.bin_u/gamedata/sensors/fr_thales_rbe2.blkx
Had a thought. Should striker I still show IFF in the HMD overlay? Whilst I know the datalink IFF is a feature of striker II, I would figure that striker I could simply display the IFF information it receives from the radar. Currently it has the same marker for both friend or foe that the radar sees.
should probably have the same symbology as the HUD
but also this kinda goes into this direction
idk if this is correct but uh
if you look over here for the captor-m
this is the track stuff for TWS, it just ‘selects’ or ‘designates’ a scan target
for rbe2 its different:
it gets an additional track property
of interest is the “scantrack” section; it shows a scan period update time of 0.01 seconds which is what you see in game and the reason for why the tws lock is rock solid and and speed/direction changes are immediately visible. imo this is also why the direction arrow jumps around a bit as the update rate is so ridiculously fast.
captor-m doesnt have this yet. i’d maybe think that the update speed for it would be at best half a second but thats just a guess
Soooooo a P-track…
@k_stepanovich any reason why CAPTOR-M wasnt given the same priority track as the ESA radars? Its sitting as a suggestion right now
https://community.gaijin.net/issues/p/warthunder/i/P8Gb6ip55srm
Already displays HMD radar IFF, allies are circles and hostiles are diamonds.
They could set scantrack at the speed reqired to sweep 1 bar, so 1 sec for 70°, 2 sec for 140°, etc…
i guess
Either I have simply not noticed this or its not working on my end. I shall have a look next time I play and see
Ill take a screenshot later and post it
@Smin1080p_WT Can this answer be reviewed btw? As seen in the quote below, the feature DOES exist in-game, its simply limited to ESA radars like the Rafales RBE2-AA and Su-34 V004. Priority scan works the exact same way, itd just be a tad slower (updates once per bar, so dependent on the horizontal scan width).
Probably gonna tell you that the feature doesn’t exist like they did for radar based MAWS… even though they do exist, just on tanks with APS. Britain has one.
A reworked version of TWS is already in progress for modern radars like Typhoon. It’s possible this will be part of that update as that is one of the primary reported issues with radars like CAPTOR over earlier more basic TWS searches.
Can you tell us what’s there?
Looking forward to seeing it in action in the future, thanks for the heads-up :)
someone with knowledge on how to make user models could probably make a preliminary test vehicle with a captor-m and that scantrack
it might be possible to copy the files, keep the same model, and tweak what you want? i don’t have any experience but i guess that’s how the meme user vehicles were done (like the KV-2 with the massive dart and the plane that had the recoil from 15” guns)
I wonder if in the “reworked” radar the contact will be tracked only on bars or outside of them too?
As far as I remember, the trick is that it tracks everything it has in its memory on each bar pass.