View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000060 | Falcon BMS Known Bugs | Avionics | public | 2021-01-18 03:44 | 2021-01-18 03:44 |
| Reporter | anonymous | Assigned To | |||
| Priority | normal | Severity | trivial | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | PC | OS | Windows | OS Version | Windows 10 |
| Product Version | BMS 4.35 | ||||
| Summary | 0000060: Offset Aimpoints implementation | ||||
| Description | * OA1 and OA2 should be relative to a STP so when you apply system deltas to that STP, OA1 and OA2 should follow. In BMS they don't, they are permanent in relation to the original STP. However, they do follow the STP once you mode select VIP/VRP. I highly doubt that this is an intended behaviour. * Moreover, the behaviour of the targeting box seems to be incorrect as well. The idea behind OA is that the radar cursor and SPI point to the OA but the targeting box and HUD cues point to the STP. IN BMS the targeting box follows the selected OA. * OSB 10 changes between STP and OA, it works on the FCR but does not work on the TGP. | ||||
| Steps To Reproduce | Jump into the cockpit and create Offset Aimpoints around a STP in AG mode. Observe how the STP moves when you slew the radar cursor but the OA stay fixed. Also change OA through OSB 10 and observe how the targeting box and the bomb fall line switch to OA ad do not stay on the STP. | ||||
| Tags | No tags attached. | ||||
| Theatre of Operations | KTO | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-01-18 03:44 | anonymous | New Issue |