Bug & Feature on beta 2

[RudiZhang]

BUGs: for TL, i don't know why but it shows together

I don't have any option for arrival

It read as "runway one", but for non-FAA it should be runway zero one

no [WIND] and CAVOK text display for non-FAA format, but read correctly

no text ATIS showing when using external ATIS

for external ATIS, ATIS letter read as "a b c", i don't know why

Feature: Add Transition Altitude maybe?

make [TL] logic like if no value on [TL] then don't show [TL]? so people can make a commen temple

set ATIS code before connect?

cloud shows in metric on text?

airport condition/NOTAM fetch from main pannel?

[mythicfci]

I can confirm I'm having the same bug with vATIS not adding a space between "Transition level" and the number.

I previously uploaded my vATIS profile in #42 if it is helpful in diagnosing this issue.

[justinshannon]

The next version should fix the following issues (not yet released):

• Add space after "transition level"
• Read leading zero on numbers (non-FAA format)
• Fix missing WIND and CAVOK
• Cloud height converted to metric (if enabled)

The ATIS code cannot be set before connecting. This would require lots of changes to the current codebase.

The issue with vATIS not reading the ATIS code correctly from an external ATIS generator is not an easy fix. vATIS just reads what the external ATIS generator (e.g. UniATIS) produces. vATIS doesn't know the ATIS template format, so it's difficult to parse and replace the ATIS code with the correct phonetic.

I am going to close this issue, since it is so old. Once the new vATIS version is released, feel free to open a new Github issue if you are still experiencing any formatting or functionality issues.