AS2016 for P3D is NOT COMPATIBLE with P3Dv4.  A new product, Active Sky for P3Dv4 has been created for specific P3Dv4 use.

This is a FREE UPGRADE for AS2016 for P3D users. See here to download and participate in the ASP4 OPEN BETA.  ASP4 is expected to release soon!

Error: Crash/error on startup of any Active Sky product (FileNotFoundException referencing _nLoad)

Details:

We have had a few reports recently from false-positive via Microsoft Windows Defender where detection will initiate on temp files created by what appears to be standard .NET operations.  We have confirmed multiple times that no malware exists and have repeatedly sent files for analysis to Microsoft, where it will clear, but then come back occasionally for some users.  During updates of our products, we notice a higher frequency of these issues since it appears the previous "whitelisting" of our software is no longer valid for the new version and must undergo this new "whilelisting" process.  

We apologize for the inconvenience, however this is beyond our control and apparently due to aggressive "code detection" with false-positives.  There are several solutions to resolve this:

1) Please ensure your Windows is up to date with all the latest updates

2) Ensure that Windows Defender has been updated with latest virus definitions

3) Uninstall Active Sky, remove any "quarantined" items from Windows Defender

4) Reinstall Active Sky

These steps will usually allow Active Sky to run properly without further issues.

If the issue continues, the following steps will allow the product to run:

1) In Windows Defender, either allow the detected threat or exclude the found item.  See this link for details: https://www.thewindowsclub.com/manage-quarantined-exclusions-windows-defender-security-center

2) It is recommended to submit the detected threat to Microsoft to have them analyze and whitelist/clear this software accordingly to prevent this from happening in the future.  You can submit threats for analysis here: https://www.microsoft.com/en-us/wdsi/filesubmission

If you are unable to obtain resolution with the above steps, please open a new ticket with details and we will assist directly.

Keywords: Rain, starts, stops, precip, AS16, ASP4, ASN

Related Product(s): Active Sky 2016 for FSX and Prepar3D v3, Active Sky for Prepar3D v4, Active Sky Next

Description

We often receive technical support requests regarding the unexpected starting and stopping of rain/precip in FEW and SCT (scattered) cloud coverage conditions when rain is reported even though SH (showers) are not indicated.  This is working properly and as designed according to our advanced precipitation and radar simulation which accurately considers actual cloud depiction in sim and applies the realistic behavior/rule that precip cannot fall from clear air.  Clouds move with wind in FSX and P3D, and in FEW and SCT conditions, it is normal for rain to start and stop accordingly as occasional nimbus clouds pass overhead, regardless of SH (showers) element existing in the METAR string.

Details

The effect is described in the AS16 (pg 35) and ASP4 (pg 33) User's Guide - Generic Precipitation Display.

AS16 and ASP4 include advanced precipitation and radar features which constantly monitor the cloud positions as actually depicted within the simulator.  The occurrence, type and intensity of precipitation will thus change depending on the existence, type, thickness and convection properties of the simulated cloud that is overhead the aircraft.

Users will experience what may appear as "showery precip" as "few" or "scattered" nimbus (rain) clouds pass overhead, so it will be normal for rain to start and stop or change intensity over time.

Steady rain will occur when the area is covered in overcast cloud layers or fast moving broken layers (typical with nimbostratus).

METARs are a glimpse in time, showing conditions at the time of observation, using equipment such as ceilometers (measuring cloud base heights and coverage) and rainfall sensors (if equipped).  The measurement location and scope is very specific and small, and does not account for change over time even as short as a few seconds/minutes.  The use of the SH (showers) METAR element is generally associated with convective precipitation i.e. cumulonimbus and not indicated in the more stable non-convective nimbus clouds. 

If you require further assistance please visit the forum or feel free to submit a ticket.

Please also see this link for REQUIRED INFORMATION when submitting a ticket:

http://support.hifitechinc.com/Knowledgebase/Article/View/29/0/required-information-when-submitting-a-support-ticket

More Information

For more information please visit:

HiFi Forums: http://www.hifitechinc.com/forums

HiFi Support Center: http://support.hifitechinc.com/

Related Product: Active Sky Next, Active Sky 2016 - Related Version: ALL

Description

Also known as the "8-minute freeze", this can occur intermittently during a longer flight.  When the freeze occurs, all motion on the simulator stops.  Sound may be observed still playing, but the FS program stops responding.  Approximately 8 minutes later, the simulator "comes back" and operates normally.

Resolution

With much research and testing, HiFi has determined that this freeze is related to the threading, affinity and the collision and deadlocking of terrain load fiber processes within FSX.  It is almost unanimously related to use of Hyper-Threading, and can affect any FSX installation, including default/stock installations without any add-ons.  Use of weather add-ons increase the likelihood of this freeze.

