OT Runtime Error...HELP!

Duckie

Duckie

SOH-CM-2024
Still in the rebuilding process for FSX with my new PC and just started getting this Runtime Error!

attachment.php


I've verified no file system errors, all visual C++ versions are up to date, all .Net editions are correct and up to date. I've read where fx_xxx files in the [LIGHTS] section of AI config is probably the culprit. I've loaded tons of AI, all FSX versions, NO FS9 AI. I'm in the process of disabling all AI effects calls except for actual "lights".

What's the conventional wisdom in this regard? (my system specs are in my sig)

Thanks

Steve
 

Attachments

  • -2020-oct-5-002.jpg
    -2020-oct-5-002.jpg
    24 KB · Views: 73
Priller said:
Hi Duckie,

Try this one: https://docs.microsoft.com/en-us/cpp/error-messages/tool-errors/c-runtime-error-r6025?view=vs-2019

So, in short, first run windows update, and force every update you can. it might even be so that there are already several updates waiting to be installed. Do that first and we'll take it from there.

It's a known error!

Jan
Click to expand...

Thanks Jan. Sorry I did not mention it but that was the first thing I did. Just checked again and Windows is up to date. Nothing in queue.

Steve
 
The try to go to the control panel, programs and features and do a repair of FSX.

Standing by!

Jan
 
Not joy on getting it to boot. Reinstall here I come. 1st time I've ever had to do it after initial install.
 
[FONT=&quot]Finally found time to do some testing of the “Run Time Error! …FSX.exe R6025 – pure virtual function call” and the fixes proposed from others on other forums. This specific error only involves 3[SUP]rd[/SUP] Party AI. It first started appearing after I had added several 3rd party AI addons along with traffic for each (I did not know that at the time it was occurring). The error would occur after 10-20 minutes (sometimes less than 10 minutes but never more than 20 minutes) of flight and not necessarily over the airfields these 3rd party AI were assigned.[/FONT]
[FONT=&quot]After spending a good bit of time researching online I came across information regarding this problem. The earliest post I found dated back to 2014. The latest post was 2017. There may be others. These are just the ones I found. [/FONT]
[FONT=&quot]According to those sources the problem lies within 3rd party AI config files, lights section, special effects other than lighting assigned to a lights function. That said, seems no one has been able to determine which effect is the offender or if there is more than one. [/FONT]
[FONT=&quot]At least one source recommends one of two possible resolutions to eliminate the error: [/FONT]
[FONT=&quot]1. Disable all AI traffic; or [/FONT]
[FONT=&quot]2. Disable all special effects assigned to lights (smoke, after burner, supersonic bloom, etc.).[/FONT]
[FONT=&quot]I now have done limited testing with each of these recommended solutions and can report that, for me, they appear to work.[/FONT]
[FONT=&quot]Testing both solutions involved flying for approx 1 hour, single session, hot switching between airports[/FONT]
[FONT=&quot]1. AI Disabled (0%) - No errors appeared. Session was uninterrupted.[/FONT]
[FONT=&quot]2. Special Effects disabled in AI config Lights section. No lights were disabled. AI Traffic set to 41%. No errors appeared. Session was uninterrupted.[/FONT]
[FONT=&quot]Note: This error never occurred on my old system (Win7 – 64 Home) and I flew FSX approx 7 years. I had essentially the same AI installed; however, they were mostly FS9 models. The error only began occurring on my new Windows 10 system (specs in my sig) after installing the newer FSX models of the same AI. [/FONT]
[FONT=&quot]Obviously this error is not all that common but it does occur. Hopefully this will help in the future for anyone still on FSX if it happens to them.[/FONT]
[FONT=&quot] [/FONT]
[FONT=&quot]Steve[/FONT]
 
You must log in or register to reply here.
Back
Top