For MPQ-64, it should still be implemented however. I think the current code allows for the TWS ESA part to have a different sector size. Would make each scan cycle have more accurate TWS updates.
Though I think the reason why TWS ESA isn’t implemented for most ground radars is because they are rotating. And how they simulate that is by having a “fixed” radar with 360° horizontal coverage. So there’s no “front” of array concept in-game unless the array has a fixed position (hence why the Pantsir/TOR/BUK, etc have it on their fixed arrays), with the front of a fixed array being related to the turret position instead. So if TWS ESA was added to “rotating” radars now, they would have continuous update of all trackfiles in a 360° radius (or if sector limited, it is pointing always in the same direction), regardless if the radar is even pointing in the relevant direction.
Spyder is an interesting one, having actually 4 fixed arrays irl, but in-game I believe it’s just simulated as one singular 360° rotating radar with 4 evenly offset beams. For this radar though, they could just add TWS ESA, because of its configuration.
So I think for TWS ESA to work on rotating arrays, Gaijin needs to couple the radar scan pattern with the physical rotation of the model of the radar antenna. Then they can get a “front” and do correct TWS ESA updates. Or at least some way to shift the “front” with rotation. But I can see that coupling model and scan direction may cause some spaghetti (net)code issues, especially the faster the radar rotates.
It seems they’re trying to sweep under the rug numerous bugs—like Tan-SAM’s radar operation, IRH’s LOAL, and mixed missile loading—by overwriting memory with the new SAM, making it hard to believe the Type 03 will be properly implemented.
I hope Tan-SAM gets fixed alongside the Type 03’s implementation.
