This is an ORBX problem.    

This is an ORBX problem.    Orbx is using the libraries in their dlls, and P3D is loading up the Orbx dlls.  That is why the error is reported as P3D.  The fix is still to install the library version mentioned above.

Is this the  the c++ runtime error "call to virtual function" or alike? If so no, as I don't have any addons on my pretty vanilla Win8.1. Any help, should I

try the first posting? My 8.1 is fully updated and surely has newer runtimes...

CyberMike, did you try to install the runtimes?  One thing I am sure of is it is not Prepar3d itself giving the error.  Do you have Any addon of any kind.  Is your P3d installed on a clean system, not in the same directory as a previous installation?   I am running 8.1.  I have seen this error, each time I do I had just "done something" like installed something.  The reason why I am sure it is not a Prepar3d error is if this was their error they would see it at compile time.  

 

At any rate, the "call to a virtual function" means that it somewhere in the P3D system, a 3rd party as I believe, there is a function call to the Microsoft C++ runtime library.  These libraries are updated often for security and performance reasons.  When they are updated they replace previous versions of functions just by using the same name, and then maybe adding a few arguments.  If you call a function and your library doesn't have the argument available you will get this error.  The answer is usually to make sure your files are not corrupt or missing, by reinstalling or installing the runtime libraries.  If a 3rd party dev is not using the same libraries on their machines as the core developer, or neither of the ship the library, you'll see this error.  But the primary developer isn't likely to be at fault as they will see the error when they try to make  build, but a 3rd party may be using an already built executable with the libraries they are calling available on their dev computers somewhere, which is why the 3rd party doesn't see the error, but they are creating it.  The real fix is for the 3rd party to send the library as well, and actually for neither of them to depend on the library being available on the clients system.  I suspect developers of FSX related products are using very "dirty" systems to develop with, as they're truly usually just "mom and pop" shops, and may have many other products on their systems, and acquired different versions of these libraries which fulfilled the need of any calls to any versions.  But when others load up their dlls if they don't have a "well seasoned" system, they won't have the version that has the arguments for the function that was called.

As expected, if I try to install the runtime from the first thread posting, it refuses by saying that a newer runtime is already installed. Previously to p3d, I only had visual studio 2012 installed and I don't want to break that...

I would uninstall and re install the libs.

No way, I remember wasting many hours with alike back on Vista.-

So LM are to stupid to use the latest c++ runtime?

Guys, I uninstalled and reinstalled the libraries several times and still had the error within minutes of beginning a flight. It was only when I ran a registry maintenance program with a new cfg and driver for the video card, did the problem go away. Not claiming this to be "the" solution, but it did work on my set-up.

TechguyMaxC,

 

I'm a little confused?

 

Are you saying, we need to have update 10.0.40219 installed (which I have) before upgrading to 10.0.40219.325 (version you get if you download from the link you just posted)? So those out there who are still at 30319, or some other vintage version, what are they supposed to do?

 

Are you also sure that the LM developers are at 40219.325 for the x86 and x64 versions?

 

Bill Clark

 

The downloads that are in the initial post are the "base" version that everyone needs to have installed before applying the patch in my last post.  I don't know what VC++ version the LM devs use on their computers, but the best guess is that it's the newest version which is publicly available.  Someone from the LM dev team would need to confirm.  Rob Ainscough (beta tester) may be able to find out for us.   

 

 

Guys, I uninstalled and reinstalled the libraries several times and still had the error within minutes of beginning a flight. It was only when I ran a registry maintenance program with a new cfg and driver for the video card, did the problem go away. Not claiming this to be "the" solution, but it did work on my set-up.

 

Another good route then.

 

