Runtime Error "6025"

[falcon409]

Just suddenly started getting this error again, although I'm not sure it's the same as the one I was getting back with V2.0. I spent all morning trying to whittle away at the possible causes. . .Addon Aircraft. . .Addon Scenery. . .Scenery Object Libraries. It doesn't appear that it was an aircraft as even after all were moved out leaving only default I still had the error. Next was scenery, that, in and of itself appears not to have been the culprit either as I took the sim down to nothing more than default. . .still got the error. Finally removed the 8 or 9 scenery object folders from the scenery library and the error disappeared. After that another problem arose and I finally ran the "Repair" utility and have had to more or less start over from scratch. Just a HU that errors can come from any direction, especially those you find the most improbable.

[luckydog]

Same here....quite some time ago. Finally gave up and went back to 1.4.......

[Daube]

Have you tried updating the C++ runtimes on your computer ?

[falcon409]

Have you tried updating the C++ runtimes on your computer ?

Yep, did that with no change, I finally ran the "Repair" program for V2.2 which took over 30 minutes to complete. When it finished, I rebooted and tried to load V2.2 and got an immediate CTD. Finally removed the Prepar3D.cfg file, dll.xml and exe.xml files and it finally allowed me to reload the sim. So basically I started over from scratch. Pretty irritating because although it "appears" that something in one of the object libraries was the cause, I can't be 100% sure. Gauging from the LM Forums, there can be any number of causes for Runtime errors which makes this particular error difficult to troubleshoot.

Also, this "seemed" to start only after installing Orbx Regions in the PNW Area as well as the individual airports I had purchased for that part of the US. However, even after completely uninstalling everything Orbx related, the problem persisted so I can't say positively that it was the original cause, could just be coincidence. Anyway, V2.2 is back albeit in a stripped down version. Now I'll start adding scenery back in, one at a time and hope for the best.

[Daube]

It was surely due to one of the entries in the exe.xml or dll.xml...
I had to delete one of these recently... I believe it was for TacPack. Fortunately, I had renamed the files instead of deleting them, so I could retrieve them later on, and clean them step by step...

[falcon409]

It was surely due to one of the entries in the exe.xml or dll.xml...
I had to delete one of these recently... I believe it was for TacPack. Fortunately, I had renamed the files instead of deleting them, so I could retrieve them later on, and clean them step by step...

Not too sure about that Daube because those two had not changed in a long time and V2.2 was running fine. However, Orbx did add some info to the dll.xml file concerning their "Free Flow" module and I removed that as a precaution. Reloaded the sim and the problem persisted. The only other entries I have in that file are for FSUIPC and FSTramp which have also been in that file for a long time with no problems. I did remove the exe.xml file though as the only entry there was for REX Weather which I don't use, but when it would try to load at the beginning of a session I would just turn it off.

[roger-wilco-66]

Just FYI, there is a known condition like that which is reported in the LM p3d forum:

http://www.prepar3d.com/forum-5/?min...ewtopic&t=4737

and

http://www.prepar3d.com/forum-5/?min...topic&t=4734.0

The information is a bit confusing at this time though.

Cheers,
Mark

[falcon409]

Just FYI, there is a known condition like that which is reported in the LM p3d forum:

http://www.prepar3d.com/forum-5/?min...ewtopic&t=4737

and

http://www.prepar3d.com/forum-5/?min...topic&t=4734.0

The information is a bit confusing at this time though.

Cheers,
Mark

That's the problem I had with my predicament Mark, I didn't find any one thing/cause for the error message. Seemed every person who was getting the 6025 error was getting it for a different reason. Pretty hard to pinpoint it when that's the case. I tried to be systematic about the way I went about looking for the cause but in the end, I can't really say that the scenery objects (which were active in the Scenery Library but not being used by any scenery) were the root cause. All I know is that by going back to the grass roots P3D_V2.2, base scenery and only payware FSX/P3D aircraft I no longer have the problem and it would have shown itself by now because it would hit only a few minutes into my flights and I've been flying all over New York State and New Jersey without a hiccup.

[WND]

Ed, remember that old saying: "It's the operator" !!!!! (as I'm rolling on the floor laughing !)