View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000182 | Falcon BMS Known Bugs | Avionics | public | 2021-06-12 12:02 | 2021-06-18 17:06 |
| Reporter | LorikEolmin | Assigned To | |||
| Priority | low | Severity | minor | Reproducibility | sometimes |
| Status | new | Resolution | open | ||
| Platform | PC | OS | Windows | OS Version | Windows 10 |
| Product Version | BMS 4.35 U1 | ||||
| Summary | 0000182: TACAN bumps up in package upon flight destruction | ||||
| Description | I hesitated to check "always", I think it's actually a rule. Package is made of Flight n to Flight n+4. When Flight n is destroyed (maybe just Lead? Not sure), Flight n+1 gets Flight n's default AI TACAN. For instance, Number 2 in Flight 2 gets TACAN 22Y instead of 23Y, while in flight. "Minor", because it just needs to be known, to retrieve a correct TACAN and A/A distance to other aircrafts. It deserves being wide-known for solo flyers, though. | ||||
| Steps To Reproduce | Try that in a campaign. Not sure in a TE. Flying in Flight 0000002 permits to see it clearly when Flight #1 is destroyed (suicide mission should work). | ||||
| Additional Information | Radio transmission may also be altered (wingman reporting weapons use for instance). | ||||
| Tags | TACAN | ||||
| Theatre of Operations | KTO | ||||
| *widely known | |
|
side note: a hash (#) followed by a number is interpreted as a link to issue number #, if it exists. So issue (# 2) is replaced as 0000002. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-06-12 12:02 | LorikEolmin | New Issue | |
| 2021-06-12 12:02 | LorikEolmin | Tag Attached: TACAN | |
| 2021-06-12 12:03 | LorikEolmin | Note Added: 0000599 | |
| 2021-06-13 22:52 | Blu3wolf | Note Added: 0000602 |