I think i found out what the issue is with the TWS+ radars.
Instead of updating the target whenever the radar beam passes over it, the target gets only refreshed when the whole scan pattern finishes.
So the target gets only refreshed by the TWS+ updates and the radar dosent give normal target updates anymore
That would do it
Yeah leave it up to Gaijin to create more issues, while trying to fix an issue
I cant think of a time where Gaijin has actually fixed a problem without creating a new one
best example of that is the whole Mig-29 situation
@Morvran have an more Up to date one
*Duplicate
Still have no idea why they pretend they cant just use the AESA code to model P-Track for CAPTOR-M and PS-05/A Raven. Its incredibly easy to do…
because that way they have to set the refresh manually for every scan pattern, for every mechanical radar that got TWS+
Yeah… But apparently that would be unfair according to the French guys because it would have to have latency modeled. Not that I really understand why it would cause any latency actually
See, still wanted to add more Internal reports which Gunjob said here…
Would be cool to see everything submitted. Even if not an specifics, just the title
I also wonder whether you should include BOL related reports on that list too
https://community.gaijin.net/issues/p/warthunder/i/B8OvCzjZ7E91
I am pretty sure I got that allready
Turned out it was in an diffrent Collection of the DC…
Well, know its on the EF as well
I mean, not really, it would work literally the exact same way as the devs have the ESA radars modelled, but would just have an increased time between updates due to the lower scan speed. They already have the entire code laid out for them, all they need to do is input the appropriate CAPTOR-M and PS-05/A values instead.
Heck, in the most recent major update, they improved the priority track code for the RBE2-AA allowing it to track stuff outside its current scan zone. Thats quite literally what the bug report for priority track for the CAPTOR-M states it can do:
Also, afaik the only 2 mech scan radars capable of P-track are the CAPTOR-M and PS-05/A Raven, so they cant even use the excuse that too many radars would need changes. They’re either being outright lazy or biased.
This reminds me a lot of when they swore up and down that they could not make the MUSS soft-kill APS on the Puma IFV react to threats, saying they “did not have the code for it”. I suggested they should just use the code from the hardkill APS’ already in-game but just make it so the effector was the laser jammer instead of a projectile. 2 years later thats exactly what they did.
They have the code, they’re just too lazy to do anything with it.
Just for fun, these 2 blurbs of code should be roughly what P-track would look like on the EFT (with the current state of the radar) using the ESA code already in-game (unless I missed something):
Instead of updating targets every 0.04s like on the RBE2-AA, it updates them every 2 seconds. Still 5000% slower than the RBE2 for example, but it would be ~42% faster on the medium scan pattern and 50% faster than the wide pattern. Itd be slower than narrow pattern for tracking a single target, but would also allow the radar to update targets outside its currently selected scan zone every 2 seconds, and wouldnt influence the track rate of the narrow scan anyways.
P.S: I also adjusted the brackets from gaijins code cuz the way they bracket their code bugs the heck out of me…
2 seconds is probably waaaay too long of a latency. I reckon 0.5-1 second is more than accurate, maybe have it 0.08 seconds per target if that is possible for them to code
No, 2 seconds is accurate as per the sources on P-track. The radar scan volumes in-game are wildly inaccurate. iirc they should all be 140deg with varying numbers of bars (1, 2, 4, 6, 8), with P-track working by jumping the radar to a target when the radar crosses its azimuth. 2 sec p-track is the approximate time between each point at which the radar would cross the targets azimuth to be updated (140deg/70 deg/s = 2sec)
