Hello, I have an issue with the tracking radar and IRST sensors of the CS/SA5. If anyone can help, I need to know the current ingame numbers for the maximum vertical gimbal limit of the tracking radar, it’s vertical FOV and the vertical FOV of the IRST sensor.
Reason for this is, that it looses lock when a target or munition is directly above it (90°) even though I am very certain that the FOV of both tracking radar and IRST are large enough to compensate for the missing 5° in gun elevation (assuming the maximum vertical gimbal limit is 85°, just like the gun).
Important note: This is not the same issue as loosing the lock when a target flies over you. This is an issue of munitions such as the french AASM 250 HAMMER (SBU 64) guided bomb dropping from straight ontop of me and both my sensors being incapable of tracking them anymore.
Problem is, neither do I know the FOV numbers, nor do I know the maximum vertical gimbal limit of the track radar sensor, so I can’t prove an issue in a bug report.
IIrc this is my first ever forum post so I apologise if I mislabel something but this issue is genuinely driving me nuts.
Radar has a elevation limit of 75°, IRT has 82°
As Tracking Radar and IRT are one and the same system, they both suffer from the fact of being c&p of the pantsir (values match 1:1, who would have guessed)
Okay, thank you very much. Though I do have to ask - as I am not an expert on this stuff - but doesn’t this then mean that it should have enough FOV to keep tracking bombs dropping from 90° ontop of me? It would still be important to know what their respective FOV’s are.
On another note, I have noticed a severe irregularity of the SA5’s tracking quality, a few matches ago today it happened where it lost a perfect lock on both an MQ-1 and a Hellfire flying straight toward me. The PGZ-625 TT was incapable of regaining a track.
Another question, if these are indeed copy and paste of the Pantsir, then I have to ask why the tracking quality seems worse?
This is not the first instance it has happened, which is why I am trying to understand this issue.
What you read here is, the “rangemax” that is max range of the radar, but more importantly “range”. That value determines at what range the radar detects a set above “rcs” target. As pantsir has a greater “range”, it means its radar will be able to track smaller targets much better. That will be the main issue here.
Example: Assume there is a flying block with RCS of 1. Pantsir will be able to track it at 36km, but CS needs to wait untill the target is within 20km.
Other than that the only changes are ranging in IRT for CS and NCTR for Pantsir. The rest of the code is identical. They just changed the range to be smaller.
Again, thank you alot for the thorough explanation. The “azimuthLimits” are then I assume are the FOV’s? But then I don’t understand why the IRST has an azimuthlimit of 90° both directions.
Colour me surprised but I’d have thought, that when my tracker elevates to - in this case 75° and then has an FOV large enough to cover the missing 15° that the track would continue. To me that seems like a coding oversight by gaijin and in all honestly pretty annoying when we are using drone and munition interceptors such as the SA5. Wonder if the Skynex/Skyranger will have the same issues.
For something meant to intercept drones, I assumed that this machine wouldn’t have trouble tracking smaller targets, let alone spotting them on it’s (search)radar.
There is no such thing as FoV when it comes to tracking in game. It is a zone limited by the azimuth and elevation. Anywhere within that zone track is possible. The moment target moves out of that zone, track is lost.
On another note, remember that many system Irl can not track over their whole sensor FoV. Maybe the can track targets that are only in the middle. Maybe they can track within a circle starting from the middle and covering, lets say 50% of the total FoV. Maybe they can track over the whole FoV, but we don’t know it.
