CrossWiseRanger Posted April 26, 2018 Posted April 26, 2018 Rift flying in UH-1h, version 2.5. Modified a mission to add wind to see how the wind effects tracking with ILS and NDB's. First noticed that the ILS was not working. Then that the NDB's were also not operational. The only setting changed between a functional and non-functional ILS and NDB is the setting for wind speed @ 33ft. Any setting not 0 gives inop nav. What is not working specifically. The UH-1h CDI vertical and horizontal pointers do not move. Shows flags for GS and LOC. Morse code is heard. On A-10C, the ADI Course Warning and Glide Slope Warning red flags are showing. Bank Steering Bar not moving and Pitch Steering Bar not visible. No morse code is heard. Tested on Kutasi and Senaki airports. Tested with an old mission and a newly created one. Also tested with both the UH-1h and A-10C. Problem replicated across all scenarios. Bug? VR with Oculus Rift preferred flying method.
Frederf Posted April 26, 2018 Posted April 26, 2018 Yeah. Runway selection by ATC and landing radio aids are switching by different logic. Also radio landing aids are switching at all which in a lot of cases would be unnecessary and not done in reality. Affects all runway-associated radio landing aids. Note that you may get "back course" signal on those two airports as they have shared frequency ILS for each direction. You should get localizer reverse-sensing and glideslope won't be functioning for the opposite direction. Try set a strong headwind 6m/s or more and you should see ATC and radio equipment both configure for the same runway. https://forums.eagle.ru/showthread.php?t=206555
Recommended Posts