Once again, thanks for the great product and support! I have a question that I think has been asked in the forum but I have not completely understood the responses:When I dial in an ATIS/AWOS frequency the report never seems to exactly match the Actual weather by Active Sky as reported by Sky Watch for the same facility. The times, clouds, ceilings and temps are all just a little (or a lot) different. I always use system time, I don't have TAF processing marked and I don't have FS weather download checked on. So where is FS getting it's data for ATIS/AWOS? It would be really realistic if ATIS/AWOS reports really matched up with what AS was producing! Then we could practice looking up and using ATIS/AWOS frequencies instead of using the convenient but not so realistic Sky Watch.Thanks again for a great product and support!DD

Hi DD,In your post I am not sure what you mean by Sky Watch. Is that FlightWatch, built into AS where you tune into 122.0, or something else?? I re-read your post and it looks like that is what you mean.With your default flight there is a set of weather that is also saved. Everytime you start FS that weather is initially loaded and the FS ATIS locks on to this weather. The easiest way to clear this out is by using the clear weather button in FSUIPC. Then, if you refresh AS the FS ATIS should report the correct conditions. And sometimes it just takes some time for things to cycle.Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

I did mean FlightWatch - oops. Thanks. I'll give this a try!DD

Jim:After clearing the weather within FSUIPC and refreshing, things seemed to align between FlightWatch and local ATIS/AWOS reports. However.... The alignment doesn't seem to be consistent. I just attempted a flight from KJQF to KAVL and the FlightWatch and AWOS times never corresponded and neither did the weather conditions - close but never the same. I've been comparing FlightWatch, FS9 AWOS, and NOAA Metar data (via FS Browser - a great way to test!) and I can't find a pattern. There doesn't seem to be a tight link. What am I missing? It seems FS9 ought to be using AS data.I use system time, don't use TAF processing, and do use FSUIPC wind smoothing.FYI, I'm using the 140 build and the unregistered FSUIPC that came with it.Hope this isn't too nit-picky. Otherwise this program is awesome!DD

I'm experiencing exactly the same thing with build 140 as well. Flightwatch in AS2004 is really not consistant with the destination METAR being displayed in the AS2004 interface window.

Hi DD,Thanks for the update. Without some details it is hard for me to say too much. But here are some general ideas:I am not sure what you are trying to match up. If it is Internet weather reports and AS, you can stop, because the data sources are different.If it is FS and AS then you need to know that the closest station reported in AS has a exact range of two miles. That means you need to be within two miles of that station for weather to match up exactly. After that two miles, many stations are used. We report the closest station to give you an idea of the weather, not the exact weather at your plane's location.If it is AS and the ATIS system in FS then certain data is handled differently such as wind direction.If it is between AS and FlightWatch, there are certain METAR codes and combinations that FlightWatch cannot handle. We have included as many common codes as possible, but new stuff sometimes shows up.In the real world these same things happen because none of these things are designed to give a pilot EXACT conditions minute by minute, mile by mile. If you think that something is really off the mark, please let us know the details and we will be happy to look into it!Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

Jim:Thanks for your persistence!Let me try to clarify:I would like to be able to fly along as in real life and occasionally check AWOS reports at nearby stations using the COM radio and have accurate information that reflects what AS is doing in the visible sky around me. (This could be checked by Alt-tabbing out of FS and viewing the nearest station as reported in AS). I realize your data source is not exactly NOAA (though it is often exactly the same - which is great!) I realize that AWOS and AS may have some magnetic vs. true heading wind differences and visibility reporting variability but how can I explain the following that I just experienced after loading my default flight, clearing FSUIPC weather and then loading AS:AS Weather as viewed in AS screen itself: KJQF 242051Z VRB05KT 10SM FEW050 BKN200 28/16 A3009 RMK AO2 SLP182 T02830156 56011 RMK AUTOGEN AS2004.5AWOS/ATIS: (133.67): KJQF 2155Z 07505KT >20M FEW050 28/16 A3009Why are the times different? I use system time. Where does ATIS get an actual wind direction when AS is sending VRB to the program? Does FS AWOS/ATIS only report 1 cloud layer? Thanks for all your help. I'm just trying to learn some real world aviation weather by understanding your excellent program better!Thanks,DD

