From: James T. <zak...@ma...> - 2009-09-08 17:48:07
|
This: > Just want to ask developers: is it possible to make ILS/LOC > establishing radius more realistic? > > What we have now in FG? You can establish ILS/LOC anywere you are if > you are in n-kilometers over airport. In real life ATC asks pilots: > "Report localizer established" because in real life you can > establish it only when you are on base/final. and this: On 8 Sep 2009, at 17:55, Atadjanov Daniyar wrote: > Is it possible to fix another bug in navradio (?) system? If runway > or the region has two (or more) NDBs with same frequency, then FG > shows only one of them _everytime_. In real life (as far as i know) > NDBs of working runway are turned on and other NDBs with same freqs > are turned off. In MSFS: ADF is showing the direction to the nearest > NDB with selected frequency (the easiest way i think). Both come under the category of 'problems with the nav radio code'. The second in particular I hope to work on 'soon' - I don't know nearly enough about modelling radio reception to improve the code (or make judgements about its quality) to address the first issue. You may notice I've been careful in my emails to state the areas I'm working on, precisely because there's many overlapping problems. The GS needle indications are wrong in the aircraft - no amount of improvements or advanced modelling in the navradio code will matter, if the panels aren't handling the output deflection sanely. Similarly, I've been cleaning up the code so that changes to the behaviour are hopefully cleaner and easier in the future. BTW, for NDBs, FlightGear *should* be picking the closest NDB with the matching frequency - exactly as MSFS. If that's not what you're seeing, that's a bug, and likely my fault. Please let me know a suitable test location and NDB frequencies / idents to reproduce the problem, and I'll take a look. Regards, James |