November 28, 201312 yr Hi Yorkie! Long time no speak/write. Just a quick one: I set FSX settings to "Metric - Metres/Millbars" and Latitude & Longitude "Southern - Eastern" for Australia. I've noticed that the Metric setting (at least for me) plays around with the FO and in particular his callout for transition. eg: I've set the transition altitudes correctly (takeoff & descent forecast ) within the CDU/FMC (ie 10,000). The FO doesn't call Transition Altitude until around 32,000ft. I've tested this 3 times now with the same result. I've also uninstalled & reinstalled NGX & Emergency. If I switch FSX back to "US System" FO callouts are AOK. Any idea on what I can do to resolve this? Thanks mate! Steve PS: I just got back into the NGX after a long foray with the 777. Can't wait for your 777 FO! Ryzen 9 9950X3D @ 5.6Ghz + Corsair Nautilus Water Cooler - 64Gb Corsair Vengeance DDR5 6000Mhz - ASUS RTX 5070Ti 16Gb - Samsung G9 Odyssey 49 inch 5120x1440 Monitor - ASUS Crosshair X870E - Win 11 Pro - MSFS 2020 - 3 x NVMe M.2 1Tb - Fractal North XL Case "Tertia Optio, Latebra Factum" Steve Summers
November 29, 201312 yr Commercial Member I've noticed that the Metric setting (at least for me) That's the problem. You need to set it to Feet (US style). Only Russians and Chinese use "meters" for altitude. Everyone else uses feet. Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
November 29, 201312 yr Author Damn......always the simplest thing that is overlooked! I'll give it a whirl! Thx mate. Ryzen 9 9950X3D @ 5.6Ghz + Corsair Nautilus Water Cooler - 64Gb Corsair Vengeance DDR5 6000Mhz - ASUS RTX 5070Ti 16Gb - Samsung G9 Odyssey 49 inch 5120x1440 Monitor - ASUS Crosshair X870E - Win 11 Pro - MSFS 2020 - 3 x NVMe M.2 1Tb - Fractal North XL Case "Tertia Optio, Latebra Factum" Steve Summers
Create an account or sign in to comment