danickinator

> Please let me know if you are encountering any errors with ES5 code that unexpectedly becomes ES6 code when the language target is set to `es5`. @evanw the issue...

One of the things that makes NZZO_FSS fairly unusual is that it spans both sides of the antimeridian - the two transceivers associated with it are located in Auckland, New...

Final bit of elaboration: The position we were trying to tune NZZO_FSS was overhead OMKIN which is ~630nm from the Auckland tranceivers (ids 0 and 2 in the json above)...

I can confirm the issue is still present in 0.14.142. I'm currently taking part in Cross the Ditch 26 and departing Auckland for Melbourne I can see Brisbane Radio but...

I've just logged back on and can confirm that I can tune NZZO_FSS while sitting at Auckland. This is using the same build that did not work during my flight...

Re-ran Swift again with the log going to the console and encountered the same thing: several minutes of tuning NZZO_FSS without issue, with log messages like this: ``` swift.audio|swift.vatsim|BlackCore::Afv::Clients::CAfvClient|BlackMisc::CContinuousWorker|BlackMisc::CWorkerBase: Aliasing...

> A few more questions: > > * @danickinator: Do you still have the entire log available. Does it contain a log line like "ATC NZZO_FSS timed out after XXX...

Found the log (which lives in `~/.local/share/org.swift-project` under linux). There's no timeout messages concerning NZZO_FSS. It just goes from the Aliasing message to the Station not found message: ``` 19:39:35...