Rhayvn Posted December 2, 2022 Posted December 2, 2022 Localizer works fine, but the glideslope is inactive until you cross the runway threshold.
Raz_Specter Posted December 16, 2022 Posted December 16, 2022 thanks will check Custom built W10 Pro 64Bit, Intel Core i9 9900k, Asus ROG Maximus Code XI Z390, 64GB DDR4 3200 RGB, Samsung 1TB NVme M.2 Drive, Gigabyte AORUS 2080TI, 40" Iiyama Display. Wacom Cintiq Pro 24, HOTAS Virpil T50 Stick / FA-18C TM Stick and Virpil T50 Throttle, MFG Crosswind Graphite Pedals. HP Reverb SPECTER [sIGPIC][/sIGPIC] Lead Terrain Developer / Texture Artist
JG14_Smil Posted December 30, 2022 Posted December 30, 2022 Allow me... "direction = 161.568576;" it should be: "direction = 75.800005;" You seem to offset ILS Localizer's 2 degrees to match your approach plates, which is just wrong. Based on other DCS maps, Approach plates should give magnetic headings, not true headings, and if your Approach plates are correct, then every one of your field runways if off by 2 degrees. You can prove this with the F10 map and ruler feature, which give magnetic/true heading readouts. ILS Localizers are supposed to be lined up with true runway heading (as seen in Mission Editor).
Recommended Posts