R6025 is either caused by a faulty add-on or a faulty installation of .Net Framerwork or the Visual C++ libraries.

 

I've written down the procedure I've used for renewing said libraries here:

http://forum.avsim.net/topic/459387-fsxse-terraing3ddll-related-crashes/?p=3156267

I've had both the terrain.dll and g3d.dll crashes in steam, but in over 50 hours of flying with SE, have never seen the R6025 error. I agree with Bjoern that the pure virtual function error is most likely caused by a C++ or .Net library problem, or an issue with an add-on, rather than being something inherently wrong with FSX-SE itself.

 

 

R6025 CTD possible causing by wrong coding of STEAM FSX software.

 

What coding.  The only "coding" if you want to call it coding was changing the Microsoft Visual used for installing the program.  Instead of using the one used for FSX (Microsoft Visual C++2005), they used Microsoft Visual C++ 2010.  Since FSX is an old program, you should also have Microsoft Visual C++2005 and 2008 installed.  I would also recommend Microsoft.net 2.0 as Microsoft.net's are not, for the most part, backward compatible.  FSX used Microsoft.net 1.1 which was updated to 2.0 and proper dotnets are needed to run your application properly.

 

Best regards,

I had posted earlier that I had not seen this R6025 Error to date in my SE flights, but somewhere along the lines, that post thanking Ahmet for pointing me to what this R6025-related CTDs were, disappeared.

Rick,

 

If I can be help full, it will make my day.

Rick,

 

If I can be help full, it will make my day.

 

Ahmet

 

You have already been helpful. I saw your screenshot. I do not get that error. I was trying to thank you soon after I saw your post but it got deleted.

 

 

Thanks.

Personally I have dropped the steam version ( Just for now ). Dovetail and Steam are the future of this hobby! I had MSFSX GOLD installed on a separate hard drive but when I purchased the Steam Edition and installed it on my regular drive C: it somehow interacted with my old version in drive D: and not in the let me help you out kind of way!  For now I have MSFSX running just the way I like. It would have been better if Dovetail had said for a $5 fee you can help us beta test the product rather than releasing it as a product. It would also have been nice before they released it to have called on the community that has kept it alive for so long. I don't mind beta testing and I would have paid to do it, but if I had known this in advance, I would have installed the Steam Edition into a separate computer. 

I had to reinstall MSFSX and start over. Not too cool!

Rick,

 

R6025 CTD possible causing by  wrong coding of  STEAM  FSX software. No one knows how to solve this problem, including the STEAM. There are many members are suffering  from this problem.

 

http://imageshack.com/a/img538/6899/dXOL0r.jpg

So why are only select people getting this error?

So why are only select people getting this error?

Just a few are getting the error in P3D too (including me).  Many have fixed their error there by disabling tessellation which is part of the graphics.  I get rid of the error by enabling "Prompt on Exit" when I shutdown P3D.  It's a bad code somewhere but I believe it is in the display driver or an addon.

 

Best regards,

 

 

Many have fixed their error there by disabling tessellation which is part of the graphics. 

Jim, you meant that many have fixed the error by enabling tessellation right?  That what I have to do to make the problem go away.  This runtime error is likely cause by third party add-on that was built against older runtime libraries.  Newer runtime forces the code implementing the virtual function to do so differently and when it does not, the runtime library crashes.  FSX-SE has been recompiled using newer compiler, hence the issue shows up, just like P3Dv2 is built using newer compiler.

 

 

Jim, you meant that many have fixed the error by enabling tessellation right?

 

That would not fix it for me (whether enabling/disabling).  Mine crash only occurred at shutdown.  I agree with the rest of your assessment.  Probably something to do with the Microsoft Visual setup used for installing the products.

 

Best regards,

This sim, FSX-SE, is determined to snare us at every which way. If it is not the dreaded terrain.dll, it's the G3d.dll. If not that, then how about the latest after installing FSDT airports----bglmanx.dll---and that, occurred just as about to ask for push-back via GSX at FSDT's Zurich airport.

 

55 minutes just totally wasted. I ask myself, is this hobby really worth it.

I would assume that DTG is aware of these bugs.

 

If you read the latest news on the Active Sky Next page, you will be able to  confirm that the developers of ASN has had some stability issues with FSX-SE also.

 

I don't think there's much we can really do about the .dll errors until DTG uploads a fix for the issue, which I'm sure that they will do. For now long haul flights on the new simulator are all but impossible for most people, but after these issues are sorted out this will be a very solid simulation.

Long haul flights are mostly impossible for FSX and P3DV2 users too. Depends on the scenario. People are just turning up their overclocks and config settings too high. Hope Dovetail fixes your problems.

 

Best regards,