OkI have tried the following"You can completely eliminate AS from the mix by doing this: First load a normal flight with ASv6... start the flight and save it after a while (maybe after 2 hours if you normally get crashes after that point). Then reboot everything, don't load ASv6, and load/continue your flight. The weather situation will be in exact FS-controlled format which COULD in fact be re-created manually or via real weather downloads (eliminating any possibility that the wx data format provided by AS is bad). You will "almost certainly" experience the same CTD situation."I did not have a ctd. ended finebut on the other hand other testing has also had me complete flights with ASkyso Im left without a consistent resultwhat else is new LOLMike

Hi Mike,Are you flying the same route each time?Any AFCADs on your ayatem?Hope this helps,Jimhttp://www.hifisim.com/Active Sky V6 Development TeamActive Sky V6 Proud SupporterHiFi Beta TeamRadar Contact Supporter

I have been testing with the same route, for the most partAFCAD?Mike

Hi Mike,That is indeed strange.It says to me that the problem must be with a memory leak situtation that gets progressively worse as the flight session goes on.Memory leaks are common with bad scenery files including landclass info. AI add-ons use AFCAD (for airport/parking/taxiway information) and this can also be problematic. I believe there is one documented problem where missing or corrupt textures (scenery OR AI add-ons) can cause such a condition.The next step for isolation would be to remove any/all scenery/AI add-ons...Beyond that, you could also try the same saved flight scenario but this time save it before actual departure, to see if the route being flown (or time of session) has anything to do with it.Feel free to email me directly at [email protected] for direct troubleshooting. I believe at this time all current CTD reports have been solved with the exception of this one. We fixed 5 already this month (all bad scenery add-ons).Best,

FWIW, I recently had a new "Out of Memory" CTD while over the middle of the Atlantic with ASv6 Update3 feeding across my WideFS connection with the latest FSUIPC beta 3.538 after about three hours of flight. Since I had been doing a lot with the latest FSUIPC beta and axis configurations, I happened to notice that in my WideServer.log file I had repeated connecitons being created and dropped right up until the time of CTD. To make a long story short, I had recently installed McAffee Personal firewall Plus which is now free to us Comcast Broadband customers and had it properly configured for all ports related to Flightsim and addon-ons. All indications was that WideClient always connected fine but then I noticed that ASv6 was updating FlightSim stations rather slowely, sometimes stalling on a single station update for around five seconds.After removing McAfee firewall from the WideClient PC, unchecking the Quality of Service (QOS) protocal on both machines and settig the NIC's from "full autonegotiate" to "autonegotiate 100MB Full Duplex", I have not had one dropped connection in my WideServer.log file and no more CTD's. The point here is, check all your log files. In this case, poor network connections was killing FS and never gave any inidcation of irregular RAM or swap file usage. Pete Dowson also helped me narrow down this problem for which I'm grateful.v/r,Al

Thanks for the offerI am going to try and get a better hold on exactly what is happening and then contact youMike