Facts about R6025 errors

[Dstevenb 0]

A-ha! I completed 3 tests each over 3 hours with no R6025 error. I then proceeded to the next level and installed ORBX global. Bang 10 minutes into flight the dreaded error again. I dropped video settings and am now approaching 1 hour fault free.

 

Jim. How do the scenery settings have any bearing on a function call? I dont get why that would have any bearing on the sim.

[Jim Young 2,356]

 

 

Jim. How do the scenery settings have any bearing on a function call? I dont get why that would have any bearing on the sim.

 

You are removing some of the strain on your system to render something when called by a program.  I think now it could be an older program made for FSX or even FS9 that is having problems communicating correctly with P3D.  By lowering the settings, it is giving that older program time to render a call.  I had to seriously look at my system when I started getting them in 2.4.  I saw that not everyone was getting the 6025 error.  It was not happening on a clean install of P3D w/o addons and my settings relatively low.  I think the only addon I installed was MyTrafficX and the program was never made for P3D (yes it works with it but not set up in the way the developer would have set it up for P3D). 

 

I hope you continue to have error free flights.  So far, in 2.5, I have not seen the error and I had my settings up really high at the beginning to test it out.  I still say it's an addon.  What the common denominator is for everyone is yet to be found.  The fact that you do not see the error with tessellation turn on and you dropping the video card settings, is an indication this is probably video card related.  Again, not everyone is getting this error, just a select few.

 

Best regards,

[Dstevenb 0]

Thanks for your (and this board's) help in getting me error free flights. Lowering the settings seems to have done the trick, although having forked out some serious cash for a 4GB 770 card doesn't fill me with awe that everyone is quite on the ball with correct implementation. I would understand the headache if I was running a €20 card, but not one that cost €500.

 

At any rate, the error goes with low settings. I can live with that.

[Dstevenb 0]

Uh-oh. I completed successful tests with ORBX Global Base. I then went to the next step of adding Austrralia and England regions. Once again the R6025 is back. This time worse than before. If I turn all settings to their lowest I get no error, but in 2.5 I also get no airports buildings, trees or any other buildings. I don't see the motivation to shovel money to LM for that type of performance, whether it is or isn't their fault.

 

However an Inno 770 nvidia 4Gb card should _not_ be insisting on such pathetic settings. A half months wages makes me expect it works as advertised. If I want terrible graphics I'll go to MSFS95. I cannot live with that.

 

Sorry but my frustrations are getting the better of me. I am getting fed up with every step forward equalling two steps backwards. Nothing on my hex-core system says I should be even considering a non-performing flight sim.

 

What can I do?

[stook2005 7]

Did you try flying an Orbx region without installing FTX Global Base?

[Dstevenb 0]

No not yet. I am very much considering jumping back to P3Dv1.4 as I can't stand this error. Simming is no fun. If P1.4 starts playing up I'll go back to FSX and seriously consider pumping my cash in X-plane. For LM and ORBX, and any other developer I can say that I have stopped buying any add ons No point buying flashy tires if the car won't start.

[Jim Young 2,356]

 

 

For LM and ORBX, and any other developer I can say that I have stopped buying any add ons No point buying flashy tires if the car won't start.

 

I can agree with your quote.  Always frustrating when we get sudden unexplainable crashes.  I got this error in v2.4 but resolved my problem by having P3D ask me if I really want to shutdown P3D as I was getting the error 100% of the time at shutdown.  One of my addons, not sure which was not shutting down properly when I shutdown P3D.  I got it once or twice during a flight too but think those were related to LOD_Radius set at 6.5.  One of my addons, don't know which, was not able to render at that LOD.  Moved the slider back to 4.5 and the problems when away (or I never saw them again).  P3D is not like other games where you can turn the sliders up to max and expect no issues every time you play.  There are some old addons that some say are compatible with P3D (via the migration tool), and they install okay but they really are not really for prime time and P3D.  I would not install an addon into P3D unless you know it is 100% compatible with P3D and the developer has developed a new installer.  P3D uses Microsoft Visual C++ 2010.  Most FSX addons that are imported to P3D use Microsoft Visual 2008 w/SP1 and some really older apps use the 2005 w/SP1 version.  Microsoft Visuals are not backward compatible for the most part.  This has been proven over and over when LM issues and update or hotfix.  Suddenly, the addon developer has to modify his installer and Microsoft Visual so it will be compatible.  If everyone was getting this crash, I would say there is a problem with LM's P3D.  But not everyone is getting this crash so we have to look at how the product was installed, your settings, and the addons.  Maybe you aren't sharing the P3D Folder or you do not have complete ownership of the folders.  Just so many causes.

 

Best regards,

[Dstevenb 0]

I am about to instal FSX again. If that doesn't crash then it is bye bye Prepar3d.

[Dstevenb 0]

I may have found a solution to this problem. I am just testing my theory right now.

[Dstevenb 0]

Following 2 days of full-on testing, I think I have found the solution to my problem (and also all of those who have the R-6025 error that is present with a vanilla install and only having approved add-ons. So what did I do?

 

I first got so damned sick and tired of the same CTD after 15-30 minutes flight that I was ready to ditch P3D (as you can read a few posts up). However, I decided to test FSX before I ditched P3D, so I did a new install of FSX. No addons, just vanilla. It work flawlessly as I knew it would. Being, however a stubbon old xyz, as LM support forum moderators will gladly tell you, I decided to one last time test to P3Dv2.5. And what do you know?

 

BINGO! P3D suddenly works perflectly. NO R-6025 error!!??

 

As of today 2 test flights over 5 hours each no R-60256 errors.

 

Now, I would love to know WHY?

 

PS: As I pay for a developer P3D license I'd would like this fix to be known as the "Dwight Fix" - no charge for it.