Beta testing is suppose to iron out these small bugs. However, it gets extremely frustrating when you are trying out a new version of the program and it freezes halfway to two-thirds of the way through the flight. I got great support from Dave Opper who went beyond the call of duty digging through the HiFi files to find my previous registrations for ASA/ASE (for installation of AS2012). I apologize for my blunt and probably rude comments regarding ASN. If you are having any issues you are recommended to open a support ticket at for direct support from HiFi staff. We're also actively working with Peter Dowson to try and identify this new issue and resolve it. The recommended steps are intended as an interim identification and resolution of the issue to get users up and running.Īs you also note, this issue in your case (Jim) was related to FSUIPC compatibility issues which only just occurred post ASN-release. And we're doing our best to identify and resolve this more elegantly for everyone. However, after 1 year of testing by approximately 30 testers with various configurations, this issue did not come up and as mentioned it is only a small percentage of users facing this. Thank you for your assessment of our poor programming and beta testing. Note that this is not a wide-spread issue and we are doing our best to identify the reasons that this happens and avoid a complicated configuration process to get things to work, but at this stage we are still identifying the details. It is simply poor programming that should have been caught by the beta team or the developers.Īs indicated in our support forum threads there are a few users experiencing this and we have found several potential causes and solutions. I would not recommend anyone to mess around with their system firewall. I do think it is wrong that anyone who installs an addon has to make sure all of the above has happened. Just posting what I have done and it did not fix my problem.
![active sky next trial active sky next trial](https://i.ytimg.com/vi/YGv5nN03ebY/maxresdefault.jpg)
#Active sky next trial windows
This was done on Day 1 when Windows was first installed. When I right click any and all of the folders, it says I'm the owner. That has stopped a lot of errors/problems but not this one. I installed the program "Take Ownership" and made sure I own the FSX folder and any folder located on another HDD that FSX might access.
#Active sky next trial simulator
Nothing in Windows Firewall indicating these modules are being excluded from scanning.Ĭ:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\as_srv\as_=1 Well, let's go through the checklist (my responses in bloody red):
![active sky next trial active sky next trial](https://img.informer.com/screenshots/6465/6465065_1.jpg)
It really is frustrating especially when two-thirds into your flight and fsx freezes and you get a StackHash error and the error report in OP.īefore I even saw this post, I had already taken ownership of the main fsx folder and everything ASN.
![active sky next trial active sky next trial](https://i.imgur.com/pwXiTBp.jpg)
I have been seeing this error message quite frequently.
#Active sky next trial full
If you continue having this problem, please open a support ticket at with a full log export (tools, export logs) as well as your dll.xml and fsx.cfg, and please also list which AV/firewall/security software you are using. If you've tried everything else, you can try to isolate this to access issues by doing one or more of the following:Ī) Assign ownership of the Program Files (x86) folder to your user account ( ) and assign read + write permissions to your user account for the FSX folderī) Run FSX "as administrator" (Right click the FSX icon, choose "Run as administrator") This seems to affect some users but not all. If you said no, you will have to either clear the entry in fsx.cfg for as_btstrp.dll (as_connect) and restart FSX, or change the value at the end of that entry to 1Ĥ) This may be related to rights access of the Program Files (x86) folder. Please try the following to solve problems with "cannot control ambient weather" message:ġ) Ensure that the folder (FSX folder)\as_srv is excluded from virus scanning.Ģ) Make sure ASNext (asnext.exe) and the ASConnect modules (as_btstrp.dll and as_connect.dll in same folder as above) are excluded from scanning in your firewall/security software, as some security software over-aggressively blocks or scans these components.ģ) Please ensure that you have selected YES when FSX asked to run as_btstrp.dll.