• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. dantaylor

    FreeMesh in P3D v4

    Similar issue here. Same scenery addons, their order is correct in my P3Dv4 as described in various manuals, websites, etc. For me disabling FreeMeshX didn't help, as the problem seems to be an issue with ORBX FTX Vector and FreeMeshX working together in the North American geographical region. This is what I learned on the ORBX support forum. I didn't notice any similar problems in other geopaphical regions. See my screenshots for an example, this happens at many North American airports though. Image 1 Image 2 Any advice on what to do? I'm using FreeMeshX 2.0. Best regards, Daniel
  2. Hi all, Thanks to your help I could pinpoint the error down to the dll.xml from the scenery.cfg folder (C:\ProgramData\Lockheed Martin\Prepar3D v4). The culprit was CMeteoXml (path: .\CMeteoXmlx64.dll). I googled the issue, and the result was that the cause has something to do with Carenado's weather radar. I don't really get the connection to why this error only happened flying around North America (and not even once in a Carenado aircraft), but I'm happy that it's now gone! My solution was to simply deactivate the entry in the aforementioned dll.xml, as there was no other solution I could find on the internet. So, @Jim Young, I followed your instructions step by step and did some extensive test flights inbetween to make sure I didn't miss anything. That's a very kind and generous offer, thank you! @B777ER, that's absolutely right. There are lots of resources out there, but there's nothing like personal assistance that allows you to systematically go though the debugging process while also learning something about the way the sim works. Without this help, I would have just tried some random options without actually knowing what I was doing. These forums actually remind me a lot of the comradery I value so much from the "real" world of aviation, me being a GA pilot. So, thank you very much again, now I can actually start flying in P3D for the first time (I was just done with all of the installations as this error occured). Best regards, Daniel
  3. Hi Jim and Simbol, Thanks for your quick and detailed answers and instructions. I’ll go through your to-do lists tomorrow in the morning (German time) right away and let you know about the results.
  4. Sorry for not posting in the CTD sub-forum. I'm a noob.
  5. Dear all, I am experiencing a very weird and frustrating CTD phenomenon in P3Dv4: If I start the sim at the default airport with the default plane (F22), it crashes after 1-3min of flying around. Leaving the plane on the runway without any movement does not crash it. Taking off from the default airport (Eglin AFB) in a different plane also causes the crash to happen, most of the time slightly later than in the previous set up. Sometimes I get a Windows error message telling me that P3D has stopped working, but in most cases the simulator simply freezes and exits directly a few seconds later. Now comes the weird part: I can fly around in other areas (e.g. Europe, Pacific NW, New York, etc.) and there will be no problem at all in some cases. To narrow down the problem, I loaded a flight from Destin/Fort Walton Beach Airport (geographically located near the P3D default airport Eglin AFB in FL), this also caused the crash to happen. I referred to the Avsim CTD guide for some tips. At first, I received error logs (in dxdiag.txt) pointing to kernelbase.dll and facilities.dll as the culprits. Another issue that does not neccesarily make the whole process easier, is that the program AppCrashView does not detect and log every P3D crash for some reason. I tried some tips from the CTD manual and this forum, which included installing an older version of my graphics card driver and running Windows Repair from tweaking.com. The result was that the same crashes occur, but with the error logs additionally pointing to atc.dll now in some cases. For addons, I am running ORBX FTX Global, Vector, Trees, OpenLC Europe, Germany North, Germany South; ASCA, AS16, ENVTEX, PTA with the THOPAT preset, FreeMeshX, a number of European airports and various planes (e.g. PMDG 777, 747; AS/DD CRJ, A2A C172). I am not 100% sure when this issue started, because I performed most of my post-addon test flights in Europe due to the scenery installed. ASCA, AS16 and ENVTEX were installed last. Loading various PTA presets did not seem to cause the problem (I did some test flights around the default airport at that time). Apart from reinstalling the graphics card driver and running Windows Repair I have performed the following actions: Uninstalled and reinstalled MS Visual C++ Uninstalled and reinstalled ASCA, AS16, PTA and ENVTEX Disabled all of the add-on sceneries Uninstalled FSUIPC Uninstalled add-ons that showed errors in P3D's content error log None of this has proven to be effective. At this point I am quite frustrated. Crashes also occour in other scenery areas (althoug much less often and not as fast as in the default scenario). I could now blast you with a list of my PC specs and all add-ons. To not make this post too long to read, I will only include the most recent crash log from AppCrashView and a dxdiag log. Of course I will provide you with all other the information that is necessary ASAP. But please let me know what exactly is required, because I don't just want to take a random guess. I apologise for my system language as shown in the logs for being German. I hope you can find all the relevant information anyway, as the logs are standardised. Here is the most recent log from AppCrashView: dxdiag.txt contents from a previous crash pointing to atc.dll (the aforementioned one was not logged in dxdiag.txt): Your help is greatly appreciated. As mentioned above, if you require any additional information, just let me know and I will provide it as quickly as possible! Please let me know what the next steps could be in resolving this issue. I hope that I do not have to go for a P3D or Windows reinstall. Best regards, Daniel