Jump to content

Recommended Posts

Posted (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.

Screen_171201_081404.thumb.jpg.8bc86fbbd5cd9539026d522713931a92.jpg

Screen_171201_081426.thumb.jpg.c00c009de0e95eb5270b424c3e3d2a04.jpg

Screen_171201_081502.thumb.jpg.7417305c99c5888ec1587fbc70dc492b.jpg

Screen_171201_081534.thumb.jpg.d69510e338d46c38ce797a8526125b88.jpg

Edited by acdelta57
images added
  • Like 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''

  • 7 months later...
Posted (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 by TonyZ
Posted (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 ?).

 

attachment.php?attachmentid=189864&stc=1&d=1531505595

1279632451_AV8BAWLSKobuletiRWY072_5_2_19273Screen_180713_184405.thumb.jpg.77fa75f6431f67dbf2b7c084947dafbb.jpg

Edited 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

Posted

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.

 

picture.php?albumid=1563&pictureid=9999

(1AF) "THUD" | 55th FS



Joint Task Force 1 | Discord

Posted (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.

 

attachment.php?attachmentid=190011&stc=1&d=1531673212

 

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).

1831066608_AV8BAWLSuser134960_pic9999_1531658560.thumb.jpg.c4aa24ca246121e01a559602ecffd641.jpg

Edited 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

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...