All I know for the most certainty (I am not the kind that will tell you anything is 100%, you're lucky if you get a 90 out of me) - 86% - that this is not an LM issue. Some other module is causing it.  If I had the source I could probably reproduce the error and find it, that is what I get my cookies for.  What I would suggest is anyone with this error take note of where their P3D is installed, what card/driver, is it a clean windows, anything else anyone can think of. 

 

I am getting the error too.  But I am also having hiccups with the current nvidia/evga driver.  I have tessellation disabled, had just installed nvidia inspector and made a new profile in it.  I keep thinking it's Orbx because it's happening in Jackson Hole, one of the first sceneries to use a DLL asfaik, and it has not been updated.  But the only other differences are my own home grown perfectly innocent photoscenery, which I load in with scenery config editor.  It went away after a reload of the libs, but then I just HAD to play with NI, and it showed again.  I'm also getting OOM's for the first time now, LOL.  But 2.3 is the best yet.  And I'm thrilled that they've gotten this far without an actual NVidia profile.  They needed to clean up first. When we see that, Shazaam!  

 

The "registry fix" is something to take note of; that is where the information of what libs are installed is held, and maybe conflicts result if there are multiple entries?  Or locations not where they are expected.  

Sorry Orbx.  

OK, had a thought.

 

If LM doesn't load the runtime module before the third party, there might be a problem.  There's your sign!   If LM has an interface for a 3rd party and somehow a sequence is allowed where that 3rd party dll is getting loaded before the factory/interface is readied ... Kapoooww!!  A threading issue?  Handing things off to the GPU too quickly?   

( * gets out bataan, starts beating LM at the legs - )

Hi,

 

An update on my situation............I now have a bunch of Orbx stuff installed, but nothing else.

 

FTX Global

FTX Global Vector

FTX Global OpenLC Europe

Pilots - FS Global 2010

 

Now instead of getting R6025 errors, I have gotten two ntdll.dll crashes, within less than 20 minutes flying time with Tessellation turned off. When I have Tessellation on, it seems runs ok (I need to run again with these new add-ons). Possibly the choosing of Tessellation either on/off changes the order DLL's are loaded in P3D?

 

So is the issue now the library, or is it something else?

 

But it looks like the old issue of "DLL Hell" is back with us again. It might be safe to update my library to .385, but will I break something else? Right now my copy of FSX is running well so I feel I'm taking a chance of breaking something else that works (like PMDG 737 NGX in FSX)?

 

This is really frustrating!

Bill Clark

I'm hoping new nvida drivers helps, whenever they get them out.  I'm gonna say that Orbx is causing Nvidia driver problems .

I do not know how this post got pinned, but I'm unpinning it.  The OP is filled with erroneous information, like downloading a 64 bit version of the Microsoft Visuals?  P3D is a 32 bit application and the 64 bit version has nothing to do with P3D. 

 

The error was caused when running P3D and not QuickBooks or any other 32 bit application.  Therefore, it is a P3D addon problem (not a P3D.exe problem).

 

Unpinning. 

 

Best regards,

You install the 64bit runtime for 64bit Windows, regardless of the application.  Likewise, the ARM version if you are running Windows on a processor with an ARM based instruction set.   If you're running prepar3d on a 32bit system you probably have many more issues, unfortunately.    I did MFC development exclusively for more than a decade up until about 2006 (MCSD 2004, MFC/SQL).  Started with Borland OWL in the late 80's.  Now I do ASP.NET, although I have quite a few custom libs I use more often.   I know a little bit about these libraries and what's going on when they're running.

 

I think the idea the OP is trying to get across is that this runtime error is not exclusive to P3D, and trying to offer a fix.  I admit I don't know the fix to it myself, other than

 

DON'T OK THE ERROR MESSAGE BOX, lol,

 

But that's not a "Fix" like the title states, wish we had one.

 

 

I've also notice that without OKing the box, ground textures will go blurry.  AND the last time it happened was some old Chicago scenery I have that does not have DLLs.  Now my bug finder/pointer is pointing at somewhere in the scenery loading system.  I wish I had code to take a peak at.

 

If I get some more time I'm going to play around with adding/removing scenery, changing out scenery files, clearing shaders.  Last thing I'd want to do is change out the driver (latest WHQL with tess issue) because it might fix things, but I might not want to play around later.  If I have to I'm just going to do another clean install. ... I find that clean installs aren't so bad if I have something else to do while they are running about.  Multitasking makes it not seem so bad.

I'm with Jim on this one.  I received this error every flight when having tessellation off.  With tessellation on, no error.  This is on a fresh install of P3D v2.3, with NO addons.  I do not believe that this error is addon related.  I'm currently running with tessellation on in order to avoid the error.

 

Gerald