70
edits
Bugs: Difference between revisions
Jump to navigation
Jump to search
phantom DME
John Denker (talk | contribs) (repaired formatting + started "fixed bugs" section) |
John Denker (talk | contribs) (phantom DME) |
||
| Line 10: | Line 10: | ||
Workround: Specify the latitude as a slight offset to what you require. Eg instad of --lon=16 make it --lon=16.0001 The difference visually is next to nothing. :-) | Workround: Specify the latitude as a slight offset to what you require. Eg instad of --lon=16 make it --lon=16.0001 The difference visually is next to nothing. :-) | ||
==== ident from phantom DME ==== | |||
In the real world, some VOR stations and even some localizers | |||
have a colocated DME station ... but there are plenty that | |||
don't. | |||
The DME has its own Morse ident, with a distinctive higher pitch. | |||
In the simulator, due to a bug in the code, all stations | |||
transmit the DME Morse ident ... even stations where no | |||
DME is present. | |||
The code in navradio.cxx finds the nearest VOR or LOC on the | |||
frequency, and checks to see if it is in range. It also asks | |||
for the "nearest" DME on the frequency, but makes no attempt | |||
to check that it is in range. To say the same thing the | |||
other way, there is no attempt to check that the aircraft is | |||
within the service volume of the DME. Since there is almost always | |||
a DME /somewhere/ on the frequency, the has_dme variable will | |||
always be set true. | |||
For a demonstration of this bug, park at KAOO airport and | |||
tune up the AOO VOR (which has no DME). Or park at almost | |||
any airport and tune up the localizer (since relatively few | |||
localizers have DME). | |||
== Fixed Bugs == | == Fixed Bugs == | ||