Thallios Posted January 29, 2021 Share Posted January 29, 2021 In the Attack Radar A/A the bar settings are displayed incorrect. All possible bar settings are displayed (see picture) Link to comment Share on other sites More sharing options...
Tholozor Posted January 29, 2021 Share Posted January 29, 2021 (edited) Moving the TDC over the bar scan will display all available options. Moving the cursor over an option and using TDC Depress will select that option. The same action can be performed on the azimuth scan at the bottom of the display. Edited January 29, 2021 by Tholozor 1 1 REAPER 51 | Tholozor VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/ Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/ Link to comment Share on other sites More sharing options...
Thallios Posted January 29, 2021 Author Share Posted January 29, 2021 Thanks my fault Link to comment Share on other sites More sharing options...
Jak525 Posted January 30, 2021 Share Posted January 30, 2021 Well, there does seem to be a bug here in that the possible bar options are being displayed without the cursor over them. I noticed this can happen sometimes. When the cursor is not over the region it should simply display as normally. Link to comment Share on other sites More sharing options...
July Posted February 12, 2021 Share Posted February 12, 2021 (edited) Bumping this thread, this behavior definitely can't be considered correct can it? As Jak as previously stated, the bar options are all shown despite no TDC placement. This leaves us unable to see what bar scan we are in for both TWS/RWS. I can attach a .trk if needed. Edited February 12, 2021 by July Link to comment Share on other sites More sharing options...
July Posted February 12, 2021 Share Posted February 12, 2021 (edited) Track file here. https://drive.google.com/file/d/1bsNYBC-Htkz0ZgVHRMS5sBlPp2SLA_nn/view?usp=sharing Edit: I've tried to watch this .trk myself, turns out I can't due to some kind of error. Potentially because the .trk is from a multiplayer game. I have no idea how to replicate the bug, nor do I know any steps related to the bug appearing other than being in A/A mode. Hopefully this .trk works for someone else. Edited February 12, 2021 by July Link to comment Share on other sites More sharing options...
Recommended Posts