acdelta57 Posted December 1, 2017 Posted December 1, 2017 (edited) Flying a few AWLS approaches I noticed the localizer is deflecting in the opposite direction. Example Aircraft left of course, LOC needle deflected to left when it should be right and vice versa. Check screenshots Kobuletti airfield AWLS CH1 Tacan 67X The GS and LOC needles represent the approach correctly but like I said when intercepting to track the Course needle deflects opposite. Edited December 1, 2017 by acdelta57 images added 1 [sIGPIC][/sIGPIC]1000 miles of road will take you around town, a 1000 feet of runway can take you around the world...unless your in a Huey, you can go anywhere with no runway in a Huey! multiplayer name ''DustOff=3=6''
TonyZ Posted July 13, 2018 Posted July 13, 2018 (edited) I think this post needs bumping. I agree that the localizer needle in the HUD is ass backwards and appears to never have been fixed. You always fly to the line not the line to the fpm. The fpm is the plane and the line shows the direction from the fpm or waterline TO the ILS indicator. Edited July 13, 2018 by TonyZ
Ramsay Posted July 13, 2018 Posted July 13, 2018 (edited) I agree that the localizer needle in the HUD is ass backwards and appears to never have been fixed. Why do you think that, the AWLS localizer was fixed a while ago (IIRC 2.5.1 ?). Edited July 13, 2018 by Ramsay i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Thudster Posted July 15, 2018 Posted July 15, 2018 The AWLS system is still not correct in the Harrier. The Glideslope seems to work correctly, but the Localizer is still bassakwards. Should work like the picture here, you fly to the needles. Instead, it works like you're flying an ILS Backcourse. (1AF) "THUD" | 55th FS Joint Task Force 1 | Discord
Ramsay Posted July 15, 2018 Posted July 15, 2018 (edited) Should work like the picture here, you fly to the needles. The picture is what I see in game. • AV-8B left of the localizer, the HUD azimuth bar is right of the VV • AV-8B right of the localizer, the HUD azimuth bar is left of the VV In my previous screenshot composite, I was always above the glide slope and left of the runway centre line, so the HUD glide slope and azimuth bars were always below and right of the VV. Please explain what's wrong by posting a DCS 2.5.2 track or screenshot. When the beam is acquired, a vertical azimuth steering bar and a horizontal elevation steering bar are displayed (see Figure 23-10). Both bars are referenced to the velocity vector in the NAV mode and to the vertical flightpath symbol in the VSTOL mode. The azimuth bar represents aircraft azimuth angle fromthe localizer and the horizontal bar represents elevation angle fromglideslope. Full deflection of the steering bars on the HUD represents ±2° for elevation and ±6° for azimuth. Azimuth steering reference marks are provided adjacent to the velocity vector/vertical flightpath symbol when the AWLS steering mode is selected. The reference markers denote 3° and 6° steering deviation (left and right). Edited July 15, 2018 by Ramsay Confirm NAV Mode Azimuth direction is correct i9 9900K @4.8GHz, 64GB DDR4, RTX4070 12GB, 1+2TB NVMe, 6+4TB HD, 4+1TB SSD, Winwing Orion 2 F-15EX Throttle + F-16EX Stick, TPR Pedals, TIR5, Win 11 Pro x64, Odyssey G93SC 5120X1440
Thudster Posted July 15, 2018 Posted July 15, 2018 You are absolutely correct. I missed it. :thumbup: Just went back in and yup - I'm flat wrong - it's correct now. Happy to be screwed up on this one lol. (1AF) "THUD" | 55th FS Joint Task Force 1 | Discord
Recommended Posts