by noisy » 12 May 2012, 11:15
Hi,
DCA996 wrote:My guess is this is because your aircraft's current location is not the original locatoin where the fstower is active, ie. the last world/airport that you selected or was associated with a saved flight you may have selected.
No, it has nothing to do with default FS tower location.
I just checked it, and it's a bug in the latitude/longitude conversion routines. It occurs only for coordinates between 0 and 1 degrees west or south (sign gets lost in the deg/min and deg/min/sec formats as the degrees field is zero).
I fixed it, until the next release you can use this workaround:
Switch lat/lon format to degrees only and change longitude from east back to west (or north to south for latitude).
Hi,
[quote="DCA996"]My guess is this is because your aircraft's current location is not the original locatoin where the fstower is active, ie. the last world/airport that you selected or was associated with a saved flight you may have selected.[/quote]
No, it has nothing to do with default FS tower location.
I just checked it, and it's a bug in the latitude/longitude conversion routines. It occurs only for coordinates between 0 and 1 degrees west or south (sign gets lost in the deg/min and deg/min/sec formats as the degrees field is zero).
I fixed it, until the next release you can use this workaround:
Switch lat/lon format to degrees only and change longitude from east back to west (or north to south for latitude).