Tholozor Posted November 16, 2023 Posted November 16, 2023 (edited) Currently, the AACQ legend will overlap with the bullseye-to-cursor readout in the top-left corner of the ATTK display. I found this quite odd, even after seeing documentation showing both in the same area without mentioning any type of swapping/priority logic, so I did a little digging for real-world examples. I found helmet camera footage from the U.S. Hornet East Demo Team (video source) which just so happened to have the ATTK format pulled up. It also has the bullseye-cursor data shifted slightly to the right compared to the position in DCS. Full disclaimer, I am aware the video was taken in 2010, so a later OFP may have changed the position of this data block after the version the DCS version represents. This example was the oldest I could find that had the ATTK format present on a Legacy Bug on video, if anyone has older examples, please feel free to share. Since the DDIs don't display the full raster on a digital recorder, I took various frames and warped them to the same orientation and overlaid them to present a more complete picture of the ATTK format. The out-of-display bullseye symbol can be seen just below the spacing between the bar scan and current bar legends. Edited November 16, 2023 by Tholozor 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/
Spock14 Posted November 16, 2023 Posted November 16, 2023 I´ve heard it from multiple USMC and USN Pilots that it never overlapped
ED Team BIGNEWY Posted November 16, 2023 ED Team Posted November 16, 2023 We will investigate, but we will likely need better evidence. thank you Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Harker Posted November 16, 2023 Posted November 16, 2023 @Tholozor is right. The TDC Bullseye data window should be moved to the right, to make space for the acquisition cues (AACQ, ACM modes). This is a picture from a recent Super Hornet professional simulator (not a game), so not at all the same, but the position of the cursor Bullseye data is clearly shown, and that part has not changed. 1 The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
ED Team Lord Vader Posted November 17, 2023 ED Team Posted November 17, 2023 Hi all. Even without accurate visual references, the overlapping seems wrong. I am raising this internally for analysis. If you do happen to acquire non-classified information, even pictures, please send to @BIGNEWY. Thanks. Esquadra 701 - DCS Portugal - Discord
Harker Posted November 20, 2023 Posted November 20, 2023 On 11/17/2023 at 11:51 AM, Lord Vader said: Hi all. Even without accurate visual references, the overlapping seems wrong. I am raising this internally for analysis. If you do happen to acquire non-classified information, even pictures, please send to @BIGNEWY. Thanks. The radar page at 19:10 also shows the Bullseye legend moved to the right compared to DCS. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Tholozor Posted November 20, 2023 Author Posted November 20, 2023 Nice, I remember that one from the thread about the faster cursor speed. You can also see there seems to be a spacing between the forward slash and where the hundreds value would be for the bullseye range. 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/
Harker Posted November 21, 2023 Posted November 21, 2023 You can also see there seems to be a spacing between the forward slash and where the hundreds value would be for the bullseye range.Yes, the number values seem to have right text alignment, and both be at fixed positions, respectively. That way, the / between bearing and range always remains at the same place and it's easier to read the values at a glance. The vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord. F/A-18C, F-15E, AV-8B, F-16C, JF-17, A-10C/CII, M-2000C, F-14, AH-64D, BS2, UH-1H, P-51D, Sptifire, FC3 - i9-13900K, 64GB @6400MHz RAM, 4090 Strix OC, Samsung 990 Pro
Tholozor Posted February 22, 2024 Author Posted February 22, 2024 Partially fixed after today's update. The bearing and range is shifted over, but the AACQ legend still overlaps with the symbol denoting the Bullseye is out of the scope of the tactical region. 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/
Recommended Posts