Closed ml0130 closed 1 year ago
You need to disable "Format ATIS using FAA format" and "Use "decimal" terminology in spoken text"
EDIT: Misread your issue, but now I'm on beta 2 and it seems that it reads the frequency number by number.
@amosngSP the problem is that since this is for an FAA Facility the formatting for FAA ATIS' needs to be keepded on.
This should be fixed in beta 3; please test and let me know.
@justinshannon can confirm that #48 is fix. but it does seem that the frequency issue could use some tweaking when they end in a 0. Ref the sound file
For some reason, if there is a NOTAM with a frequency that ends in a .0 and no other trailing number it reads it as if it was a normal number. For example for Area 3 of SCT, I run a NOTAM
CLNC IS CLSD FOR CLNC CTC SO-CAL APP 127.0
but for some reason instead of it as one-two seven-point zero. It reads it as One Henered Twenty Seven.Is this a known problem?