ASP4 and ASXP Updates Official!

P3Dv4.5 HF3 compatibility, further fixes, adjustments, and network/stability improvements highlight these latest updates. Thanks to everyone who participated in the OPEN BETA!

See our Downloads Page to download the update(s) now!  


Update 041920 – Active Sky XP (ASXP)

  • X-Plane compatibility updates
  • Fixed issue with API regarding multiple sigmets not being returned
  • Changed registration process to require e-mail address verification before user account verification, preventing typo or other email access issues
  • Adjusted registration process to prevent stuck email registration step if process fails during initial email verification, now continues normally
  • Server weather data network complete overhaul using new cloud computing components and network resources for increased performance, better data consistency between sessions and better load balancing
  • Attempted fix for problem with Privacy Policy date parsing using Arabic calendar/region settings
  • Fixed problem with some stations in flight plan parsing (i.e. KTNX) from Navigraph data when an unexpected 3-letter (TNX) station existed in the airport database
  • Fixed problem with some sound devices in networked mode, during audio device selection process from server, when using device with non-ASCII UTF-8 characters X-Plane compatibility updates
  • Changed metar.rwx suface data output filename casing to METAR.rwx
  • Fixed potential issue with email verification during registration not showing verification code entry window

Update 041520 – Active Sky for Prepar3D v4 (ASP4)

  • P3D v4.5 HF3 compatibility updates
  • Attempted fix for potential wind check message crash
  • Fixed issue in API regarding only single sigmet being returned
  • Changed ASP4 use over to new weather server system for increased performance, data consistency between sessions, and better load balancing
  • Fixed issue where some stations/airports (i.e. KTNX) may parse incorrectly in flight plans
  • Fixed issue where some sound cards/audio devices with non-standard ASCII characters (i.e. UTF-8) may not work correctly in networked mode when selecting a server audio device for AS audio output
  • Attempted fix for invalid date parsing for Privacy Policy with Arabic calendar/region settings