The download hangar is currently disabled. We're doing our best to bring it back as soon as possible.
RunTime Error Problem
RunTime Error Problem
Hi, after loading Robins AFB I took a hop around the base to see the scenery and about 10-15 minutes into the flight I ran into the infamous Microsoft RunTime Error message R6025. I install scenery from Altus ARB, took a hop to go sight-seeing it and about 10 minutes later again got the error message. I looked at YouTube for possible fixes and tried the one where you type at the command prompt...to no avail. I tried removing FSX's cfg file, launched FSX, launched a flight from Pensacola, "lived" for about 25-30 minutes before the error message returned. I thought it may be to much car, boat and ship traffic (I had the sliders at 35%). I set the sliders to 0%, loaded a flight from Pensacola, was in cockpit no more than 15 seconds... and got the Error message. I set the sliders back to 35% launch from Pensacola, "lived" for around 30 minutes before getting the messages again while on approach to Pensacola. I removed the trees and fence around the base, launched, flew around for 30 minutes, on approach to Pensacola got the error message again. I think I read somewhere in the forum that Runtime Errors are most likely caused by effects files. I did find 2 effects files for the F-16: fx_f16_ab_fx and fx_HTAI_f16_ab_FSX_fx. I am not sure these could be the cause. Any help and or suggestions would be greatly appreciated.
Re: RunTime Error Problem
If a *.fx file is the cause you would see visualfx.dll errors in your Windows Event viewer under Windows Logs - Application.
Re: RunTime Error Problem
The cause is not normally caused by scenery, as it is caused by an effect file.
The normal cause is that the effect file runs for 40-50 seconds and then ends. This is unacceptable for the game. The effect MUST run for the entire time, even if you do not see the effect. The normal effect file that will do this is a burner file, as this most often fits the criteria.
It is an effect on an AI aircraft. Normally the cause is that somebody uses an effect from a flyable aircraft on an AI aircraft without altering it to run permanently. The normal cause is an effect designed for a flyable aircraft that has not been modified for Ai use.
This would account for the different crashes at different times at different places. It is caused by an AI aircraft spawning within a certain distance of the base you are at, burners glow for the time period and then stop and that is when the crash happens.
I would think of any effects files that you personally have added to any aircraft that you have operating as AI, not just specialised AI models but anything you are running as AI.
If you are unable to think of what causes it then you have to work it out. In this case do the following :-
1. Create a holding folder on your desktop.
2. Count how many traffic files you have in your system, remembering that you may have traffic files in any active folder and not just in the normal \Scenery\World\scenery folder. (For example 120 files)
3. MOVE all of those traffic files to the holding folder on your desktop.
4. Run FS and go to a time and place that you know the crash happens and see what occurs.
If it doesn't crash you know that a traffic file that contains the troublesome aircraft If it does then you have confirmed that it is a scenery effect file - very rare but it can be.
Second Stage
5. Move the first 50% of traffic files back to \Scenery\World\scenery. ( For example the first 60 files)
6. Run FS and go to a time and place that you know the crash happens and see what occurs.
If it crashes you know that a traffic file that contains the troublesome aircraft is in that first 50%.
So you move back the last 50% from \Scenery\World\scenery back to the holding folder (For example 90 files in holding folder and 30 in S\W\S). Run FS again and monitor. According to the result you either move 50% again ( For example 15 files either from to to the holding file.
If it doesn't crash the problem traffic file is not in the first 50% so you transfer 50% of the remaining files from the holding file to S\W\S and re-test (For Example 30 files in holding and 90 in S\W|S).
The objective is to narrow it down to find the crash when you only move one file from the holding file to S\W\S. That is the traffic file that contains the problem aircraft.
I used 120 traffic files as an example but the principle is the same even if you have 1200 traffic files. By moving 50% each time is the most efficient and quickest way to discover the culprit.
There are other methods for finding the cause but this will work if you have no other tools or experience of using them.
The normal cause is that the effect file runs for 40-50 seconds and then ends. This is unacceptable for the game. The effect MUST run for the entire time, even if you do not see the effect. The normal effect file that will do this is a burner file, as this most often fits the criteria.
It is an effect on an AI aircraft. Normally the cause is that somebody uses an effect from a flyable aircraft on an AI aircraft without altering it to run permanently. The normal cause is an effect designed for a flyable aircraft that has not been modified for Ai use.
This would account for the different crashes at different times at different places. It is caused by an AI aircraft spawning within a certain distance of the base you are at, burners glow for the time period and then stop and that is when the crash happens.
I would think of any effects files that you personally have added to any aircraft that you have operating as AI, not just specialised AI models but anything you are running as AI.
If you are unable to think of what causes it then you have to work it out. In this case do the following :-
1. Create a holding folder on your desktop.
2. Count how many traffic files you have in your system, remembering that you may have traffic files in any active folder and not just in the normal \Scenery\World\scenery folder. (For example 120 files)
3. MOVE all of those traffic files to the holding folder on your desktop.
4. Run FS and go to a time and place that you know the crash happens and see what occurs.
If it doesn't crash you know that a traffic file that contains the troublesome aircraft If it does then you have confirmed that it is a scenery effect file - very rare but it can be.
Second Stage
5. Move the first 50% of traffic files back to \Scenery\World\scenery. ( For example the first 60 files)
6. Run FS and go to a time and place that you know the crash happens and see what occurs.
If it crashes you know that a traffic file that contains the troublesome aircraft is in that first 50%.
So you move back the last 50% from \Scenery\World\scenery back to the holding folder (For example 90 files in holding folder and 30 in S\W\S). Run FS again and monitor. According to the result you either move 50% again ( For example 15 files either from to to the holding file.
If it doesn't crash the problem traffic file is not in the first 50% so you transfer 50% of the remaining files from the holding file to S\W\S and re-test (For Example 30 files in holding and 90 in S\W|S).
The objective is to narrow it down to find the crash when you only move one file from the holding file to S\W\S. That is the traffic file that contains the problem aircraft.
I used 120 traffic files as an example but the principle is the same even if you have 1200 traffic files. By moving 50% each time is the most efficient and quickest way to discover the culprit.
There are other methods for finding the cause but this will work if you have no other tools or experience of using them.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: RunTime Error Problem
Hi, I will try moving the traffic files within the hour to see if I can locate the culprit aircraft. The error messages I got was as follows :
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:F:\Program Files(x86)\Microsoft Games\fsx.exe
R6025
-Pure Virtual Function Call
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:F:\Program Files(x86)\Microsoft Games\fsx.exe
R6025
-Pure Virtual Function Call
Re: RunTime Error Problem
Yes that is the error.
Let us know tour findings. It will undoubtedly help somebody else in the future.
Let us know tour findings. It will undoubtedly help somebody else in the future.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: RunTime Error Problem
Hi, after several hours swapping in and out various traffic files and hours test flying to see if I would get an error message or not, I narrowed it down to bases that are in the state of Florida and I have met with success !! It was the NAS Pensacola traffic file that was causing the error. I guess my next question would be, would a possible fix be to un-install the Pensacola package then re-install it, hoping that the good effects files will over-write the bad?
Re: RunTime Error Problem
Well that might work but only if it is a corrupt effects file, which I am not sure that it is.
You should try it though, if it is easy.
However, in case that doesn't work, which aircraft are in that problematic traffic file? You don't all individual titles just the different types. What I mean here is if there are two types but they are in the same folder then they count as one. the reason is that they use the same aircraft.cfg file and therefore use the same effects.
The reason that you have to follow it through, if it is not a corrupt file, is that you may put the problem effect into another aircraft at some point in the future and therefore get the problem back.
You should try it though, if it is easy.
However, in case that doesn't work, which aircraft are in that problematic traffic file? You don't all individual titles just the different types. What I mean here is if there are two types but they are in the same folder then they count as one. the reason is that they use the same aircraft.cfg file and therefore use the same effects.
The reason that you have to follow it through, if it is not a corrupt file, is that you may put the problem effect into another aircraft at some point in the future and therefore get the problem back.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: RunTime Error Problem
Hi, I looked at the Pensacola traffic file and it contains VT-86's T-45C's, the Blue Angels F-18C and D, and C-130H Fat Albert. As I have recently installed FSX and started installing MAIW Packages starting with east coast packages and then working my way west, I used the new and improved FSX aircraft packages that the company has been putting out. I put in the C-130 family, the T-45 family and the Hornet family. These new aircraft packages contain new effects files that I copied into FSX's effects folder. May I ask, do you think there maybe a conflict with the old fx files of the Pensacola package and the new FSX aircraft packages new fx ?
Re: RunTime Error Problem
There won't be a conflict. If they are the same name then one will replace the other.
If they don't have the same name then they will happily reside alongside each other. The aircraft.cfg will only call one of the effects.
i do remember there being an issue with a default effect file that needed to be altered. So i checked the T-45 conversion pack support thread and sure enough that is the problem. https://militaryaiworks.com/forums/82/1 ... sh#p186486.
If you read that you will see the cause of the crash and it has a link to the amended default effect file.
If you rename that default fx file in your system and download and install the new one I am willing to guess that your problem will no longer occur.
If they don't have the same name then they will happily reside alongside each other. The aircraft.cfg will only call one of the effects.
i do remember there being an issue with a default effect file that needed to be altered. So i checked the T-45 conversion pack support thread and sure enough that is the problem. https://militaryaiworks.com/forums/82/1 ... sh#p186486.
If you read that you will see the cause of the crash and it has a link to the amended default effect file.
If you rename that default fx file in your system and download and install the new one I am willing to guess that your problem will no longer occur.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
Re: RunTime Error Problem
Ok great, thanks for the info...seeing that I will be working the next few days I will not have any time to try the fix. I will report back Tuesday on my day off to let you know what happened.
Re: RunTime Error Problem
* Update* Hi, I downloaded the file, changed the name of the old file, put the Pensacola traffic file back into FSX, launched from Pensacola, flew for 30 minutes and....it works!!! No more Runtime Error messages!! I want to thank you for all your help and support you gave and the rest of the staff at MAIW and all others that contribute for all the fine work that you guys do.
Re: RunTime Error Problem
Thanks for this. I had been suffering from the R6025 Runtime Error recently as well. I'd chased it down to the Hawks, but I thought it was a texture/alpha problem.
Downloaded and installed the .fx file and everything works ok now.
Cheers
Derek
Downloaded and installed the .fx file and everything works ok now.
Cheers
Derek
Re: RunTime Error Problem
No problem guys.
Steve
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________
_______________________________________________________
Quid Si Coelum Ruat
_______________________________________________________