Since this issue can be made worse when using Active Sky, although it is an FSX problem not directly related to our product, we provide potential solutions below to help anyone experiencing these freezes:

1) Use an appropriate AFFINITYMASK setting within your FSX.cfg configuration file.  This setting specifies which cores are used for FSX.  Using too many cores, or improper cores can cause freezes.  If you are using 6 or more cores, it is important to limit the cores used, as too many cores causes synchronization problems and more potential freezes.  We recommend using 3 cores maximum, regardless of HT enabled or not.

2) ASN will warn and optionally apply an appropriate AFFINITYMASK setting if it is not already configured.  The setting used will be based on using up to 3 physical cores, but depends on your CPU and number of cores, and if HT is enabled or not.

3) Use the UIAUTOMATIONCORE.DLL fix -  http://www.avsim.com/topic/326554-fsx-crashes-when-using-menus/page-3?hl=%2Buiautomationcoredll#entry3122893

4) Use lower resolution cloud textures and setting your Cloud Draw Distance to 90 or less.

5) Lock frame rate lower - try setting to no more than 30.

6) Update video drivers.

7) Run FSX in compatibility mode for win 7 (if using win 8 or above).

8) Disable SLI if activated. 

9) Make sure you are running the latest version of Active Sky (www.hifitechinc.com/downloads) .

More Information

For more information please visit:

HiFi Forums: http://www.hifitechinc.com/forums

HiFi Support Center: http://support.hifitechinc.com/

Related Product(s): ALL

Background

HiFi does not provide technical support for the SimConnect configuration part of a networked setup.  While our products generally support networked configuration, properly configuring the client/server environment, system permissions, Windows rights, firewall and security software permissions and SimConnect itself is outside the scope of our products and technical support offerings.

We highly recommend that a networked SimConnect configuration is not attempted unless you have advanced Windows networking experience.

Assuming SimConnect is properly configured and all other client/server environment, system permissions, Windows rights, firewall and security software permission settings are correct, our products should operate properly.

Common errors and symptoms related to improper configuration include:

• Failure of ASN/AS16 to connect to simulator (constant "Waiting for simulator" status)
• Ambients error

Detail

There are several common issues that we'll review here:

• Improper SimConnect.xml and SimConnect.cfg settings
  • This results in failure of ASN/AS16 to find the simulator and connect to it, with a constant "Waiting for simulator" status.
  • The solution is to properly configure SimConnect.  Refer to the resources listed below for help.

• SimConnect.xml and SimConnect.cfg in the wrong locations
  • This results in failure of ASN/AS16 to find the simulator and connect to it, with a constant "Waiting for simulator" status.
  • The solution is to properly place the SimConnect.xml and SimConnect.cfg files.  SimConnect.xml should be located in the simulator's AppData path on the server.  SimConnect.cfg should be located ONLY in the user's My Documents folder.

• Duplicate SimConnect.xml and/or SimConnect.cfg files (usually in the ASN/AS16 folder)
  • This results in failure of ASN/AS16 to find the simulator and connect to it, with a constant "Waiting for simulator" status.
  • The solution is to remove any duplicates and ensure the configuration files are located ONLY in the proper locations (see above).

• XPACK/SP2 version of SimConnect client not installed
  • This results in the failure of ASN/AS16 to find the simulator and connect to it, with a constant "Waiting for simulator" status.
  • A SimConnect client version error may also be seen via message box or in the log file.
  • RESOLUTION:
  • The XPACK/SP2 version of the SimConnect client (simconnect.msi) is required for proper ASN operation and sim connectivity.  This should be installed on your CLIENT computer.
  • For FSX Boxed you must install the SDK and then update it to SP2 incrementally via SP1 and SP1A.  Once updated, the simconnect.msi file within the SDK folders will be properly updated to SP2/XPACK client.
  • For FSX: Steam Edition, you will find the simconnect.msi file under the SDK subfolder, located within the SteamApps\Common\FSX folder.  SDK installation is not required.
  • For P3D: You will find the simconnect.msi file under the REDIST subfolders, located in the P3D install folder.
  • For all simulators:  Ensure that you are using the XPACK/SP2 version of the simconnect.msi file.  Copy the file (if required) to your CLIENT machine and run/install it there.

More Information

For more information please visit:

Google Search for “simconnect help”:

http://www.google.com/search?q=simconnect%20help

Microsoft SimConnect Documentation:

https://msdn.microsoft.com/en-us/library/cc526983.aspx#Thesimconnectcfgfile

ASN User Guide (pg 80-88 regarding SimConnect configuration):

http://nimbus.hifitechinc.com/ASNInfo/ASN_User_Guide.pdf#page=81

HiFi Forums:

http://www.hifitechinc.com/forums

HiFi Knowledgebase Article for FSX:

http://hifisupport.kayako.com/Knowledgebase/Article/View/6/8/networked-configuration-with-simconnect

