CoBlue Posted June 5, 2020 Posted June 5, 2020 (edited) Latest OB. HUD, TACAN Command Steering missing. See pic. Also what are the TACAN numbers on HSI when TACAN boxed? pic nr2. Edited June 5, 2020 by CoBlue i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.
Harker Posted June 5, 2020 Posted June 5, 2020 Not a bug. Once you input a course, you navigate based on the courseline arrow on your HUD. As for the numbers, the first one is calculated remaining fuel at that destination and the second is letting you know when to start your descent towards the destination, from your current altitude, in order to maintain optimal fuel performance. 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
norman99 Posted June 5, 2020 Posted June 5, 2020 Unfortunately the descent distance never makes any sense for me. It doesn't make much sens in the above example either, 35nm - 14nm means it's indicating a top of descent with about 20nm to run, from 25,000ft. It should be more like 40-50nm, if using a standard idle, 250kt descent. Not sure if it's WIP or just screwed up.
Tholozor Posted June 5, 2020 Posted June 5, 2020 Whenever I follow the indicator to begin descent, it always places the point I'm navigating to exactly at 10° below the horizon. 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