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.

ASE Destination Winds Incorrect

Featured Replies

Hi,1. Start ASE.2. Load a plan or enter your departure and destination airports and process.3. Submit a texture snapshot if you wish.4. Click on the Install GE Pro Textures icon and GEP will run and submit textures. Close GEP if it stays open.5. Start FS9.6. After FS9 is loaded at an airport click on the Refresh AI Aircraft icon.

  • Replies 74
  • Views 13.2k
  • Created
  • Last Reply

Top Posters In This Topic

Hi Bob,After FS and AS are started and running are you refreshing the AI system with the icon in AS?
Did that tonight and had better results. Unfortunatley, I had almost a 90 degree crosswind, so I can't say for sure, but it if the AI refresh applies to the destination airport, then that will probably do the trick.I'll setup a flight just for the purpose of testing and let everyone know.

Bob Donovan - KBOS

Hi,1. Start ASE.2. Load a plan or enter your departure and destination airports and process.3. Submit a texture snapshot if you wish.4. Click on the Install GE Pro Textures icon and GEP will run and submit textures. Close GEP if it stays open.5. Start FS9.6. After FS9 is loaded at an airport click on the Refresh AI Aircraft icon.

Thanks Jimif it is so important, why you not make it automatic for each flight?

Hi,Make what automatic?

Hi,I also have problems with destination Wx. I try to experiment with simple flight from LEIB Ibiza to LEPA Palma de Mallorca. During descent from fl100 and on final wind is changing a lot. It really makes aproach impossible. Wind changes to correct one after touch down. I also noticed that there is another Wx station on ASE map for LESB (3nm north from LEPA) with strange metar. I dindn't menage to find any metar for LESB on internet anywhere (sites like allmetsat.com for exmpl.). But ASE shows absolutely diffrent wind for LEPA and LESB, also metar time for lesb changes every minute (it starts like 081821Z 14808KT...), so I have two stations LEPA with 05009KT wind and LESB with 14808KT, those stations are very close to each other, and maybe this causes problems?Similar situation is for ex. in Poland - metar for EPKK (Krakow) gives wind 05007KT and for EPKP (small airfield) it is 11806KT - quite a difference in directions, when there is about 15nm of distance. No metar for EPKP can be found on net, and its time designator also changes every minute.

Pawel Dragan

Poland, Gdansk

the problem I have is on approach, ATC has the winds wrong, so they tell me to land on the opposite runway, I just ignore them, and by the time I get to my destination, the winds are correct. It's strange but I just deal with it. Using ASE with fsx and fsuipc smoothing winds. I did recently uncheck force destination wx, but kept weather change to 50%

The only way I manage to correct the winds are by going into FSUIPC and turning the weather off, this seems to reset the winds instantly to what is expect.FSX see the weather if I press Ctrl Z so seems to be getting to FS, but I am flying the Level D and the winds reported are 90% of the time incorrect during flight, I have set the update from 0% to 100% updates to try to change it, it has no affect, unless I open fsuipc to turn the weather off. The winds on the destination airfiled are usually 180

Dave

Before I turn off FSUIPC weather controls, can someone help me with the benefit of using it with ASE?Refreshing the AI certainly puts the AI on the right runways with the wind, but ATC assigns me the runway anywhere from 60mi to 120mi from the airport.It appears they are using my present-position weather, rather than destination weather when doing so.The reason I believe this is because the ATIS seems to be grabbing the wind conditions of my present position rather than the airport conditions.I bet there's a little checkbox somewhere that will clear this up. There's so many combinations, getting the proper checks/unchecks will probably do the trick.

Bob Donovan - KBOS

Hi Bob,Please turn off DWC and see what happens.

Hi,That link is not working for me.

The youtube link seems to be working today if you want to take another look.It really doesn't tell you much, just shows the problem.I'm still fiddling with the settings one check-box at a time.I know there's a proper combination somewhere.

Bob Donovan - KBOS

Hi,I would need to know what ASE is showing and what FS is reporting.

  • 2 weeks later...

I'm seeing this issue with ASE and FSUIPC. I don't use DWC since I understand this messes up Radar Contact (performance and destination ATIS wrong).I do use FSUIPC for wind, temp and pressure smoothing. Now, when Radar Contact provides destination weather it provides the same weather as the departure airport even though when I land it is more in line with the weather reported on 122.02. However, I get directed to the wrong runway and land in a tail wind.I'm not sure when I sould refresh the AI, so I refresh after the initial weather process completes. However "Depiction Output Active" always stays on - is this to do with FSUIPC?Can you help please?Best wishesSteve Munn

Stephen Munn

 

Hi,Refresh AI after a flight is loaded in FS.Depiction Output may stay lit for a long time if you are in an area of may airports and this is normal.

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.