Dave317 Posted February 5, 2017 Posted February 5, 2017 If I take off from an airbase i set the altimeter to 0. After flying around then calling inbound to the same airbase the atc gives me the QFE but it is completely wrong. Is this a dcs problem or am I reading it wrong?
renhanxue Posted February 5, 2017 Posted February 5, 2017 Apologies if I'm asking a really obvious question, but what unit is the ATC using? The Viggen wants millibars (or hectopascals, same thing), which is not the same as the US inches or the Russian millimeters of mercury.
grunf Posted February 5, 2017 Posted February 5, 2017 ATC gives you QFE in inHg. Did you properly convert it to mbar?
Dave317 Posted February 5, 2017 Author Posted February 5, 2017 Ah I thought QFE was QFE. I didn't realise there was different measurements.
grunf Posted February 5, 2017 Posted February 5, 2017 Here's an inHg to mbar conversion table I made for myself, which I keep in the kneeboard. :) 1
609_Relentov Posted February 5, 2017 Posted February 5, 2017 (edited) Cool, thanks grunf! Do any other DCS modules require QNF entered in mbar? If not, this sort of table would be a great addition to the Viggen manual or kneeboard, since altitude settings are so important for air-to-ground ordinance usage (and by default, DCS does not provide the proper unit of measure in the ATC call-backs). Relent Edited February 5, 2017 by 609_Relentov
grunf Posted February 5, 2017 Posted February 5, 2017 (edited) Cool, thanks grunf! Do any other DCS modules require QNF entered in mbar? If not, this sort of table would be a great addition to the Viggen manual, since altitude settings are so important for air-to-ground ordinance usage (and by default, DCS does not provide the proper unit of measure in the ATC call-backs). Relent I know M2000 uses mbar, that's why I created the table :), Hawk, maybe Gazelle too, but I'm not sure. Most if not all Russian planes use mmHg. Edited February 5, 2017 by grunf fogot the hawk :)
Dave317 Posted February 5, 2017 Author Posted February 5, 2017 Thank grunf. Leatherneck is it possible to add this to the knee board?
unipus Posted February 6, 2017 Posted February 6, 2017 Cool, thanks grunf! Do any other DCS modules require QNF entered in mbar? If not, this sort of table would be a great addition to the Viggen manual or kneeboard, since altitude settings are so important for air-to-ground ordinance usage (and by default, DCS does not provide the proper unit of measure in the ATC call-backs). Relent Well, the kneeboard DOES contain your flightplan data, including QFE for each waypoint. So for targeting purposes this is pretty much already taken care of properly in the kneeboard, no?
609_Relentov Posted February 6, 2017 Posted February 6, 2017 Well, the kneeboard DOES contain your flightplan data, including QFE for each waypoint. So for targeting purposes this is pretty much already taken care of properly in the kneeboard, no? Hmm, you're right, thanks unipus. I didn't look at the waypoint chart close enough to see that it had the QFE figures there, nice addition to the dynamic kneeboards.
609_Relentov Posted February 6, 2017 Posted February 6, 2017 (edited) One more comment/question on the issue of establishing the QFE at a given waypoint. What if waypoints are not provided (beyond the take off airfield), and we have to add them through lola coordinates via the CK37 during the mission? These waypoints of course are not included in the generated kneeboard, and I don't recall seeing any QFE info on the F10 view. Not sure where we would get the QFE info for these, or do we just use the airfield QFE and do ballpark adjustments based on the altitude difference between the take off airfield and the target waypoint... I would imagine this could affect the accuracy (re: dispersion altitude) of the BK90. Edited February 6, 2017 by 609_Relentov
Dave317 Posted February 6, 2017 Author Posted February 6, 2017 Well, the kneeboard DOES contain your flightplan data, including QFE for each waypoint. So for targeting purposes this is pretty much already taken care of properly in the kneeboard, no?[/quote It would be nice for mp though.
Fishbreath Posted February 7, 2017 Posted February 7, 2017 I would imagine this could affect the accuracy (re: dispersion altitude) of the BK90. The BK90 has an internal radar altimeter. It'll affect dumb munitions, but not the smart ones. Black Shark, Harrier, and Hornet pilot Many Words - Serial Fiction | Ka-50 Employment Guide | Ka-50 Avionics Cheat Sheet | Multiplayer Shooting Range Mission
Express0083 Posted February 7, 2017 Posted February 7, 2017 Thank you so much Windows 10 64bit MSI Z170A MB EVGA 1080 FTW Intel i7 6700k 4.0 GHz (SKylake) 16GB RAM Warthog Hotas and Rudder Oculus Rift
609_Relentov Posted February 7, 2017 Posted February 7, 2017 (edited) The BK90 has an internal radar altimeter. It'll affect dumb munitions, but not the smart ones. Good to know, thanks. I guess I missed that in the manual :). Now if I could only get the BK90's to disperse the sub-munitions. They fly right over the target waypoint and keep on going, and then just lose their kinetic energy and fly into the ground. I fire them when the horizontal line has shrunk to the outer poles (I__I) on the hud, between 50-500 meters, NAV/ANF (tried both) master modes, weapon on ATTACK and they have plenty of energy to make the waypoint... can't figure out what I'm missing. Edit - I also tried entering the dispersion code for long area 921000 in mode TAKT / IN but they still did not disperse. Another edit - just realized this was after a re-arm, so it may be related to the other re-arm bugs. I'll have to create another Viggen spawn point with the BK-90's pre-loaded and see if they disperse. Final edit (lol) yeah, after creating another Viggen spawn with the BK-90's loaded, they did disperse after deploying as I saw the explosion pattern, so it's probably the re-arm bug I was seeing. Edited February 7, 2017 by 609_Relentov
RaXha Posted February 7, 2017 Posted February 7, 2017 Good to know, thanks. I guess I missed that in the manual :). Now if I could only get the BK90's to disperse the sub-munitions. They fly right over the target waypoint and keep on going, and then just lose their kinetic energy and fly into the ground. I fire them when the horizontal line has shrunk to the outer poles (I__I) on the hud, between 50-500 meters, NAV/ANF (tried both) master modes, weapon on ATTACK and they have plenty of energy to make the waypoint... can't figure out what I'm missing. Edit - I also tried entering the dispersion code for long area 921000 in mode TAKT / IN but they still did not disperse. Another edit - just realized this was after a re-arm, so it may be related to the other re-arm bugs. I'll have to create another Viggen spawn point with the BK-90's pre-loaded and see if they disperse. Final edit (lol) yeah, after creating another Viggen spawn with the BK-90's loaded, they did disperse after deploying as I saw the explosion pattern, so it's probably the re-arm bug I was seeing. This is a short in the dark but are you doing this in multiplayer or singleplayer? The Bk-90 doesn't work in multiplayer unless you are the host at the moment. :-)
david.lind Posted February 7, 2017 Posted February 7, 2017 If you use dynamic weather the pressure changes over time or? for a given location?
UVPMechan Posted February 7, 2017 Posted February 7, 2017 Here's an inHg to mbar conversion table I made for myself, which I keep in the kneeboard. :) Somehow it does not fit. Why is the conversion table for Mig-21 different?
grunf Posted February 7, 2017 Posted February 7, 2017 Somehow it does not fit. Why is the conversion table for Mig-21 different? Because the MiG-21 table converts inHg to mmHg, not to mbar.
UVPMechan Posted February 7, 2017 Posted February 7, 2017 Because the MiG-21 table converts inHg to mmHg, not to mbar. And you're right.
unipus Posted February 9, 2017 Posted February 9, 2017 No problem, stumbled on it quite accidentally myself and was very happy!
Recommended Posts