CaptJackG Posted October 24, 2023 Posted October 24, 2023 (edited) While sitting on the ground in Hawkinge with Qnh of 1013 hPa the altimeter reads 0'. Should be 524' for field elevation. Setting the Qfe of 994 hPa to read 0' at the field the altimeter reads 554'. Going to have a good trounce with my crew chief. Cheerio. Edited October 24, 2023 by CaptJackG
aphill Posted October 26, 2023 Posted October 26, 2023 What? No one has noticed this except CaptJack??
Art-J Posted October 26, 2023 Posted October 26, 2023 (edited) Contrary to what one might think about "seriousness" of DCS, I'd bet there are many more players who just fire up their engines and fly to do pew-pew and dakka-dakka ;). We noticed 2.9 boost gauge bug quicker because that one is actually much more important. But yeah, I can confirm the kollsman window bug. I remember reading that Channel map used to have some weird ambient pressure issues (not sure if it stll does), so I tried good ole Caucasus. Screens below show readings taken at Vaziani. Pressure set to QFE (~ 974 hPa) yields approximate field elevation (~1540 ft) instead of zero. Edited October 26, 2023 by Art-J i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
grafspee Posted October 26, 2023 Posted October 26, 2023 @Art-J Since you mentioned boost gauge bug, i am aware that @NineLine said that bug is reported and he closed the topic but i am not sure what does that mean, does it mean that they fix this by reverting to old boost gage range or they redone needle logic for new 16lbs scale ? System specs: I7 14700KF, Gigabyte Z790 Aorus Elite, 64GB DDR4 3600MHz, Gigabyte RTX 4090,Win 11, 48" OLED LG TV + 42" LG LED monitor
Art-J Posted October 26, 2023 Posted October 26, 2023 ^ Yeah, i saw it. My guess is a good as yours, unfortunately, but it's good to see it reported quickly at least. Since more knowledgeable guys say the 2.9 gauge face is for older gauge model which should not be there on Merlin-66 plane in the first place, I hope they'll give the gfx artist a task of drawing a new texture with old scale. That would do the trick. Texture job should be easier and faster than coding job (for needle movement) anyway, but that's just my speculation. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Skewgear Posted October 27, 2023 Posted October 27, 2023 Does this 13 hours ago, Art-J said: Contrary to what one might think about "seriousness" of DCS, I'd bet there are many more players who just fire up their engines and fly to do pew-pew and dakka-dakka ;). We noticed 2.9 boost gauge bug quicker because that one is actually much more important. But yeah, I can confirm the kollsman window bug. I remember reading that Channel map used to have some weird ambient pressure issues (not sure if it stll does), so I tried good ole Caucasus. Screens below show readings taken at Vaziani. Pressure set to QFE (~ 974 hPa) yields approximate field elevation (~1540 ft) instead of zero. So what's labelled as QFE in the briefing is actually QNH? Or is this just a Spitfire-ism? We've known for ages that on Normandy 1 and 2 the altimeter value on spawn seems as if it's wound all the way to one extreme of the scale. I assumed that was intended behaviour to simulate setting up the cockpit for the first flight of the day, but in light of this perhaps that's not true. DCS WWII player. I run the mission design team behind 4YA WWII, the most popular DCS World War 2 server. https://www.ProjectOverlord.co.uk - for 4YA WW2 mission stats, mission information, historical research blogs and more.
Art-J Posted October 27, 2023 Posted October 27, 2023 (edited) Nah, the QNH vs QFE is currently Spitfire-only issue. Quite possibly introduced with 2.9, but I haven't flown the plane in 2.8 all that often to recall how its altimeter worked then. The altimeters in other Allied planes work correctly and according to briefing window, haven't tested German ones. The instrument being wound to extreme is a separate thing, a feature rather than an issue from my point of view. It's always been the case across all maps really, but that's more of a "DCS'ism" in general, with some warbirds always spawning calibrated to QFE and the other always calibrated to God knows what. Edited October 27, 2023 by Art-J i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Screamadelica Posted October 27, 2023 Posted October 27, 2023 Always been something a bit strange with the kollsman window readings and altimeter value. Used to think I was setting it incorrectly but soon realised the settings were not matching up as they should. Guess it's on the list of things to do, but not urgent. When in doubt a large, violent crashing sound will tell you when you've reached QFE.
iFoxRomeo Posted October 27, 2023 Posted October 27, 2023 Good luck with this bug. I reported an altimeter setting bug for the K4 about 8 years ago. After only 6 years it was acknowledged, but... I updated from 2.8.8 to 2.9 today. But before that I made a few screenshots. Altimeter setting on the Spitfire was ok on 2.8.8(Caucasus, QNH 2992/1013). Interestingly the scaling direction also changed with 2.9. 2.8.8 QNH 1013 Caucasus 74ft Elevation, check scale and scale direction 1000 -> 1020 2.9(latest) QNH 1013 Caucasus 74ft elev., altimeter set to 74ft results in 992 setting, check scale direction now 1000 -> 980 2.9(latest) QNH 1013 Caucasus 74ft elev., altimeter set to 1013hPa ->approx. 550ft below elevation Fox Spoiler PC Specs: Ryzen 9 5900X, 3080ti, 64GB RAM, Oculus Quest 3
Art-J Posted October 27, 2023 Posted October 27, 2023 (edited) Uh, so the kollsman scale is different and reversed in 2.9 compared to 2.8 then. Nice catch and quite important one! Could it be the case of yet another different version instrument modelled (or rather textured), just like in case of boost gauge? So maybe in a similar fasion, the coded window rotation logic is OK, but it just doesn't match the new (reversed) texture? Edited October 27, 2023 by Art-J 1 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
Art-J Posted October 29, 2023 Posted October 29, 2023 (edited) Upon taking a second look It seems to be just a texture problem indeed, similar to boost gauge one. @NineLine since the latter has been reported, could you please highlight this new issue as well? Maybe the gfx artist will fix both together while he's at it. The instrument animaton logic is the same as it was in 2.8, but kollsman scale texture (apart from being divided somewhat different) is just reversed in 2.9, which results in incorrect operation of the instrument: a) In 2.8 rotating the knob CW rotated kollsman scale CW - towards higher reference pressures (scale increased to the right), which corresponded to CW rotation of altimeter needles as expected (higher airfield elevation above MSL). b) In 2.9 rotating the knob CW also rotates kollsman scale CW - but towards lower reference pressures (scale increases to the left now), which combined with CW rotation of altimeter needles causes incorrect, reversed operation of the instrument (lowering reference pressure cannot cause higher airfiel elevation above MSL). Edited October 29, 2023 by Art-J 3 i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
ED Team NineLine Posted November 21, 2023 ED Team Posted November 21, 2023 On 10/29/2023 at 9:12 AM, Art-J said: Upon taking a second look It seems to be just a texture problem indeed, similar to boost gauge one. @NineLine since the latter has been reported, could you please highlight this new issue as well? Maybe the gfx artist will fix both together while he's at it. The instrument animaton logic is the same as it was in 2.8, but kollsman scale texture (apart from being divided somewhat different) is just reversed in 2.9, which results in incorrect operation of the instrument: a) In 2.8 rotating the knob CW rotated kollsman scale CW - towards higher reference pressures (scale increased to the right), which corresponded to CW rotation of altimeter needles as expected (higher airfield elevation above MSL). b) In 2.9 rotating the knob CW also rotates kollsman scale CW - but towards lower reference pressures (scale increases to the left now), which combined with CW rotation of altimeter needles causes incorrect, reversed operation of the instrument (lowering reference pressure cannot cause higher airfiel elevation above MSL). Sorry I missed this will take a look at it today. Thanks. Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Art-J Posted November 21, 2023 Posted November 21, 2023 6 minutes ago, NineLine said: Sorry I missed this will take a look at it today. Thanks. Oh, It's been fixed in the latest update together with boost gauge. i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.
ED Team NineLine Posted November 21, 2023 ED Team Posted November 21, 2023 Just now, Art-J said: Oh, It's been fixed in the latest update together with boost gauge. Oh even better, thanks! Forum Rules • My YouTube • My Discord - NineLine#0440• **How to Report a Bug**
Recommended Posts