This will prove once again that "anything" can cause this error (Runtime Error 6025) to occur. For over a week now I have racked my brain (at least what is still remaining) trying to find the addon that is causing the constant errors. It had gotten so bad that I couldn't even get the gear completely up before I would get the error. I removed everything that wasn't specifically P3D related. All FSX native aircraft and the few custom sceneries that I had loaded and I was still getting the error although not as quickly as before. I finally did a search of all threads on the LM Forums for any mention of the runtime error problem and got page after page after page. It's a widely found problem. Every individual was getting the problem from what seemed like a different scenario. Some were scenery related, some were addon aircraft related, some were a combination of both. . .but one individual gave a different opinion. He had turned off "tessellation", then realized later that he had started having problems some time after he did that. He went back, turned it on and has had no problems since. I had also been using tessellation but during a TS discussion with an SOH member it was suggested that I turn that off (don't remember the exact reason now). Anyway, I went back last evening, turned it back on, restarted the sim and haven't had a single error pop-up since.
Now according the experts at LM, the cause for this error is that there is a function call that is incompatible with P3D, caused by either an incompatible scenery or aircraft. But based on what I found, and what others have found works for them. . .it is that and many other things as well. It's why this particular error has been so difficult to pinpoint and correct. Just something that you can take a look at if you are also being plagued by this elusive error message.
Now according the experts at LM, the cause for this error is that there is a function call that is incompatible with P3D, caused by either an incompatible scenery or aircraft. But based on what I found, and what others have found works for them. . .it is that and many other things as well. It's why this particular error has been so difficult to pinpoint and correct. Just something that you can take a look at if you are also being plagued by this elusive error message.