HiFi Support Center:

http://support.hifitechinc.com/

Related Product: Active Sky Next, Active Sky 2016 - Related Version: ALL

Description

Resolution

SP2/Xpack version of SimConnect needs to be installed for correct functionality of ASN/AS16. This can be found in the SDK folders of your FSX or P3D installation. See the install/SDK folder for more information. The installation file for SimConnect is simconnect.msi.

More Information

For more information please visit:

HiFi Forums : http://www.hifitechinc.com/forums

HiFi Support Center: http://support.hifitechinc.com/

Related Product: Active Sky Next, Active Sky 2016 - Related Version: All 

Description

Getting the right level of performance out of your flight simulator and all add-ons can be a complicated matter, but we will attempt to do our best to inform you of the various options, features and considerations that relate to your overall performance experience.

We highly recommend reading the User’s Guide and the Performance Considerations chapter which cover many of the topics and recommendations covered here.

Certain settings can drastically affect simulator frame-rate performance.  Some settings influence performance levels differently than others.

Resolution

After years of testing, we have determined a specific priority of performance-related settings:

1. The complexity of the weather environment

   1. This includes the weather data and number of cloud layers, vertical development, number of drawn cloud sprites, and typically is not under the user’s control other than changing location, historical time period, or maximum number of cloud layers and other synthesis options that can affect the cloudscape complexity

2. Cloud Draw Distance

   1. The configured cloud draw distance (which can vary dynamically with ASN/AS16 when using minimum and maximum values) drastically affects the number of cloud sprites shown.  The minimum acceptable distance should be used to achieve the best performance.

3. 3D Cloud Texture Resolution

   1. When using third-party graphics add-ons that include cloud textures, care should be taken to reduce the texture resolution to a reasonable level to not overload your graphics card.  512x512 resolution is highly recommended in most cases.  The lower the resolution, the higher the performance.

4. Graphics card and related settings

   1. While FSX/P3D do not make optimal usage of GPUs at this time, certain GPU settings including anti-aliasing and transparency anti-aliasing can greatly affect the frame-rate.  The minimum acceptable anti-aliasing settings should be used to achieve the best performance.

5. ASN/AS16 Performance-related Settings

   1. As mentioned in #2, cloud draw distance has a significant effect on performance and memory. Values larger than 150 should be avoided, because they are associated with increased frequency of Out of Memory (OOM) cases and/or other abnormalities, such getting no clouds rendered.

   2. Most METARs contain a maximum of 2 to 3 cloud definitions. So, in most cases the Maximum Cloud Layer option should be set accordingly. Note, that this setting affects depiction where ASN/AS16 uses interpolation for cloud synthesis.

   3. Using local suppression mode can cause a significant increase in performance, especially during cloud transitions.  Enabling local suppression prevents smooth cloud redraws, reducing the number of cloud sprites to ½ in many cases.  We highly recommend using this feature if you’ve exhausted other attempts at improving performance.

       

More Information

For more information please visit:

ASN User’s Guide - Performance Considerations Chapter:

http://nimbus.hifitechinc.com/ASNInfo/ASN_User_Guide.pdf#page=22

HiFi Forums:

http://www.hifitechinc.com/forums/showthread.php?3681-FPS-suffering!&highlight=inspector

AVSIM PMDG Forums:

http://forum.avsim.net/topic/324786-nvidia-configuration-guide-inspector-2xxxx-drivers-version-20-explanations-of-all-settings/

Related Product: Active Sky Next, Active Sky 2016, Active Sky Prepar3D v4 (ASP4) - Related Version: All

NOTE: If you are running Prepar3D v4 with AS2016, see this Article.  

Description

After running ASN, AS16 or ASP4 and your simulator, and connection is established, an Error message pops up and indicates “ASN/AS16/ASP4 cannot control ambient weather parameters correctly, thus it cannot function properly at this point and will shut down.  Further ASN/AS16 or AS_P3Dv4 operation is not possible. "

Alternatively, a similar "Ambients Error" and "Could not communicate with ASConnect" message may be presented.

Resolution

If you are receiving this error, it indicates one of the following conditions:

1. If using Prepar3D, the most common explanation is that your paths are not set to the proper version 3 locations.  Specifically, your simulator installation path, simulator AppData path, and ASConnect installation path must be set to the Prepar3D locations.  Also ensure that the latest update for ASN/AS16/ASP4 for P3D is installed.  The latest version can be downloaded from www.hifisimtech.com/downloads .
   
   
2. If using FSX Steam Edition, the most common explanation is that an add-on has created an improper sim AppData folder, and now ASN/AS16 is finding the wrong path based on the existence of this improper AppData folder.  This happens when the only sim installed is FSX:SE and FSX Boxed was never installed, and certain add-ons have been installed which create files in the wrong appdata location.  The solution is to keep your sim closed, run ASN/AS16, and change settings/options/general Simulator AppData Path to the correct location, which is most likely C:\Users\[username]\AppData\Roaming\Microsoft\FSX.  Note that the improper folder in these cases is ..\FSX-SE (changing from FSX-SE to FSX will solve the issue).  After making this change, Restart ASN/AS16 and then start your simulator.