Hi DD,I didn't have all the answers so I did a little reading before I posted this!Why are the times different? AWOS updates every minute, while most of the time METARs are updated near the top of each hour. Then, there is about a 15-20 minute delay before the AS data server has pulled in all its data. In your example, the 2051Z METAR would have been the very latest. So nothing is wrong there. At about 2215Z(give or take a few minutes) the 2155Z METAR would have been ready to display.I am not sure how the FS ATIS would voice a VRB wind direction. If using FlightWatch it would have reported "variable at 5 knots".Again, I am not sure how the FS ATIS reports multiple cloud layers. I think it just recognizes the lowest layer. I always use the FlightWatch system. I know it's not perfect, but it will voice the data from AS, so I don't worry too much about its accuracy.I have learned a little bit myself tonight in reaserching your questions. If you keep throwing me specific examples, I'll keep trying to help!Hope this helps,JimActiveSky Supporthttp://www.hifisim.com/images/as2004proudsupporter.jpg

Jim:The time thing makes sense. I will continue to look at examples and send them your way if they don't make sense.Thanks!DD

Hi Dianne, All,This problem has been identified and fixed, B141 is pending. Thanks for your feedback on this!

Hi,In your example, everything is correct. FS always reports the "current wind" which when VRB will change. The >20SM is normal, remember METARS only report max 10SM vis. We use moisture calculations to extend the vis realistically past 10 miles. FS ATIS reports up to 20SM. FS ATIS does not report clouds above 12,000ftAGL.As to the mis-matches after flying a while, I have identified and fixed that problem (local suppression was interferring with the FW data), and B141 is pending public beta.Thanks!

Damian:Thanks for the clarification. I look forward to trying out B142. Keep up the great work!DD

Damian:I'm trying out B142 now.I tried a flight from KJQF to KAVL tonight. Still having some issues of AWOS/ATIS not matching AS info (as seen in the AS screen by alt-tabbing out of FS to check). I did change my FS time back several hours to allow for cloud watching but left AS at system time. I don't think that affects the info other than the time readout. AS: KIPJ 270054Z 00000KT 9SM CLR 22/19 A3017ATIS (119.67): KIPJ 2308Z 07103KT 9SM CLG 146 BKN 22/19 A3017AS: KAVL 270054Z 00000KT 5SM -RA BR SCT030 BKN042 OVC049 21/19 A3024 RMK AO2 RAB2359 SLP220 P0001 T02110194ATIS (120.2): KAVL 2327Z 23303KT 4SM LR SCT030 BKN 042 21/19 3024Thanks for all your help! DD

Hi,In the first example, KIPJ, everything is correct. Looks like you have a random cirrus layer being created as per AS options. If you don't want additional upper cirrus layers created, uncheck the "upper layer generation" option.Also, for winds, we do not ever write 0 wind speed as this will cause problems with FS9 interpolation and data checks - not so much an issue with DWC but still a possibility and very much an issue when DWC is off. Thus any zero wind is changed to 3 kts. The direction is computed from upper wind info.In KAVL, I see a 1SM difference in vis. This is common and probably due to FS reducing vis slightly per the light rain. Remember, ATIS reports in FS do not report above the first cloud ceiling (BKN042 in this case) which is why the OVC049 is not mentioned. Newer real life wx equipment can see past ceiling layers (BKN or OVC) but FS is still using this older limitation (which IS accurate per older wx equipment - existing at many airports).Hope that helps!

After reading this thread I have a simple newbie question:When I'm coming to land which source of information about wind should I use to ensure landing with correct wind information (without tailwind) about ACTUAL conditions simulated in FS2004:a) Fligt Watch for destination airport:( ATIS/AWOSc) data in AS2004 main windowAnother problem which bothers me is landing on the same runway in the same direction as AI traffic (as GA pilot I mainly use uncontrolled fields). Which source of information should I use to integrate well with the traffic? Yesterday I used information from FlightWatch (wind about 4knots) and ended landing on runway 19 where all other planes were using runway 1 (information from AWOS was not consistent with FligtWatch I used).