Knugge Posted February 21 Posted February 21 Since the last patch (2.9.13.6818 MT), the auto-generated kneeboard no longer displays navigation points (B-points). Only the takeoff and landing points appear on the kneeboard.
Typhonus2 Posted March 28 Posted March 28 So, can we expect to see this fixed ASAP? Since the target QFE is listed on the kneepad, and not readily available elsewhere to my knowledge, it renders the module largely unplayable. Most of the weapons require QFE to properly target ground objects. Am I missing something? 1
Minsky Posted March 28 Posted March 28 7 minutes ago, Typhonus2 said: So, can we expect to see this fixed ASAP? Since the target QFE is listed on the kneepad, and not readily available elsewhere to my knowledge, it renders the module largely unplayable. Most of the weapons require QFE to properly target ground objects. Am I missing something? Can't you just calculate it using briefing's QNH and waypoint's altitude? Sure it's not as easy as dialing in precalculated numbers, but saying this makes the module unplayable is a bit of an exaggeration. 1 Dima | My DCS uploads
Typhonus2 Posted March 28 Posted March 28 (edited) To be honest, I'm unfamiliar with this technique. The number has always been provided right on the flight plan in my kneeboard, which I assume the developers thought was a realistic way for the pilot to get that information. I know that I can tell the waypoint's altitude from the map. How do I get the QNH, as many missions seemingly don't have missions. Also, is QNH universal in the whole map? Would it be the same everywhere? Or do I need to know QNH over the target - which, again, how would I get this? Edited March 28 by Typhonus2
Minsky Posted March 28 Posted March 28 (edited) 2 hours ago, Typhonus2 said: To be honest, I'm unfamiliar with this technique. The number has always been provided right on the flight plan in my kneeboard, which I assume the developers thought was a realistic way for the pilot to get that information. I know that I can tell the waypoint's altitude from the map. How do I get the QNH, as many missions seemingly don't have missions. Also, is QNH universal in the whole map? Would it be the same everywhere? Or do I need to know QNH over the target - which, again, how would I get this? The QNH is always displayed in the mission briefing and is the same for the whole map (at least with the static weather presets). Here's the basic formula to calculate the QFE. It doesn't account for temperature, but should be good enough for us: QNH – (target elevation in feet / 30) So, if QNH is 1020 mbar and target elevation is 800 feet, QFE at its location will be 1020 – (800 / 30 = 26.6) = 993.4 mbar. I would strongly recommend reading this (part 11, section 1.7 - QFE). Edited March 28 by Minsky 1 Dima | My DCS uploads
Typhonus2 Posted March 28 Posted March 28 I read that section, and will give this a try. But I'll note that the manual piece to which you referred me, in its third recommended method, seems to detail a much more complex version of this math than you note here. Still, it's worth a shot. Thanks! 1
Zabuzard Posted March 28 Posted March 28 The issue had been semi-fixed a week ago or so, for the next update.There is more to fix unfortunately, but it should be usable again soon. 2 1
Typhonus2 Posted March 28 Posted March 28 Thanks! I'm spending a lot of time with the Viggen in the newish Kola map and this will make it easier. 1
itsthatguy Posted March 29 Posted March 29 16 hours ago, Zabuzard said: The issue had been semi-fixed a week ago or so, for the next update. There is more to fix unfortunately, but it should be usable again soon. There's been a hotfix released since you say this problem was semi-fixed, why wasn't it included? Are 3rd party devs not allowed to push changes to a hotfix version?
Zabuzard Posted March 29 Posted March 29 There's been a hotfix released since you say this problem was semi-fixed, why wasn't it included? Are 3rd party devs not allowed to push changes to a hotfix version?"Not allowed" is the wrong term, but yeah. Our stuff will be included in the regular patch again, when there was also enough time for all the testing steps that take place behind the curtain to ensure you have a smooth experience and not constant crashes 2
Recommended Posts