Fixed and tested - will be in FSM v0.94 later this week
Addition RA “R” now in production 0.94
very nice, David.
will test it tonight!
Thanks! 
tested yesterday, all good with an German ATC, but here with a WU response.
next test, norwegian ATC (not sure why their response code would differ if most of them use the same ATC software? ex. Euroscope)
1 Like
another small issue with ATIS, THIS ATIS IS NOT AVAILABLE, but only occurs when published like this: (A_ATIS & D_ATIS)
I believe that’s a limitation of the Hoppie network rather than the app.
seems that with a suffix with _A or _D would do the trick. I think that is what Fenix do with their EFB: looking at type=inforeq&packet=vatatis+ICAO, if not found, check if ICAO_A and ICAO_D is available/exists, then response is ok.
and
thanks, something to think about, but not a priority as I am wondering whether it should be sorted out in the ACARS network not in the client? You can always enter ICAO_D or ICAO_A in FSM
in VSR we load all the stations for each airport online, so if you have 2 ATIS they are loaded automatically, been like that since 2022.
thanks, I didn’t know that 