bbrz Posted July 25, 2019 Posted July 25, 2019 Precise enough because imacken assumed that the precision of RA is required. i7-7700K 4.2GHz, 16GB, GTX 1070
imacken Posted July 25, 2019 Author Posted July 25, 2019 Precise enough because imacken assumed that the precision of RA is required. Don't know where that came from. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Eviscerador Posted July 25, 2019 Posted July 25, 2019 You can set QFE on your altimeter in NEVADA and work with Nellis altitude as zero to ease your calculations. Once the TGP comes, you will be able to read the GPS altitude of the designated point on there, like on the A10C. Other than that, use the F10 map and do the math. [sIGPIC][/sIGPIC]
bbrz Posted July 25, 2019 Posted July 25, 2019 You can set QFE on your altimeter in NEVADA and work with Nellis altitude as zero to ease your calculations. ? How would you do that since the altimeter setting range is only from 28.10 - 31.00. i7-7700K 4.2GHz, 16GB, GTX 1070
bbrz Posted July 25, 2019 Posted July 25, 2019 Don't know where that came from. https://forums.eagle.ru/showpost.php?p=3988136&postcount=15 i7-7700K 4.2GHz, 16GB, GTX 1070
imacken Posted July 25, 2019 Author Posted July 25, 2019 https://forums.eagle.ru/showpost.php?p=3988136&postcount=15 https://forums.eagle.ru/showpost.php?p=3988122&postcount=11 We're talking at complete cross purposes here! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
imacken Posted July 25, 2019 Author Posted July 25, 2019 ? How would you do that since the altimeter setting range is only from 28.10 - 31.00. This begs the question I've always wondered, what is the reason for this restriction? Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box
Ramsay Posted July 25, 2019 Posted July 25, 2019 (edited) You can set QFE on your altimeter in NEVADA and work with Nellis altitude as zero to ease your calculations. AFAIK the weapons computer uses MSL (QNH) or the GPS reference ellipsoid for the aircraft's altitude and waypoint data or DTED for the target's elevation i.e. • if you are are 25,000 ft MSL Baro and the terrain below at 5,000 ft MSL - you are assumed to be 20,000 ft above the target's elevation. • if you set QFE so the baro reads 20,000 ft (at 25,000 ft MSL) and the terrian below is at 5,000 ft MSL - the weapons computer will assume you are 15,000 ft above the target's elevation. You can set QFE for circuits if it's within the mechanical range of the instrument and QNE (29.92 inHg) for ferry flights/while enroute but AFAIK, you should/must set QNH when fencing in. Edited July 25, 2019 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Eviscerador Posted July 25, 2019 Posted July 25, 2019 ? How would you do that since the altimeter setting range is only from 28.10 - 31.00. IIRC nellis airbase is at around 1800 ft. That is around 28.20 on a sunny day. Of course if you have a low pressure front that's another story. [sIGPIC][/sIGPIC]
bbrz Posted July 25, 2019 Posted July 25, 2019 IIRC nellis airbase is at around 1800 ft. That is around 28.20 on a sunny day. Of course if you have a low pressure front that's another story. You don't need a low pressure front to make QFE unusable. KLSV 1870ft, KLAS 2181ft. @imacken, mechanical precision/complexity? Furthermore since QFE usually isn't used, this adjustment range for QNH ops is sufficient. i7-7700K 4.2GHz, 16GB, GTX 1070
Fri13 Posted July 25, 2019 Posted July 25, 2019 In the Harrier it’s the DMT/ARBS, in the Hornet/Viper the A/G radar should be used (this can be used to range the ground at altitudes much higher than your RADALT). I’m curious if this is currently reflected in the Hornets CCIP accuracy as it should substitute the need to know an exact target elevation. According to Raytheon's fact sheet for the Paveway 2, 99 deliveries of guided munitions will yield a circular error probable (CEP) of only 3.6 feet (1.1 metres), versus a CEP of 310 feet (94.49 metres) for 99 unguided bombs dropped under similar conditions. https://en.m.wikipedia.org/wiki/GBU-12_Paveway_II It would be interesting to know what is that "similar conditions". The targeting pods etc should be there to perform same capability as ARBS does, but A-G should be less accurate anyways, and if DCS would model then as well worse as ground units would detect the A-G radar emission. And someone here mentioned that real pilots he has been talking to, said that the hornet A-G radar was mainly used against ships, instead on ground targets. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
Harker Posted July 25, 2019 Posted July 25, 2019 There are several ways to get a target's MSL elevation, like marking a point on the ground or using the TGP. Most of these ways require that your aircraft is equipped with DTED, so it knows the elevation of that point on the ground. In my understanding, these methods are 2D, so the DTED database is required. Another way is to use A/G radar ranging, which can be most useful if the target is on a different elevation than the terrain under you. In DCS ou can see the effect of using radar ranging versus just the radar altimeter in the Mirage. It uses radar ranging when you activate TAS, in the A/G menu. 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
Browny Posted July 25, 2019 Posted July 25, 2019 May be a silly question, but I've often wondered, how do you get height above ground when altimeters only show barometric over 5,000ft? Hey mate the actual operational limits of the Hornet RADALT is 0 to 5000ft. therefore the RADALT won't operate above 5000ft.
Fri13 Posted July 28, 2019 Posted July 28, 2019 Hey mate the actual operational limits of the Hornet RADALT is 0 to 5000ft. therefore the RADALT won't operate above 5000ft. I believe that the altitude radar would operate, but it would become too unreliable at the higher altitudes like 6000-7000ft so it is limited to be used at 5000ft. And that would give a high reliability and accuracy. It is not that the altitude radars are binary by functionality, that it either can range distance or it can't. It is just that at some point the accuracy suffers too much and then it is not possible get the ranging each time, when the distance (altitude) gets longer. So sure it can be said "RADALT won't operate above 5000ft" as it is the last height system uses and then it switches to barometric altitude, but it keeps continually ranging with radar if the terrain happen to come at range below 5000ft. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
Recommended Posts