View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000089 | Falcon BMS Known Bugs | TE | public | 2021-02-07 13:34 | 2021-02-10 23:50 |
| Reporter | anonymous | Assigned To | Blu3wolf | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | PC | OS | Windows | OS Version | Windows 10 |
| Product Version | BMS 4.35 | ||||
| Summary | 0000089: The TE's only SAM battery continues to fire after the destruction of its 2 radars. | ||||
| Description | TE virgin. Default Korea. A single battery / battalion of SA5 deployed and nothing else. After AGM 88 destroyed the acquisition radar and firing range radar (destructions confirmed by the debrief and ACMI), the battery continued to fire its missiles. At the RWR, alert "5" is always present every time a missile is sent or in flight. Admittedly, there are detection radars natively implanted on the map of the theater and the infovalorization of the ground-to-air defense seems implanted, but I find it surprising that they are able to conduct the firing of a SA5 missile, without the help of another firing guidance radar of another battery/battalion (non-existent here therefore). If proven ?, major bug? because it is therefore impossible to destroy the SA5 in TE. No such problem with the 4.34 U4. | ||||
| Steps To Reproduce | See SA5 files | ||||
| Tags | No tags attached. | ||||
| Theatre of Operations | KTO | ||||
| Seems like the SA2 or SA3 site take over ... but they are empty on a TE map (normally ?). | |
| ACMI | |
|
Zut ... Note that in the tacview acmi, missiles fired after the destruction of the two radars are not "marked" as events. |
|
|
In fact, there are three radars in the SA5 battalion: - Bar Lock - Odd Group - Square Pair something I didn't know, if that's how it's meant. The destruction of the two radars corresponds to the destruction of the acquisition radars: the third being that of the firing line, it is normal that the SA5 continues to fire. If the presence of a 3rd radar is normal, you can close. Note, however, that the Odd Group seems to display "2" in the RWR (like SA2). |
|
|
Looking at the ACMI, your first 88 hit the Odd Pair height finder (a towed vehicle from an SA-2 site - thus the '2' - google the wiki article) and your 2nd 88 hit the Bar Lock (EW radar). The Square Pair (FC radar) remains active and assumes the role of search & destroy, spewing missiles at will. The Odd Pair and Bar Lock are "continuous duty-cycle" radars meaning they are (almost) always on looking for you. The Square Pair only turns on when there is firing solution (you are in range) and stays on while supporting a missile. 4.35 introduces the TI options, and my guess is you fired on the Square Pair (radar signature 5) and since it was not active (it stays quiet until needed to "snipe" you) the 88 "FLEX'd" to the next available SAM threat ( the Height finder and EW radar) because they were painting you. In 4.35, the threat tables have been expanded to allow specific targeting of most radars. Study the -34 and the Training Manual to learn the new complex features of the AGM-88. If it were me, I would have fired once on the 'B' (Bar Lock) since it was likely continuous in the RWR and the HARM was unlikely the FLEX (use SD if you want to be sure). Once the Bar Lock is down, the Square Pair will come active (nearly continuously) to locate you. A 2nd shot with TI set to SD would kill it and render the site harmless (no pun intended). |
|
| Sounding like not a bug? | |
|
Now that I have discovered that there are (in the 4.35) 3 radars in the BATTALION of SA5, this is not a bug. Now, if it is unintentionally that there are 3 radars, perhaps one should be removed. There were only 2 radars in previous versions, as in all other SAM battalions. |
|
| Thanks Zipgun | |
| It is intentional for added realism, BMS just keeps getting better! | |
| Closing per Zipguns comments. If its decided that additional radars constitute a bug with the SA-5, please open a new bug for that instead of re-opening this one. Thanks for reporting. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-02-07 13:34 | anonymous | New Issue | |
| 2021-02-07 13:34 | anonymous | File Added: sa5.tac | |
| 2021-02-07 13:34 | anonymous | File Added: sa5.twx | |
| 2021-02-07 13:34 | anonymous | File Added: sa5.iff | |
| 2021-02-07 14:30 | anonymous | Note Added: 0000229 | |
| 2021-02-07 17:20 | anonymous | Note Added: 0000230 | |
| 2021-02-07 17:20 | anonymous | File Added: SA5.zip.acmi | |
| 2021-02-07 17:24 | anonymous | Note Added: 0000231 | |
| 2021-02-08 13:48 | anonymous | Note Added: 0000232 | |
| 2021-02-09 16:48 | Zipgun | Note Added: 0000233 | |
| 2021-02-09 21:03 | Blu3wolf | Note Added: 0000234 | |
| 2021-02-10 07:49 | anonymous | Note Added: 0000235 | |
| 2021-02-10 08:29 | anonymous | Note Added: 0000236 | |
| 2021-02-10 09:17 | Zipgun | Note Added: 0000237 | |
| 2021-02-10 23:50 | Blu3wolf | Assigned To | => Blu3wolf |
| 2021-02-10 23:50 | Blu3wolf | Status | new => closed |
| 2021-02-10 23:50 | Blu3wolf | Resolution | open => no change required |
| 2021-02-10 23:50 | Blu3wolf | Note Added: 0000238 |