3. ASConnect and the accompanying as_btstrp.dll (integration component to ASN/AS16/ASP4) is not able to run correctly due to security, AV, Firewall or File Access Rights issues.  Make sure you have excluded ASN/AS16/ASP4, FSX/P3D and the [sim folder]\as_srv\as_btstrp.dll file from scanning if you experience this error.

4. ASConnect is not able to be properly configured to run at FSX/P3D startup due to invalid network share/rights to the Simulator's AppData Path (specifically, dll.xml cannot be modified).

5. FSX/P3D Paths are not correctly configured.  First, try confirming your paths.  Without FSX/P3D running, load ASN/AS16/ASP4 and visit the Settings Screen.  In General Options, confirm that your Simulator and Simulator AppData Path are correctly configured.  If not, please select the proper paths and then restart ASN/AS16/ASP4.
   
   

If this does not resolve this issue, please follow the below steps:

1. Please perform an uninstall of ASN/AS16/ASP4 in order to rule out any installation issues.  When uninstalling, all checkboxes should be checked to remove all saved data, ensuring a "clean" install environment

2. Please disable real-time AV scanning temporarily (on networked setups, please do this on both machines)

3. Install ASN/AS16/ASP4 using the latest full version installer from http://www.hifitechinc.com/downloads

4. Run ASN/AS16/ASP4, and follow the prompts for final installation/configuration including the running of the ASConnect installer.  On networked setups, you will need to copy the ASConnect_FSX_Install.exe or ASConnect_P3D_Install.exe from the client's ASN/AS16/ASP4 install location to the server computer, and run the .EXE on the server.  Once this is done, finish loading ASN/AS16, then exit ASN/AS16.  *** MAKE SURE TO CHOOSE THE CORRECT INTENDED SIMULATOR/VERSION INSTALLATION FOLDER DURING ASCONNECT INSTALL ***

5. Using your AV software, add a "trust" or "exclusion" to for the ASN/AS16/ASP4 program.

6. Using your AV software, add a "trust" or "exclusion" for the ASConnect components which are all .dll files located in [fsx/p3d install path]\as_srv.  On a networked setup, this will be on your server machine.

7. Re-enable your real-time AV scanning. 

8. Run ASN/AS16 and allow it to initialize.

9. Run FSX/P3D "as Administrator" (right click the icon, choose "Run as Administrator")

If everything is working properly and the "Cannot control ambient weather parameters" error no longer shows, you can now be confident that your configuration is correct.  

If the error continues, there may be a problem specific to your configuration.  In this case, please open a support ticket at http://support.hifitechinc.com with a Log Export (Tools->Export Logs) which can be done WITHOUT YOUR SIM RUNNING (to prevent the ambients error/shutdown).  See this link for REQUIRED INFORMATION when submitting a ticket:

http://support.hifitechinc.com/Knowledgebase/Article/View/29/0/required-information-when-submitting-a-support-ticket

More Information

For more information please visit:

HiFi Forums: http://www.hifitechinc.com/forums

HiFi Support Center: http://support.hifitechinc.com

Related Product: Active Sky Next, Active Sky 2016, ASP4, ASP3D - Related Version: All

If you are using AS2016 with Prepar3D v4 - See here: 

http://hifisupport.kayako.com/Knowledgebase/Article/View/45/0/logging-andor-ambients-error-on-as2016-for-p3d-and-p3dv4

Description

When running ASN, AS16 ASP4 or ASP3D an error message pops up indicating “No ASConnect Log”.  In some cases, further ASN, AS16, ASP4 and ASP3D operation is not possible.

Resolution

Usually this is related to a path problem. Please confirm that your simulator's install location and AppData folder are properly selected in the settings screen.

You can also manually adjust the paths via the registry editor at location HKCU\SOFTWARE\HIFI\ASN(or AS16)FSX\FSXPATH (and FSXAPPDATAPATH) for FSX/FSX-SE, or HKCU\SOFTWARE\HIFI\ASN(or AS16)FSX\P3DPATH (and P3DAPPDATAPATH) for Prepar3D.

In addition, please make sure you are running the latest version. To download, please visit: www.hifitechinc.com/downloads .

Finally, please ensure that you have proper write access to the simulator's program files and appdata folders.  You may need to run your simulator "as administrator" if you have not assigned ownership/write access to the relevant paths.

More Information

For more information please visit:

HiFi Forums : http://www.hifitechinc.com/forums

HiFi Support Center: http://support.hifitechinc.com/