Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Build 431, FSX, and upper winds

Featured Replies

With 431 and FSX SP2 I'm just not getting the upper winds I'm supposed to be getting. If you look at the screenshot, I'm flying at FL340 so I should be getting 248 @ 62. What I'm actually getting is 261 @ 25. Also, the value stays constant for 10, 20, 30 minutes at a time. I'm not using DWC, and FSUIPC is not controlling any weather.PS: The reported overcast is not reproduced, either.

Petraeus

 

Hi,Check the date on your computer as ASA is reporting the date to be September 7, which would throw the data way off.Thanks,

Sorry Jim, but shouldn't ASA depict the weather it shows as "active" (thus a file it reads and depicts?), regardless of the actual or FS date/time?Cheers,Fede

Federico Bellato

  • Author
Hi,Check the date on your computer as ASA is reporting the date to be September 7, which would throw the data way off.Thanks,
It was today's weather. I wasn't using any historical weather. 09/07/2009 is the ninth of July, European-style.

Petraeus

 

Hi,If the date is a "future date" then there is no data to match. Then the TAF may be used.To the OP, I am not sure what was happening then. Please report if this keeps happening for you.Thanks,

  • 3 weeks later...
  • Author

quote name='JSkorna' date='Jul 11 2009, 02:01 AM' post='1603058']To the OP, I am not sure what was happening then. Please report if this keeps happening for you.Thanks,Here's another example. I'm at 28000 feet and so the winds should be between 213@51 and 209@66, but what I'm getting is 284@27. [

Petraeus

 

To the OP, I am not sure what was happening then. Please report if this keeps happening for you.Thanks,Here's another example. I'm at 28000 feet and so the winds should be between 213@51 and 209@66, but what I'm getting is 284@27.
Petraeus you aren't using the official SP1 release of ASA you are using build 431, you should be using 433.

Cheers, Andy.

  • Author
Petraeus you aren't using the official SP1 release of ASA you are using build 431, you should be using 433.
When I started this thread there was no 433.Has something been done explicitly between 431 and 433, with regard to upper winds. that would make a difference?If not, I could go to SP1, but would likely have the same problem.

Petraeus

 

Hi,What Build of ASA are you running right now? Is it at least B433?I am not sure between 431 and 433, but I would like you to have B433 and see what you get.Thanks,

  • Author
Hi,What Build of ASA are you running right now? Is it at least B433?I am not sure between 431 and 433, but I would like you to have B433 and see what you get.Thanks,
It is an intermittent rather than a persistent problem. I installed 433 last night, and a very quick test showed that upper winds were OK. However, that's not conclusive, because half the time they were OK with 431.I'll keep watching, and post again if I see the same problem.

Petraeus

 

Hi,OK, thanks.

  • 2 weeks later...
  • Author
I'll keep watching, and post again if I see the same problem.
And the problem is still there in SP1.The Arabian Gulf is not noted for its high upper level winds, yet here I am in a wind of 260@79 at FL 390, when ASA is reporting (quite correctly) [email protected], the root of the problem is simple - the upper level winds when ASA first starts, are 'sticking' throughout the flight. 260@79 was what I was seeing as I set out over Europe, and it just never changed or got refreshed by ASA after that.

Petraeus

 

And the problem is still there in SP1.The Arabian Gulf is not noted for its high upper level winds, yet here I am in a wind of 260@79 at FL 390, when ASA is reporting (quite correctly) [email protected], the root of the problem is simple - the upper level winds when ASA first starts, are 'sticking' throughout the flight. 260@79 was what I was seeing as I set out over Europe, and it just never changed or got refreshed by ASA after that.
Hi Petraeus,Unfortunately, this is what I'm also getting with 433 that I didn't see with 431. 431 is not perfect and winds aloft are often not exactly what ASA reports they should be. However, in my experience 431 gives the best results I've experienced so far with ASA or ASX. Unfortuanately, with the weather in FSX being the mess it is I think HiFi have just about achieved the best they can.Regards,Dan Parkin.

Best Regards,

Dan Parkin.

Hi All,Can all of you give something a try? Remove FSUIPC4 and then fly in some of the same areas where you are experiencing this. I realize that you might not be able to run some other FS programs, but a user and I have been corresponding through e-mail and he MAY have discovered that FSUIPC MAY be involved here. PLEASE DO NOT make any reports to Pete yet. We need some confirmations first before moving in any direction.Also, please make sure this is with B433/435. I don't want to move backward to a beta version of SP1. If a user personally moves back that is fine and I understand fully, but for this test we need a common version and that would be the official SP1 release.Thanks everyone for your patience in working through this with us.Thanks,

  • Author
Hi All,Can all of you give something a try? Remove FSUIPC4 and then fly in some of the same areas where you are experiencing this. I realize that you might not be able to run some other FS programs, but a user and I have been corresponding through e-mail and he MAY have discovered that FSUIPC MAY be involved here. PLEASE DO NOT make any reports to Pete yet. We need some confirmations first before moving in any direction.Also, please make sure this is with B433/435. I don't want to move backward to a beta version of SP1. If a user personally moves back that is fine and I understand fully, but for this test we need a common version and that would be the official SP1 release.Thanks everyone for your patience in working through this with us.Thanks,
That didn't make any difference. The upper level winds still stuck - even after clicking "refresh". Build 433.

Petraeus

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.