dresoccer4 Posted May 29, 2018 Posted May 29, 2018 another quick question. i notice when i'm lasing a target, there seem to be two very different distances show in the MFD and the HUD. and often times there are 2 overlapping distances in the HUD. in my example screenshot the distance to target is 9.4nm while in the right MFD it says 8.7. can someone explain the difference? in the second screenshot you can see the 2 overlapping distances trying to fight it out to be seen. looks like 8.8nm and 8.1nm overlapping [ATTACH]185661[/ATTACH] [ATTACH]185663[/ATTACH] Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Mumby Posted May 29, 2018 Posted May 29, 2018 (edited) another quick question. i notice when i'm lasing a target, there seem to be two very different distances show in the MFD and the HUD. and often times there are 2 overlapping distances in the HUD. in my example screenshot the distance to target is 9.4nm while in the right MFD it says 8.7. can someone explain the difference? in the second screenshot you can see the 2 overlapping distances trying to fight it out to be seen. looks like 8.8nm and 8.1nm overlapping [ATTACH]185661[/ATTACH] [ATTACH]185663[/ATTACH] 9.4 must be slant range, 8.7 is range over the ground. Your alt is 21830ft in the first image, which is 3.59 nautical miles (3.45 nm in the second image) sqrt (3.59^2 + 8.7^2) = 9.4 (Pythagoras' theorem) sqrt (3.45^2 + 8.1^2) = 8.8 Cheers P p.s. I also have the overlapping numbers in the HUD. Annoying. Edited May 29, 2018 by Mumby
dresoccer4 Posted May 29, 2018 Author Posted May 29, 2018 Thanks! Makes sense the MFD would give ground distance. Guessing the overlap is a bug Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Eagle7907 Posted May 30, 2018 Posted May 30, 2018 I’ve also noticed that the INRNG cue on the HUD comes on way too close. Like less than 6 miles when at altitude. Sent from my iPhone using Tapatalk Pro Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer
Zeus67 Posted May 31, 2018 Posted May 31, 2018 (edited) I’ve also noticed that the INRNG cue on the HUD comes on way too close. Like less than 6 miles when at altitude. Sent from my iPhone using Tapatalk Pro The INRNG cue follows a curve table for the AGM-65 that is based on launch platform mach number and launch altitude. P.S.: I'll fix the overlapping numbers. Edited May 31, 2018 by Zeus67 "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
dresoccer4 Posted May 31, 2018 Author Posted May 31, 2018 P.S.: I'll fix the overlapping numbers. right on Acer Predator Triton 700 || i7-7700HQ || 512GB SSD || 32GB RAM || GTX1080 Max-Q || FFB II and Thrustmaster TWCS Throttle || All DCS Modules
Eagle7907 Posted June 1, 2018 Posted June 1, 2018 The INRNG cue follows a curve table for the AGM-65 that is based on launch platform mach number and launch altitude. P.S.: I'll fix the overlapping numbers. Ah okay. That makes sense, so it would be correct to wait for the cue? Forgive me for noob question. Sent from my iPhone using Tapatalk Pro Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer
Recommended Posts