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.

Having problems with V1.1......

Featured Replies

I have been using the V1.0 program without any problems and today I downloaded/installed V1.1. I have the latest FSUIPC 2.95 installed and the settings are as recommended in the ActiveSky manual. I also have not changed any of the options within ActiveSky and use the ones that are recommended(same ones I was using with V1.0). The problem is that FS does not seem to be communicating with ActiveSky very well. I always start FS first and pick my start location along with clearing the WX. I then minimize FS and start AciveSky and I can see that it picks up on the nearest station and displays the current METAR info. I will then go back into FS and start my flight. At this point, it usually takes about 5-10 minutes for the WX to update. Using V1.1, the WX is not updating at all. The WX stays clear(when it really is not). I waited about 30 minutes with no luck. After playing around with it and restarting a few times I got it to start up with the correct WX. I then moved myself to another airport via the menu in FS. Normally, this will cause ActiveSky to update with the METAR at the new location. Now it keeps the previous airports METAR and does not update the new location. I never had a problem with this before. After I moved to the new airport, I minimized FS to check ActiveSky and it still was showing the METAR from the previous airport. I'm kinda confused at this point. Any insight is appreciated! BTW- On one of the times I actually got WX, it was zero visibilty even though the METAR showed visibilty greater than 6 miles.(????)Eric

  • Commercial Member

Eric,I am not sure what is causing this, but can you uninstall all, reinstall v1.0, and let me know if the problem clears up? I'd like to isolate it down to either an update installer problem, problem with 1.1, or another issue effecting it. Thanks!-Damian[table border=0" cellspacing="30" cellpadding="0][tr][td align = "left"]Damian ClarkHiFi Simulation SoftwareDeveloper of ActiveSkyThe next-generation weather environment simulation for FS2002!http://hifi.avsim.net/activesky[/td][td]http://hifi.avsim.net/activesky/images/wxrebeta.jpg][/td][/tr][/table://http://hifi.avsim.net/activesky/ima...][/tr][/table

Damian Clark
HiFi  Simulation Technologies

Hi Damian,I too am having problems with 1.1 In my case visibility drops to zero and initially temperature dropped to -84 deg, yes thats a minus.When I go back to 1.0, i.e. don't even uninstall, just run it, as I kept a copy of the directory before the install and this is not a problem.Second:I fly in Australia and I have a conversion program to create offline files from the Australian area forecasts. I'm trying to understand how ActiveSky selects the Winds aloft to use, what is the algorithim, I'm hoping it searches for the nearest reporting station but it does not appear to do that, e.g. If I am at an airport with a reporting station ActiveSky seems to select the first in the list which could be hundreds of miles away. How does activesky select the winds aloft station to use from the offline files.Many thanks in advance, and I've reverted back to 1.0 to see if you can fix the visibility and temp problem of 1.1Regards,Steve

Damian-It seems like Radar Contact v3.0 may be the culprit. I tried it without running RCv3 and it seemed to be OK. When I tried it again with RC, I had the same WX problem. I did not have any problems using it with RCv3 on Version 1.0. I read in your announcement that it is compatible with RCv3.01 due out on 1-20. I have not seen anything regarding an updated release on the RC site or their forum. Does this mean that ActiveSky version 1.1 is NOT compatable with RCv3.0?Thanks again!Eric

Hi Damian,I don't use Radar Contact v3.0, but I do use wideclient and wideserver latest version.Steve

The visibility issue is not related to Radar Contact. I was flying into KALB and it was very clear with 20+ mile visibility. METAR report was greater than 6 miles but it suddenly went to 1 mile on approach.Eric

Hi Damian,Same problem here. Installed 1.1,installed latest FSUIPC, ran with Radar Contact 3.0, visibiliy 0/0 at both departure (KLAS) and arrival (KFTW) airports. Vic

I agree. I don't have Radar Contact and I have serious visibility issues on the ground. On the ground at KSLC and PANC I can hardly see my plane in spot view even tho wx has greater than 6 miles. Never had this in V1.0.Bob Dodge

>The visibility issue is not related to Radar Contact. I was >flying into KALB and it was very clear with 20+ mile >visibility. METAR report was greater than 6 miles but it >suddenly went to 1 mile on approach. >>Eric Well, by now everyone has noticed the "bug" in V1.1! I have no Wide-Thingy, no Radar-Thinging etc. On the bright side - I must say that it has the most realistic simulation of a fog bank moving in on the ground! Just sat on the runway and waited - very reliable!That being said, I was stupid enough NOT to have saved version 1.0 (What was I thinking?....that the newest version was an improvement?....)....so.....It's back to the old reliable FSMeteo for realistic weather settings.........Just when I was starting to really love ActiveSky too!.......gwillmot

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.