Hi all, I was attempting a TXKF to KHYA flight and recived this error, Any ideas? Thanks in advance from Jim :-) http://forums.avsim.net/user_files/129369.jpg

WOWJimCYWG

This has happened to me on every flight I have taken from Europe to the Carribean from TXKF-KMIA all of these flights have resulted in the Error message. I thought maybe it was specific to me so I just uninstalled and have been hoping for the best.PMDG 747 EHAM-TNCM errorLDS 767 CDG-KMIA errorDF Baron TXKF-KMIA error By the way the airline flights were on two different computers.

Guys,In the readme file for version 1.3 of the Freeflow Bermuda package that was released recently, there was a mention of this exact error message.I understand the precise cause has not been established but there are some things to try.It is caused by the AI ships so (a sledgehammer approach) disabling them will stop the error.It has been reported that either the Ferries or the Utility ships are causing it. You could try disabling one of these (using the config tool (in the bin directory)) and finding out which one it is on your system.Hope this helps,Ian

Thank's Ian,I should have read the Doc's}(

there are a few problems with the AI that is installed. For one, if you have both the FF Florida and Bermuda, you get duplicate cargo ships. Second, some of the ai has no ui_variation, type, etc in the aircraft.cfg file. And the sail ship's aircraft.cfg file is named .xxx ??Anyway if you have an addon program that scans your ai traffic for errors such as ACA2005, run that and it will show you what to fix

And here I thought the error was because with FFBermuda installed, the experience is so real it became to much for the computer to handle.Thomas

Here's the story- I'll post it all so maybe someone can help us out, though I think this might be one of those unsolved mysteries...A search in this and any other major FS forums for "R6025" will yeild many hits - it's not a FREEflow Bermuda specific problem. Almost all of the reported crashes are related to AI traffic - both aircraft and ships - or AFCADs.First, the fix:For us, we've had about a dozen folks report this specific CTD (not bad considering 10,000 downloads). For 10 of them, the fix is to inactivate the AI utility ships (garbage barge). This can be done easily via the configuration application which is installed with the scenery - simply uncheck "utility ships" if you have the AI active. The static models of the same ship does not cause the CTD. For the others, inactivating the AI ferries solved the CTD. It is possible to disable our AI ships entirely should that be necessary...again, all of this can be accomplished with the configuration application - there's a shortcut on the start menu, or the exe can be found in FREEflow BermudabinThe background:The R6025 crash for us is a very strange one - It requires departure from TXKF, a high cruising altitude ( >FL200), and occurs about 80-100nm from TXKF. I speculate that this is when the AI is being UNLOADED from memory. These are very specific conditions, and most people are not affected at all - in fact only one of our group can duplicate the CTD.Searching the forums and MSDN library for references, a lot of technical information is available - but nothing offering a solution for this particular crash in FS2004. A "R6025 Pure Virtual function call" is a program error usually caused by a programming bug that results in an infinite loop. With respect to some of the reports in FS9, that loop seems to be interpreted as a timeout after a request for data via a network, much like a 404 error. In fact, in this specific case with our Bermuda scenery, the error can be avoided completely by NOT being connected to the internet - disconnect your modem, and there is no CTD departing TXKF - this has been confirmed. Why our AI causes this behavior is beyond me, but I'll discuss some of the details regarding the AI here, maybe someone will have some ideas...Our FREEflow Bermuda AI:The models of the ships that are responsible for the CTD are done by Ron Jeffers in FSDS. They are non-AI ships, converted to AI by several edits in the .air and aircraft.cfg files. JoeW and Ron could give us some more specifics if anyone thinks this might be a source of the problem.To address Big Al's comments:The cargo ships installed by FREEflow Bermuda are the same as those installed by the FREEflow Florida AI. The folder that this ship model is installed to is named differently (mostly because I had some issues coding the config app and I had trouble with folder names with spaces and underscores), so if you have both sets of AI installed, you will have duplicate cargo ships. It should be noted, the duplication does not seem to have any ill effects in FS9 - We have tested that. You can also safely remove the cargo ships installed by the florida package and the bermuda models will be used in florida instead - same paints so no problems.The configuration application can be used to selectively inactivate certain ships - this is accomplished simply by renaming the aircraft.cfg to aircraft.xxx. Again, this works for FS9, but will result in programs like ACA2005 reporting a missing aircraft, or misnamed aircraft.cfg. As far as I know, if FS has a flight plan, but can't find the aircraft.cfg for the AI, it just ignores it. Again, the problem here occurs when the ships are ACTIVE, so this should not be the cause or even related to the CTD.Conclusion:For a select few lucky FREEflow Bermuda customers, one or more of our AI ships will cause a CTD when departing TXKF at high altitude about 80-100nm away from the airport. Inactivating the AI ships, or specifically one of the ships listed above, will prevent the CTD. Also, disconnecting from the internet should prevent the CTD.We would love to know if anyone has any ideas why our AI is causing this CTD.Thanks!sg