Problems generating accurate real world real time weather
I am having problems getting ASA to generate the correct weather. I import my flightplan into ASA, and the briefing at the bottom shows the correct current conditions. I startup FSX, allow the weather to load into the simulation (I get the "initial weather import complete!" message, that might not be exactly what it says, but that's the gist of it.), but the weather isn't what's on the briefing. The conditions are similar, but mostly what is missing are the cloud layers. I have cloud layers turned all the way to 20 in ASA. The Report tab in ASA shows the correct/same info as the Briefing tab, but the Wx Config tab shows something different. Below are the current actual conditions and the different conditions that Wx Config tab is showing:
Correct/Actual (and shown on Briefing and Report tabs):
KATL 181724Z 01009G14KT 2SM R09R/4000VP6000FT +RA BR BKN008 BKN010 OVC020 02/01 A2979 RMK A02 P0008
Wx Config tab shows (and what is being presented in FSX):
KATL 181724Z 01009KT 2SM +RA BR CLR000 OVC001 BKN010 OVC020 02/01 A2980
Unfortunately, after posting
Unfortunately, after posting the last reply I paused the simulator changed ASA so that Force Destination Wx, DWC, Direct wind and visibility, enhanced route coverage, and Create Additional Stations are all unchecked. After that I restarted ASA and let it complete it's initialization in FSX, closed it again, restarted it and let it reinitilized again. After that I still have the same problem. While DSM (my destination) is displaying the correct weather, every station around it is still displaying clear skies. This includes XDST. From what I'm reading of the log file, ASA in sending the info, but I don't know what's happening after that. I didn't find the ASA_Log.txt file until you asked for it. I didn't know where it was. If I had, I would've save the previous information from the full flight. I will send what I have. It looks as though it only covers the most recent opening of ASA.
Hi, FS was only running for
Hi,
FS was only running for 14 minutes so I can't tell anything for sure, but things looked normal to that point.
Thanks,
Jim - HiFi Software Sales and Support
Yeah, I had paused and tried
Yeah, I had paused and tried to reset ASA at that point. It seems as though the stations immediately surrounding KDSM (XDST for example) got set to clear skies, so while the correct conditions were present directly over KDSM, within 2nm in every direction it was clear skies. This is not what was going on that day with the weather. That whole area was blanketed with snow fall. I don't know if the OVC-003 might have caused the clear skies (you'll notice in the ASA_Log.txt that is what was sent to XDST). I've never seen that on ANY actual METAR, and I don't think it would show up. That would be a VV003, or something to that effect. I think FSX might not be able to interpret that code.
Also worth noting is that while that output may look normal, it generated identical output in FSX as before I turned off sever options (see my post from yesterday with the log file attached), including Force Destination Wx Zone. All of those surrounding stations should have been output identical to KDSM, and they weren't. They were Clear Skies, while directly over KDSM it had OVC003 and SN.
I have to go fly real-world today. I will try to do another ASA/FSX flight tonight or tomorrow and get the output for you as soon as I can.
I re-flew the flight just
I re-flew the flight just now. I have Force to Destination Wx Zone checked, but Enhanced Route Coverage and Create Additional Stations unchecked. In the log file you'll see that ASA is sending the correct information for KDSM. However, at the time of approach and landing in FSX the conditions were OVC010 and 2sm vis instead of OVC001 and 3/4sm. Also, KPEA and KOXV which are close by and should've been forced to destination weather were depicting clear skies. ASA was telling them to be OVC-008. Actual conditions at those fields at the time were OVC002 and OVC003. I don't know what these negative numbers in the cloud coverage are supposed to mean, but my question is this: is FSX able to depict that?
For this flight, at 5nm from the airport I could see the airport, that is not accurate. The vis went down to 2sm once inside 4nm. 2sm is not the correct visibility. The whole area (80nm around the airport) should've had the same conditions as KDSM, but it didn't.
It doesn't appear to me that ASA is communicating correctly with FSX.
Hi, What operating system are
Hi,
What operating system are you using?
Are you signed in under the administrator account?
Thanks,
Jim - HiFi Software Sales and Support
Vista 64 bit. Yes I'm signed
Vista 64 bit. Yes I'm signed in as the administrator.
Hi, Try running both AS and
Hi,
Try running both AS and FS by right mouse clicking on the icons and Run......As Administrator.
Thanks,
Jim - HiFi Software Sales and Support
I have that set already. I
I have that set already. I run all FSX programs that way so that they work together the way they're supposed to.
Hi, How do you have that set
Hi,
How do you have that set already when that option is a menu item, only available when you right mouse click on an icon? This is a "super" level of Administration Mode.
Thanks,
Jim - HiFi Software Sales and Support
The implication of your reply
The implication of your reply is that I'm lying. So:
Maybe it's because I have a Bachelor of Science in Computer Information Systems, and understand a little bit about how poorly programs interact with each other in a Microsoft-based system. It's a Microsoft OS, and the primary program being used is Microsoft's flight simulator. That just begs for problems. And in fact these problems appear all the time... expensive payware aircraft and add-on programs continually have small glitches in which the only solution seems to be "re-install, maybe that will fix it... it should work."
To be perfectly honest, it's actually NOT an option on my system because I've disabled User Access Control because it causes too many problems. With it enabled I had to go in and manually set Run as Administrator for almost every program on the computer. (As a side note, this doesn't even make any sense considering the ONLY user on that computer IS the administrator account.) So, with UAC disabled, you can't select Run As Administrator, because it actually already recognizes you're logged in as the administrator. Programs work much more smoothly like this. Turning on UAC just to enable Run As Administrator is redundant. So, this is not the problem.
I've run ASA several different ways. The problem as I can see it is that there is a major mis-interpretation as to the use of Force Destination Wx Zone. In real life, when you descend into an airport that is calling low ceilings, low vis, and possibly some sort of precipitation, you don't ever see the airport until you break out at the end of the approach. ASA is trying to simulate the conditions by lowering the visibility at the last second. Every time I do one of these approaches using ASA I can see the airport perfectly until I get to the final approach fix, roughly 5nm out, then suddenly the airport disappears into low vis as ASA drops the vis down. This is nowhere NEAR realistic. Also, it seems that ASA doesn't draw the lowest cloud layer either. If there's an OVC001 layer in the METAR, there should be clouds covering the field. Even if the reported vis is 10sm, you won't see the runway until you break out of the clouds at 100ft. That is what I should see around the destination airport without Force Destination Wx Zone checked. With it checked, those conditions should appear everywhere within 80nm, according to the popup help in ASA. This would be a great feature if it worked. Like someone else said, even if it were reduced to something like 30nm it would be great. The idea being that fast-moving high-flying aircraft will descend into these conditions quickly and want to be able to see the conditions as they approach the area.
ASA is doing a great job of creating lots of enroute weather. But destination weather needs major amounts of work. Especially considering the "fun" part of the trip is doing that approach down to minimums. It's hard to do it to minimums if the expensive weather engine program isn't drawing the weather accurately. It is becoming apparent that this is a programming flaw that needs to be patched. From what I can tell there is a section of code looking at the altitude of the aircraft and drawing weather mostly in the vicinity of that aircraft so that IFR fields are appearing as clear skies because the aircraft is still several thousands feet above field elevation. This isn't good at all. Waiting until the last second to mimic the conditions with ONLY low vis isn't a good option. And yes, I have cloud layers set to maximum in ASA. Low level cloud layers should be getting drawn. I am very close to giving up on ASA until a new patch comes out. I got better destination weather results with FSX's default weather engine.
Enroute weather alone isn't enough to make this program worth the money I've paid for it (please keep in mind that the price tag on ASA is equal to what I paid for FSX). The destination weather needs to be fixed. This is supposed to be a comprehensive weather program covering origin, enroute, and destination.
Hi, Turn off Force to
Hi,
Turn off Force to Destination and compare your experiences.
Thanks,
Jim - HiFi Software Sales and Support
Revised conditions showing up in FSX
These are the actual conditions being depicted in FSX. Not even what's on the Wx Config tab is actually showing up.
Wind 015 13G14kts
Vis 3sm
Clear Skies
Temp 59F DP 53F
Altimeter 29.91
Hi, Please don't even use or
Hi,
Please don't even use or look at the Wx Config screen. That is for setting up your own weather.
Make sure Lock to closest is On in ASA and both ASA and FSX are set to use system time.
Thanks,
Jim - HiFi Software Sales and Support
I can definitely ignore that
I can definitely ignore that screen.
I have Use System Time for Free Flight checked in FSX, and both Force to Real Time and Lock to Closest checked in ASA. I don't know that it'll make any difference, but I have ASA set to display GMT instead of Local.
Hi, That just changes the
Hi,
That just changes the time at the top of the ASA screen. Now, what is the Report screen showing and FSX showing? I'll be back either much later or tomorrow.
Thanks,
Jim - HiFi Software Sales and Support
I don't have a chance to
I don't have a chance to double-check tonight, and I'll be doing real-world flying tomorrow. However, I haven't changed anything yet. All of those settings were already in place when I submitted my original post, so there won't be much difference. During the last flight I attempted (which was the one that I was doing when I submitted the original post), the Report screen was identical to the Briefing screen, but that wasn't what was shown in FSX. I do have DWC enabled and Wind/Visibility Smoothing enabled. Based on my interpretation of the help guide, this disables stations and creates one Global weather condition. Could this somehow be getting set to weather conditions other that the departure airport while still sitting stationary at the departure airport (it is also the same departure airport listed in the flight plan in ASA)?
Hi, No, this is not because
Hi,
No, this is not because of DWC. When you have time do a flight and report what ASA was giving you and what was showing in FS.
Thanks,
Jim - HiFi Software Sales and Support
Again, The original post and
Again,
The original post and the reply directly below it written on 12/18/2009 at 13:04 and 13:06 show what is posted in ASA verses what is showing up in FSX. I didn't have any settings to change from what you told me. I already had ASA setup as you asked me to make sure it was.
I am running ASA and FSX right now and am having similar problems once again. It's supposed to be OVC006 and FSX is showing clear skies. This is enroute, roughly 20nm from the destination airport. ASA was doing alright until the last half of the 2 hour flight. Now it's clear skies. The station I'm closest to is reading OVC006, and the destination is at OVC005. I have Force Destination Wx Zone checked in ASA, and I'm 20nm from the destination airport.
Depiction Output Active is displayed in ASA. As best I can tell, the information isn't making its way into FSX.
Hi, Please attach your
Hi,
Please attach your ASA_Log.txt file and I'll be happy to take a look and see if anything shows up there.
Thanks,
Jim - HiFi Software Sales and Support