Jump to content

Search the Community

Showing results for tags 'ctd'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements
    • Orbx Release Announcements
    • Orbx Preview Announcements, Screenshots and Videos
    • Orbx Company Updates
    • Partner Previews and Announcements
  • Public
    • Orbx Product Reviews
    • General Discussion
    • Aerofly FS2
    • Community Screenshots
    • Community Videos
    • Hardware and Tech Talk
  • Legacy Support Forums [Read-only]
    • Microsoft Flight Simulator Support Forum
    • PREPAR3D® V5.x Support Forum
    • PREPAR3D® V4.x Support Forum
    • PREPAR3D® V3.x Support Forum
    • FSX Support Forum
    • FSX Steam Edition Support Forum
    • X-Plane 11 Support Forum
    • IPACS Aerofly FS 2 Support Forum
    • Orbx Central Support Forum
    • Orbx Global Vector Support
    • Orbx Global openLC Support
    • Orbx Freeware Support Forum
  • Partners
    • Orbx Partners Support


  • Community Calendar
  • Flight Calendar

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Transaction ID

Facebook Profile

  1. As the title says, Configuring the no 3d grass, no ortho and no statics configuration for DD UUEE v2 in Orbx Central Beaks the scenery; and XP11 WILL NOT RUN. 1. It initially says it's missing grass.png from the 'vegetation' folder and CTD's. So I manually copied that one file from the 'vegetation_grass' folder to the 'vegetation' folder, as requested. I then opened Orbx Central and ran the 'Verify Files' option for the scenery package, and... 2. After restarting X-Plane it then reported that... "The following scenery package has a problem and will therefore nopt be loaded: Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/ It requires an additional library scenery package that is not installed, or it is missing some of it's files." From the log file... 0:01:28.034 E/SCN: Failed to find resource 'vegetation/forest_mix_full.for', referenced from scenery package 'Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/'. 0:01:28.034 E/SCN: Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/Earth nav data/+50+030/+55+037.dsf: 0:01:28.034 E/SCN: The art asset 'vegetation/forest_mix_full.for' could not be found. 0:01:28.034 E/SCN: DSF canceled due to missing art assets, file=Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/Earth nav data/+50+030/+55+037.dsf, err=15 (dsf_ErrCanceled). 0:01:28.034 E/SCN: WARNING: got error on DSF load for scenery file 55, 37, Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/ 0:01:28.034 E/SYS: MACIBM_alert: The following scenery package has a problem and will therefore not be loaded: 0:01:28.034 E/SYS: MACIBM_alert: Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/ 0:01:28.034 E/SYS: MACIBM_alert: It requires an additional library scenery package that is not installed, or it is missing some of its files. 0:01:28.034 E/SYS: MACIBM_alert: http://lookup.x-plane.com/_lookup_11_/missing_custom_scenery.html 0:01:28.034 E/SYS: MACIBM_alert: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/REN/io_dsf.cpp:886 0:01:28.034 E/SYS: +------------------------------------------------------------------------------- 0:01:28.034 E/SYS: | The following scenery package has a problem and will therefore not be loaded: 0:01:28.034 E/SYS: | Custom Scenery/DD_UUEE_Moscow_Sheremetyevo_XP_V2/ 0:01:28.034 E/SYS: | It requires an additional library scenery package that is not installed, or it is missing some of its files. 0:01:28.034 E/SYS: | http://lookup.x-plane.com/_lookup_11_/missing_custom_scenery.html 0:01:28.034 E/SYS: | (io_dsf.cpp:886) 0:01:28.034 E/SYS: +------------------------------------------------------------------------------- It then loaded X-Plane... but no DD UUEE V2 scenery Part of the issue might be that there's a BUG in the control panel.xml <name>Without volumetric grass.</name> -<files> -<file directory="true"> <onpath>DD_UUEE_Moscow_Sheremetyevo_XP_V2\vegetation</onpath> <offpath>DD_UUEE_Moscow_Sheremetyevo_XP_V2\vegetation_nograss</offpath> </file> </files> I.E. THERE IS NO "vegetation_nograss" FOLDER IN THE SCENERY PACKAGE!
  2. I have been banging my head against the preverbial brick wall ever since the SU5 update - crashes to desktop (CTD) led me to search for sim stability only for the situation to get worse. I did everything suggested bar make a burnt offereings! I renamed the community folder, I deleted content.xml, deleted rolling cache, deleted scenery.dat files, I re-enabled rolling cache, I added comunity folders one at a time, I uppgraded video drivers, monitor firmware.... nothing woked. Finally I investigated the issue of screen sync. I tried G-sync on with V-sync (in game) off, HDR on, HDR off. G-sync full screen set, G-sync full screen & windowed set no luck. It wasn't until I disabled g-sync completely and re-enabled v-sync in game (with FPS at 60) did I finally get some stability. Praise the virtual sky gods!!! Ive just done 3 flights - YBAS area, Bora-Bora scenery tour and YSBK to YSSY in the default C172 without a single CTD. So daring to hope I'm going to try renabling my community folder and see - wish me luck!
  3. Hello all, I purchased Changi (WSSS) and am experiencing CTD every time I attempt to start a flight from there. I've read the threads about the CGL files but Changi doesn't have one, unless I'm not finding it. Anyone else experiencing this, or have any idea of a workaround? Cheers.
  4. Hello, CTD with recent installed scenery from market place I have had the similar issue:- Purchased KTIW from Market Place (Delux Premium MSFS Version from MS Store) installed no problems I positioned random A/C to airport as departure dis a few touch and gos all well. I have numerous scenery /A/C (Carenado Ovation P44a & Cessna 182) installed some from Market Place some from Orbx directly, I do have Wycombe Park installed from market place a week earlier than KTIW. As mentioned touch and go immediately after installation on 1/1/20 worked satisfactory, closed MSFS and went back a few hours later to fly in multiplayer from KRNT to KTIW all well but CTD after hitting yellow FLY" button, this kept happening after reboot or PC Shut Down & Restart after much T/Shooting found that flying in to the Seattle area say KORS also caused CTD no warning at all. I have also seattle land marks from Market place installed several weeks ago. Since then have found that be unistalling KITW all reverts to normal No CTD using MSFS Default Airport Scenery for KITW. Can fly no issues around Seattle and district. Any thoughts Nick (Orbx) or other users who I know have similar issues, Iread all bout Wycombe possibly an issue or the developer of Seattle Land marks as knowing of an issue.
  5. Lately I cannot get through Longitude W7* 30.00" As soon as the nose of my plane hits this line my sim (P3D v4.5) freezes and will not restart. Sometimes the sounds are still working but that's it. If I click on any of my screens (I am using 3) anything to do with the sim greys out and I have to shut it down . Sometimes it crashes to desktop on it's own. As long as I stay away from that longitude all is well. I have tried crossing at different lattitudes, some as far away as 400 miles but I cannot get past it. I even tried setting my location on the map to be L W9* 30" or further and that doesn't work either. The sim will not start and crashes. In that region I am using Orbx Global Base, Vector and Open LC Europe. This longitude runs through Portugal. I first noticed this when I took off from LPCH to the north, after getting airbourne at the end of the runway I turn left to the west and go straight. It is not far to W7* 30.00". I previously posted this problem in Orbx General Discussion and a couple of guys duplicated my flight but had no problem getting through that longitude. I did also try coming in from the other side. I had to go all the way to just offshore of the east coast of North America to get the sim to go. I was only able to fly as far as W59* XX" before the sim froze and crashed. So there are 52 degrees in there that I can't run the sim in. I don't know if this is an Orbx problem, or P3Dv4.5, or something else in my computer or sim setup. Has anything like this ever been reported before?
  6. Hello, I think I have a problem with EGPH scenery, True Earth GBN and V5, I almost have CTD everytime I go there, sometimes I can take off and I have a CTD right after, sometimes it's on the approach, sometimes I can land and I have CTD while taxiing to the parking. I've tried with different settings, and nothing helped so far. I don't think it's a VRAM issue, it just happened and my VRAM use was 5.3 on 6.7 available ( would be weird that it would jump to the out of memory in a sec, when I had oom, I can see it will happen because the VRAM load is already in the 6.2 at least...), and it even happened with the textures option decreased to 1024 resolution, the vram use was around 3.8 then... I'm using P3Dv5 with the hotfix one, installed following the instructions I've found on this forum. On the ultimate crash, I had to reboot my computer manually, since it wasn't even crashing to windows... This version of P3D is far less stable for me than the first p3dv5, but this is the only airport where this happen almost everytime I go there. Does anybody have experienced that? Best M
  7. Hi ORBX, I believe I have narrowed down a G3D.dll P3D CTD on my PC using a combination of particular P3D settings and ORBX Australia V2. I am running the latest P3D v4.5 Hotfix 1. I have tried with my own settings vs. a default P3D.cfg with and without ORBX AU v2 installed. At S25°32.10 E142°13.16 while flying west along the T11 airway between VILOL and NONET P3D crashes to desktop each time with the G3D.dll module being shown as the faulting module in event viewer. Every time I tested this scenario I used the PMDG 737 NGX flying at 34,000ft and M0.78. Using my settings (attached below) I experienced the CTD with AU v2 installed only. With AU v2 uninstalled and using my P3D settings the simulator did not crash in this particular scenario. Using a default P3D.cfg I did not experience the CTD using the same scenario with AU v2 installed or uninstalled. Attached below is the event viewer log, my PC specs and the P3D settings for possible replication. I have flown around other parts of AU v2 using the same settings with not a single CTD - however in this particular area it occurs repeatedly with my settings. I hope this is able to replicated, as I feel AU V2 is definitely contributing in this particular area to the g3d.dll error I experience at these particular co-ordinates. Your Sincerely, Mackenzie Event Viewer Log: Faulting application name: Prepar3D.exe, version:, time stamp: 0x5cd47aad Faulting module name: g3d.dll, version:, time stamp: 0x5cd47a3d Exception code: 0xc0000005 Fault offset: 0x000000000000d7b7 Faulting process ID: 0x300 Faulting application start time: 0x01d52403fd6301f9 Faulting application path: C:\Lockheed Martin\Prepar3D.exe Faulting module path: C:\Lockheed Martin\g3d.dll Report ID: 583e8cb4-cef0-457c-8058-e1c433d6b4a2 Specs: CPU: Intel i7 8700K 5.0gHz GPU: Gigabyte GTX1080Ti 11GB Extreme Edition Cooler: Corsair H100i V2 liquid cooling for CPU RAM: 16GB SSD: 500GB m.2 (Windows + P3D + ORBX Scenery) Display: 2x 2560x1440p @ 60hz Other addons running at the time: AS16 P3D v4 REX SF FSUIPC P3D Settings:
  8. Hello, I really hope anyone can help me with my issue. P3d stops working when I load up airports (default and add on) in a certain areas. For example Boston area: I ctd at KBOS and airports that I tried in the area like 2B2(orbx) and to west as far as KALB and NY0, but at 6B4(37mi west of NY0) it loads up! I remember that 2B2, 6B6 and KSNC did work when I initially installed them upon release. To the South, KJFK fails but KPHL works. This problem also happens in the area around EGKK to EHAM, as far east as EDDT, but EPWA loads.To the north ESSA(orbx) works but ENVA does not. West, nothing works all the way to Spain, England, Great Britain etc. To the south everything all the way past Italy and Northern Africa to HLKF. There could be more areas that I don't know of. I believe I got this issue sometime in 4.3 but continued after updating to 4.4 (client, content, scenery). I usually fly in the Western US so hasn't been much of an issue for me as I didn't notice. The sceneries do load up and look good but after about 5 seconds is when I get the P3D stops working notification. I've tried deleting the P3D cfg file and Shader files with out success. The main scenery addons I have installed: All ORBX GLOBAL RANGE products, EU:England, NA: Cen.Rockies, NoCal, SoCal, PNW, PFjords, and few OCEANA airports and alot of airports in the NoCal and PNW regions. They all work except for a few in the global areas that I have mentioned. Could this be related to some Global Range product? I have attached a file that was generated by FTX Central. Im unsure if its related or not but did occur a few times. I've also attached (if it did it correctly) the main errors I get in event viewer when the crash occurs, though sometimes I dont get the kernalbase error just the other two. The main issue occurs everytime in the large affected known area. Please let me know what information you need me to provide for help and if the attached files are accessible. Any recommendations to remedy this issue would be greatly appreciated. orbx_ftxcentral_log.txt p3dstops_1033.MTA p3dstops.evtx
  9. Started a 350nm flight through Holland. Take-off from EHGG (Groningen) to EHLW (Leeuwarden) to EKHD (Den Helder) >>> all went well and although some blurries here and there, it was smooth and beautiful scenery! Then from EKHD to EHRD (Rotterdam) and as I approached Amsterdam the micro-stutters began but we pushed through and by the time we landed in Rotterdam, it was stutters. Shutdown the aircraft and let everything settled. Take-off to EHWO (Woensdrecht) but by now the FPS jump between 4 and 30 (capped at 30 due to Vsync on 4K and set to 60 FPS in P3D settings to reduce the blurries). By now we're more than an hour in P3D and flying over the Netherlands. Touch-stutter-and-stutter-go at EHEH (Eindhoven) and down to EHBK (Maastricht). Battling blurries but mainly stutters. Had something to eat and then straight to EHLE (Lelystad) but abeam Amsterdam P3D decided, ENOUGH! and KAPAAAW! CTD!!! No warning. No log file. No reason. Well I suppose x64 bit has its limits with 82GB of scenery but surely this magnificent scenery was not created in order for P3D to buckle underneath the detail? Aircraft: JustFlight Arrow Turbo Weather: ASP4 with fair weather scattered low clouds NL TE Settings: Everything on except - traffic and boats P3D Settings: Moderate to high but no sliders fully to the right PC Specs: i7 7700 @ 4.2 with GTX1080Ti with 32GB DDR4 on Win10x64 Maybe more optimisation or some guidelines on what to switch on and off in the Ned TE settings? Transaction ID: 5ae0725d6282a
  10. Hello Captains! I recently updated Vectors, and since then I get a CTD whenever I try to load anywhere west of Denver. Anyone have the same issue?
  11. Hi, I have P3D v4.3 installed and I keep getting a CTD at almost every shutdown. The failing module is api.dll, according to the message window that says "Prepar3d isn't working anymore". Has anyone an idea how to get rid of it? I don't know where to start. Cheers Lars
  12. Hi there, I recently bought the Pula Airport scenery. Three times in a row now, P3Dv4.2 crashed to desktop when I approached LDPL. No Windows-Log to show the reason, just a CTD and that's it. Happens when I'm on RNAV RWY09 approach just when the airfield comes into sight. Loading a scenario on LDPL works fine. Can someone help me? Other addons used: FTX Global, openLC EU, TreesHD, Germany South. GSX, AS, ASCA, EnvTex & EnvShade, ChasePlane. Flight performed from LICC with FSL A320. BG, Stu
  13. I’m having a P3D v4 CTD with Event Viewer showing a Terrain.dll issue. the problem always occurs at the same place at the coat of Scotland, just past waypoint BLACA. Every single time. Before the CTD the are major stutters for 10 seconds and then the CTD. Has anyone seen this before? I have tested over and over and when Orbx base Europe is unchecked from the library the crash doesn’t happen. I am posting this again as my previous support request went completely ignored on this forum. Orbx - what’s going on with this? Any help appreciated. Paul
  14. Installed latest update ... same as previous version <<< CTD just before taxi or halfway down the runway at NIGHT. Manually disabled DL seeing that the option is not in Control Panel in FTXC but still get a CTD or is it an OOM??? Only airport in P3D4 that's doing this. Any ideas what, why, where, when ...???
  15. After installing ORBX Telluride scenery in my P3DV4.0 (by FTX Central 3) I noted that Bonanza (P3DV4 default) vc panel textures were corrupted with a mixing of 2d and 3d images (see attached), moreover I had frequent CTD loading some Carenado planes (Phenom300, Navajo, C90, H850XP); this problems were never before ORBX Telluride installation. I have to note that also deactivating Telluride scenery , Orbx libraries and objectflow addon, the problem was still present . No changes also after upgrading video drivers and after uninstalling and fresh installing the Carenado airplanes . After lowering the grass detail level and other details using Telluride control panel, this problems were solved completely and everything returned to normal, no more CTD. In my modest opinion this interference is not fortuitous, connected maybe to my video card or other possible texture rendering interferences in my system. It would be interesting to know if other customers have had similar problems. Thanks, My specs: I7 6700K, 16 GB RAM, NVIDIA GTX 760 2GB, 2 x SSD .
  16. Hey hello.. Im getting very frustated about this.. I bought like 2 months ago, ftx vector, global, open LcNorth america and South america, trees HD, NA Southern California, NA North California, KAVX, etc.. I definitely wanna get KSAN, but if this cant be solved, it doesnt make sense to get it.. And i have to say those are amazing.. they completely change the sim, but every single time i fly inside this particular area of LA i get a CTD, probably because of OOM: My PC is not the best but definitely its able to run the sim.. CPU: i7 7700K RAM: 16gb DDR4 2Tb HDD 2 GTX 770 SLI Z270 Mobo I tried this flights all of them went to a CTD when i was getting closer to this area.. - KSDM - KSMO - L35 - KWHP - L35 - KAVX - KSDM - KVNY And this flight i was able to do it... - KSMO - KAVX - KAVX - KSMO - KSMO - KWHP - KTNP - L35 - MMPE - L35 - KTNP - MMES On every flight im between 25FPS and 60FPs depending on the area. Hope you can help me.. Im definitely thinking in getting P3D V4, im just not sure if this is going to work.. My sim is perfect it just dont work in that area..
  17. Hi everyone, first post on the forums! I've run into a spot of bother recently with P3D v3 where I keep encountering CTD's near mountainous terrain due to a faulting terrain.dll. I asked the guys on avsim but they seemed to be confused as well so I thought I might you guys at ORBX whether your product might have something to do with the problem. Specs are in my signature. All these CTD's have occurred when flying near mountainous terrain. For example, last night I was on short final into Geneva airport (obviously right on the doorstep of the Alps so there is some mountainous terrain nearby) and P3D just froze and then had a CTD. The event viewer displayed it as a terrain.dll error and my AppCrashView produced this log: Version=1 EventType=APPCRASH EventTime=131528300621292849 ReportType=2 Consent=1 UploadTime=131528300640305423 ReportStatus=268435464 ReportIdentifier=c41c9da9-6003-4376-81ab-f12677ef9474 IntegratorReportIdentifier=6a30f0fc-b4b4-412e-a51d-8576041f307e Wow64Host=34404 Wow64Guest=332 NsAppName=Prepar3D.exe AppSessionGuid=0000373c-0001-006f-c4be-c0663a48d301 TargetAppId=W:0000378dcf8f6806260dceef311e19dc8aef0000ffff!00008cd6304f3c0e0d0d80889abee8e5e1810c79dc4f!Prepar3D.exe TargetAppVer=2016//03//08:21:49:02!6d9fb!Prepar3D.exe BootId=4294967295 ServiceSplit=3539031 TargetAsId=535 Response.BucketId=717f00be7f3b214f56d9c8e9c44cf9a7 Response.BucketTable=1 Response.LegacyBucketId=108023844387 Response.type=4 Response.CabId=108241796977 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value= Sig[2].Name=Application Timestamp Sig[2].Value=56df48ce Sig[3].Name=Fault Module Name Sig[3].Value=terrain.dll Sig[4].Name=Fault Module Version Sig[4].Value= Sig[5].Name=Fault Module Timestamp Sig[5].Value=56df4841 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00008671 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.15063. DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=a6a1 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=a6a168da3d7661da609288f65e50f73c DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=5c77 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=5c77cd1d43776eebe4628a3d65c7773f UI[2]=F:\Prepar3D\Prepar3D.exe UI[3]=Prepar3D exe has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=F:\Prepar3D\Prepar3D.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\SYSTEM32\apphelp.dll LoadedModule[5]=C:\WINDOWS\System32\USER32.dll LoadedModule[6]=C:\WINDOWS\System32\win32u.dll LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[11]=C:\WINDOWS\System32\ole32.dll LoadedModule[12]=C:\WINDOWS\System32\combase.dll LoadedModule[13]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[14]=C:\WINDOWS\System32\SspiCli.dll LoadedModule[15]=C:\WINDOWS\System32\CRYPTBASE.dll LoadedModule[16]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[17]=C:\WINDOWS\System32\sechost.dll LoadedModule[18]=F:\Prepar3D\api.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\MSVCP120.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\MSVCR120.dll LoadedModule[21]=C:\WINDOWS\System32\IMM32.dll LoadedModule[22]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[23]=C:\WINDOWS\System32\ADVAPI32.dll LoadedModule[24]=C:\WINDOWS\System32\msvcrt.dll LoadedModule[25]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[26]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[27]=C:\WINDOWS\System32\cfgmgr32.dll LoadedModule[28]=C:\WINDOWS\System32\shcore.dll LoadedModule[29]=C:\WINDOWS\System32\windows.storage.dll LoadedModule[30]=C:\WINDOWS\System32\shlwapi.dll LoadedModule[31]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[32]=C:\WINDOWS\System32\kernel.appcore.dll LoadedModule[33]=C:\WINDOWS\System32\powrprof.dll LoadedModule[34]=C:\WINDOWS\System32\profapi.dll LoadedModule[35]=C:\WINDOWS\SYSTEM32\Cabinet.dll LoadedModule[36]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.15063.413_none_55bc94a37c2a2854\COMCTL32.dll LoadedModule[37]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[38]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[39]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[40]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[41]=F:\Prepar3D\acontain.dll LoadedModule[42]=F:\Prepar3D\controls.dll LoadedModule[43]=F:\Prepar3D\ai_player.dll LoadedModule[44]=F:\Prepar3D\atc.dll LoadedModule[45]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[46]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[47]=F:\Prepar3D\demo.dll LoadedModule[48]=F:\Prepar3D\facilities.dll LoadedModule[49]=F:\Prepar3D\DIS.dll LoadedModule[50]=F:\Prepar3D\flight.dll LoadedModule[51]=F:\Prepar3D\g2d.dll LoadedModule[52]=C:\WINDOWS\System32\WLDAP32.dll LoadedModule[53]=F:\Prepar3D\fs-traffic.dll LoadedModule[54]=F:\Prepar3D\fe.dll LoadedModule[55]=F:\Prepar3D\gps.dll LoadedModule[56]=F:\Prepar3D\main.dll LoadedModule[57]=C:\WINDOWS\System32\COMDLG32.dll LoadedModule[58]=F:\Prepar3D\menus.dll LoadedModule[59]=F:\Prepar3D\livingwater.dll LoadedModule[60]=F:\Prepar3D\pdk.dll LoadedModule[61]=F:\Prepar3D\g3d.dll LoadedModule[62]=F:\Prepar3D\sim1.dll LoadedModule[63]=F:\Prepar3D\simscheduler.dll LoadedModule[64]=F:\Prepar3D\simprop.dll LoadedModule[65]=F:\Prepar3D\sound.dll LoadedModule[66]=F:\Prepar3D\symmap.dll LoadedModule[67]=F:\Prepar3D\terrain.dll LoadedModule[68]=F:\Prepar3D\panels.dll LoadedModule[69]=F:\Prepar3D\multiplayer.dll LoadedModule[70]=F:\Prepar3D\util.dll LoadedModule[71]=F:\Prepar3D\visualfx.dll LoadedModule[72]=F:\Prepar3D\window.dll LoadedModule[73]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[74]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[75]=F:\Prepar3D\weather.dll LoadedModule[76]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[77]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[79]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[81]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll LoadedModule[85]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[86]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[87]=C:\WINDOWS\SYSTEM32\dwmapi.dll LoadedModule[88]=F:\Prepar3D\audiere.dll LoadedModule[89]=F:\Prepar3D\language.dll LoadedModule[90]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[91]=C:\WINDOWS\SYSTEM32\MSXML6.DLL LoadedModule[92]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[93]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[94]=F:\Prepar3D\uiInterface.dll LoadedModule[95]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[96]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[97]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll LoadedModule[98]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[99]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\aff328835c74ccf06c928da8cc8caa0a\mscorlib.ni.dll LoadedModule[100]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll LoadedModule[101]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\256e494bb636a4470fbf20aa659a9ee6\System.ni.dll LoadedModule[102]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\33efde8b33d0774ac84f1a4e3787100e\System.Core.ni.dll LoadedModule[103]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\8b11102c36bc3f51b7819509f440334e\WindowsBase.ni.dll LoadedModule[104]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[105]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[107]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\3991f21b39d3b4c16ef53c46c7571c88\PresentationCore.ni.dll LoadedModule[108]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\d0c2eddc60e2672cd6290994abd2498d\PresentationFramework.ni.dll LoadedModule[109]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\cd2d327e3239ab0acae3890753ffffd4\System.Xaml.ni.dll LoadedModule[110]=C:\WINDOWS\SYSTEM32\dwrite.dll LoadedModule[111]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[112]=F:\Prepar3D\D3DCOMPILER_47.dll LoadedModule[113]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll LoadedModule[114]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[115]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\f070aa06c51f4e8eec494cd9a1dd2cb6\System.Configuration.ni.dll LoadedModule[116]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\44f8a101303a1090c91e893ec336b745\System.Xml.ni.dll LoadedModule[117]=C:\WINDOWS\SYSTEM32\iphlpapi.dll LoadedModule[118]=C:\WINDOWS\System32\NSI.dll LoadedModule[119]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[120]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[121]=C:\WINDOWS\SYSTEM32\secur32.dll LoadedModule[122]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[123]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[124]=C:\Windows\System32\rasadhlp.dll LoadedModule[125]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[126]=C:\WINDOWS\system32\nvapi.dll LoadedModule[127]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvldumd.dll LoadedModule[128]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvwgf2um.dll LoadedModule[129]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[130]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[131]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[132]=C:\Windows\System32\WinTypes.dll LoadedModule[133]=C:\WINDOWS\system32\ntshrui.dll LoadedModule[134]=C:\WINDOWS\system32\srvcli.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\cscapi.dll LoadedModule[136]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.15063.483_none_6dad63fefc436da8\comctl32.dll LoadedModule[137]=C:\WINDOWS\system32\netutils.dll LoadedModule[138]=C:\WINDOWS\System32\coml2.dll LoadedModule[139]=C:\WINDOWS\SYSTEM32\LINKINFO.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[141]=C:\WINDOWS\System32\drprov.dll LoadedModule[142]=C:\WINDOWS\System32\ntlanman.dll LoadedModule[143]=C:\WINDOWS\System32\davclnt.dll LoadedModule[144]=C:\WINDOWS\System32\DAVHLPR.dll LoadedModule[145]=C:\WINDOWS\System32\wkscli.dll LoadedModule[146]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[147]=C:\WINDOWS\System32\DEVOBJ.dll LoadedModule[148]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[149]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[150]=C:\Windows\System32\Windows.UI.dll LoadedModule[151]=C:\Windows\System32\TextInputFramework.dll LoadedModule[152]=C:\Windows\System32\CoreUIComponents.dll LoadedModule[153]=C:\Windows\System32\CoreMessaging.dll LoadedModule[154]=C:\WINDOWS\SYSTEM32\usermgrcli.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[156]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\9e829b12fef7addbb879b11e48e50305\PresentationFramework.Aero2.ni.dll LoadedModule[157]=C:\WINDOWS\SYSTEM32\urlmon.dll LoadedModule[158]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[159]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[160]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_ref_pubwu.inf_amd64_f9309145156afb40\nvd3dum.dll LoadedModule[161]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\fd30f45dfd963758273e801d9daeba3f\System.Drawing.ni.dll LoadedModule[162]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\d760b4bb8b2f9c014aa7e8bd3818182e\System.Windows.Forms.ni.dll LoadedModule[163]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[164]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[166]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[167]=F:\Prepar3D\radar.dll LoadedModule[168]=F:\Prepar3D\Oculus.dll LoadedModule[169]=C:\WINDOWS\SYSTEM32\dbghelp.dll LoadedModule[170]=F:\Prepar3D\ControllableCamera.dll LoadedModule[171]=C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll LoadedModule[172]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[173]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCP80.dll LoadedModule[174]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9307_none_d0882a20442f72e4\MSVCR80.dll LoadedModule[175]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[176]=F:\Prepar3D\bglmanx.dll LoadedModule[177]=C:\WINDOWS\System32\PSAPI.DLL LoadedModule[178]=F:\Prepar3D\Gauges\TargetInfo.dll LoadedModule[179]=F:\Prepar3D\Aerosoft\Flight Recorder\AS-FlightRecorder.dll LoadedModule[180]=F:\Prepar3D\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll LoadedModule[181]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[182]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[183]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[184]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[185]=C:\WINDOWS\SYSTEM32\msiso.dll LoadedModule[186]=F:\Prepar3D\as_srv\as_btstrp.dll LoadedModule[187]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationUI\0f1e63d5fdec337e525ccb2a31c79ab0\PresentationUI.ni.dll LoadedModule[188]=F:\Prepar3D\SimDirector.dll LoadedModule[189]=F:\Prepar3D\BGLCompLib.dll LoadedModule[190]=F:\Prepar3D\simpropext.dll LoadedModule[191]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[192]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\icm32.dll LoadedModule[195]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Web\319a18dd4ac0f833144a1894cac6f726\System.Web.ni.dll LoadedModule[196]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll LoadedModule[197]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\c4e2f99afd5b2efa78bed97329d2e7e9\UIAutomationTypes.ni.dll LoadedModule[198]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll LoadedModule[199]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[200]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[201]=C:\WINDOWS\system32\dcomp.dll LoadedModule[202]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[203]=C:\WINDOWS\system32\msctfui.dll LoadedModule[204]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\fa217ae957406a0f964a4eff667b2a45\System.Runtime.Serialization.ni.dll LoadedModule[205]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\cb8d5cc04826287f4a38f722c1fe0123\SMDiagnostics.ni.dll LoadedModule[206]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\ea16903f1a7a96378553e45333d78bc4\System.ServiceModel.Internals.ni.dll LoadedModule[207]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.15063.483_none_9e9856e456d5e776\gdiplus.dll LoadedModule[208]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\586cb3f4f85f1e09131df9cbf00b65c5\UIAutomationProvider.ni.dll LoadedModule[209]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[210]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Accessibility\33d2873c31c340bec341bcdb1fd7f2e5\Accessibility.ni.dll LoadedModule[211]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Windows.UI\3fd6268844ed3a19ad3ba55c4e4eaa89\Windows.UI.ni.dll LoadedModule[212]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runtbff93e24#\d0977975d17ff1f1ce506f27b8efd72e\System.Runtime.InteropServices.WindowsRuntime.ni.dll LoadedModule[213]=C:\Windows\System32\twinapi.dll LoadedModule[214]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\FMGS.dll LoadedModule[215]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\Airbus_ECAMD2D.dll LoadedModule[216]=C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9279_none_50939ec6bcb7c97c\MSVCR90.dll LoadedModule[217]=C:\WINDOWS\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9279_none_50939ec6bcb7c97c\MSVCP90.dll LoadedModule[218]=C:\WINDOWS\SYSTEM32\d2d1.dll LoadedModule[219]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ASC.dll LoadedModule[220]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ND\AB_ND_GDI.dll LoadedModule[221]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\AsInput.dll LoadedModule[222]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\FBW.dll LoadedModule[223]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE2.dll LoadedModule[224]=F:\Prepar3D\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE.dll LoadedModule[225]=C:\WINDOWS\SYSTEM32\D3D10Warp.dll LoadedModule[226]=C:\Windows\System32\ieframe.dll LoadedModule[227]=C:\Windows\System32\NETAPI32.dll LoadedModule[228]=C:\Windows\System32\DSREG.DLL LoadedModule[229]=C:\Windows\System32\msvcp110_win.dll LoadedModule[230]=C:\Windows\System32\mshtml.dll LoadedModule[231]=C:\Windows\System32\srpapi.dll LoadedModule[232]=C:\WINDOWS\SYSTEM32\WLDP.DLL LoadedModule[233]=C:\WINDOWS\System32\WINTRUST.dll LoadedModule[234]=C:\Windows\System32\vaultcli.dll LoadedModule[235]=C:\WINDOWS\SYSTEM32\MLANG.dll LoadedModule[236]=C:\WINDOWS\SYSTEM32\msadp32.acm LoadedModule[237]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[238]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[239]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[240]=C:\WINDOWS\system32\wbem\fastprox.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 File[0].CabName=minidump.mdmp File[0].Path=WER893.tmp.mdmp File[0].Flags=539820035 File[0].Type=2 File[0].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER893.tmp.mdmp File[1].CabName=WERInternalMetadata.xml File[1].Path=WERF0D.tmp.WERInternalMetadata.xml File[1].Flags=851971 File[1].Type=5 File[1].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0D.tmp.WERInternalMetadata.xml File[2].CabName=memory.csv File[2].Path=WERF0C.tmp.csv File[2].Flags=851971 File[2].Type=5 File[2].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0C.tmp.csv File[3].CabName=sysinfo.txt File[3].Path=WERF1C.tmp.txt File[3].Flags=851971 File[3].Type=5 File[3].Original.Path=\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF1C.tmp.txt File[4].CabName=AppCompat.txt File[4].Path=WER1BB0.tmp.appcompat.txt File[4].Flags=17629187 File[4].Type=5 File[4].Original.Path=\\?\C:\Users\Fraser\AppData\Local\Temp\WER1BB0.tmp.appcompat.txt File[5].CabName=WERDataCollectionStatus.txt File[5].Path=WER21DB.tmp.WERDataCollectionStatus.txt File[5].Flags=851971 File[5].Type=5 File[5].Original.Path=\\?\C:\Users\Fraser\AppData\Local\Temp\WER21DB.tmp.WERDataCollectionStatus.txt File[6].CabName=Report.zip File[6].Path=Report.zip File[6].Flags=196608 File[6].Type=11 File[6].Original.Path=\\?\C:\WINDOWS\system32\Report.zip FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Prepar3D exe AppPath=F:\Prepar3D\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=9CEA1B3466F160E2F0D6777C43443EF6 MetadataHash=963977023 I have reduced my mesh resolution and tesselation factors in my settings and also rebuilt the p3d.cfg file to set P3D back to default. I suspect it is something to with ORBX Europe which was updated a while back and since then when flying near mountains I have had a terrain.dll CTD. It's odd because before this happened, even when I had LC Europe installed, flying near mountains was absolutely fine and I never had any terrain.dll CTD's. Something must have happened to cause this as my PC handled ORBX Europe absolutely fine beforehand. Is there anyway to perhaps uninstall ORBX updates to try and fix issues like this? I use FTX Central by the way. Many thanks, Flemon
  18. Good Day, I just bought FTX EU England, and installed it. Now when I load up a flight, P3D V4 instantly crashes, and it doesn't matter where in the world I load it up, or what aircraft I use, it crashes as I click Fly Now. I have uninstalled it, and now everything is working again. So this must have something to do with EU England. Here is the crash report: Faulting application name: Prepar3D.exe, version:, time stamp: 0x594a7255 Faulting module name: ntdll.dll, version: 10.0.14393.1715, time stamp: 0x59b0d03e Exception code: 0xc0000005 Fault offset: 0x000000000003f6a1 Faulting process id: 0x28d8 Faulting application start time: 0x01d33a8f75a6f5ff Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 3c973538-23cc-4c55-9043-5c9be7861080 Faulting package full name: Faulting package-relative application ID: Fault bucket 120832671485, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: P3: 594a7255 P4: ntdll.dll P5: 10.0.14393.1715 P6: 59b0d03e P7: c0000005 P8: 000000000003f6a1 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA7.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_c6b33a9dc8e73dd1e32171f57942a6c5c55b5579_305ee810_7694161d Analysis symbol: Rechecking for solution: 0 Report Id: 3c973538-23cc-4c55-9043-5c9be7861080 Report Status: 1 Hashed bucket: b7a3a672def554538aaed87f92511c0a
  19. Hello orbx, hello community, i spent most of the last 2 days troubleshooting my P3D V4. I had an issue two days ago where payware-aircraft immidiately made P3D CTD when i clicked "fly" - after some troubleshooting, i got that sorted out by deinstalling and reinstalling orbx (Global, LC EU, LC NA, North Germany, Trees HD). I thought things were fine, but they arent. I'm currently flying the same flight for the 6th time: ENTC (Tromso) to LOWW (Vienna) with PMDG 738WL. All of these flights CTD when I clicked the MCDU after 60-90minutes inflight. No matter if active sky on/off, chaseplane on/off, airports on/off, you name it. Of course, i started with deinstalling the PMDG and installing the newest package, reinstalling P3D content, but with no luck. Finally i gave it a try and disable all of ORBX Products and now everything seems to work fine. I just landed after over 3 hours of flight without any issues in vienna. Could click on the MCDU all the time. Is there any reasonable connection that can cause such issues? I'll be happy to provide whatever information necessary. My next steps would be: - completely remove all ORBX-Products and removing ALL files - reinstall them in the best possible way/order. I'd appreciate any input how to do that in the best possible manner. thank you in advance, stefan SYS: i6700k, 1080ti, win 10, p3dv4. current drivers.
  20. Hi, I have an extremely frustrating issue with P3D v4 & any Orbx product I install through FTX Central v3. This actually started the weekend after the 55% off sale. I had P3D v3 at the time and bought and installed OpenLC NA & Europe and AU Australia. I had Global Base, Vector & HD Trees already installed. After I installed the new products, P3D would crash & not respond during the scenario loading, when the terrain was loading at about 25%. The event viewer showed this application error: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 000007FEDE36C3B3 Prepar3D.exe 594a7255 g2d.dll 594a7313 c0000005 000000000010c3b3 18b0 01d300e1c8f668a3 E:\Lockheed Martin\Prepar3D v4\Prepar3D.exe E:\Lockheed Martin\Prepar3D v4\g2d.dll 58016d11-6cd5-11e7-bd20-d050995ccf1b I never had an issue with P3D v3 until after the new Orbx products were installed. Uninstalled Orbx products, still received crashes while loading scenario. Now, I have P3D v4 installed and have no application errors while loading scenarios with no addons. I installed Global Base & Vector via FTX Central, tested different world areas and I'm getting the same "P3D is not responding" crashes while scenario is loading the terrain and the same Windows application error. Not all areas. Some areas I am able to load a scenario and fly. But, the areas where P3D does crash never load and the areas where P3d does load completely always load completely. This is telling me that the Orbx install is giving me corrupt scenery files. Then I have to completely reinstall P3D v4. I am using a CAT5E cable from my PC to my router. My internet is 50meg. I have my anitvirus off while downloading & installing. The first time I downloaded Vector, I know there were corrupt files because I rebooted and checkdisk came up and showed corrupt files before loading Windows 7. I have had Base & Vector installed via actual files(not through FTX Central) on P3D v2.5 & v3 with no issues. What should I do? I'm tearing my hair out with this. It shouldn't be this difficult to install addons. Should I download the files manually via my product page? Should I turn off multiple threads for downloads in FTX central? I know this post is long, but I want to give as much info as possible. I just want my complete sim back. Thanks in advance. Nick Specs CPU: Intel 4790k RAM: 16g DDR3 GPU: EVGA 1080 Storage: (2) 500g Samsung EVO SSD's Windows 7
  21. Hopefully I can find a fix for this... Unfortunately my sim has been crashing randomly due to this module from Nvidia coming form (C:\Windows\system32\nvwgf2um.dll). The crash happens either while on the ground, or during cruze. I have tried countless different settings on FSX DX9 mode; DX10 Fixer; windowed mode; borderless windowed mode, and the crash keeps on happening. I have not tried fullscreen mode scince i have multiple monitors for vpilot, etc. All drivers are updated and any addon software associated with FSXSE are as well. the CFG file is default only entry is affinitymask=14. everything in FSXSE installed outside of the C Drive. This has been very frustrating and annoying. and I appreciate you all that can help me with this. I have been useing FSX for Years and i never experienced this before. Also here is my nvidia inspector settings if it helps... W7 Ultimate i5 3570K 16GB gskill 2133 Nvidia Titan X - 2 Jean.
  22. When taking off with any aircraft from r/w 23, climbing out over the sound at approx. 1,000ft, my system crashes to desktop, no reason given. When I disable NZQN in the world scenery there is no problem, so I removed the NZQN folder from ORBX main folder, and reinstalled with a fresh download from Flightsim Store, and the problem still persists. Any assistance appreciated. Michael
  23. Hi I have been using FTX global since it was released and has been a great addition to FSX. So with the enjoyment I have had with this product I thought I would treat myself to your FTX England product. Since I purchased this and installed it I started having CTD after about 20-30 mins. I never had any CTD before and had been running FSX trouble free for many years. I have tried searching for this issue but not had any luck. I have tried uninstall and reinstall as well as making sure I followed the correct procedure for installation making sure I update the ORBX Libraries after running everything. Another strange issue with this is that the CTD does not produce any error report. Everyone says that is impossible for it to crash without an error report but I work in IT support and I know windows event viewer and windows error reporting inside out and use this to do my job daily. So the issue I get is not that it has "Stopped responding" it literally closes the process and also closes my EZCA.exe process as well. I had issues with FSX many years ago which did generate event logs showing the offending modules e.g "Uiautomationcore.dll" and these helped me to diagnose and fix issues so that I could have a trouble free installation. Now another reason why I know that it is FTX England that is causing the problem is if I remove the sceneries for England it does not crash anymore. This is a shame as I like what FTX England brings to FSX such as the much improved default airports (which are insanely better) and the improved mesh which makes the landscape feel more alive. However as soon as I turn on England scenery 20-30 mins flying and CTD turn it off and trouble free. I would love to get this working please help as I don't even know where to look without an event viewer error report.
  24. Orbx report code: otbdf3a206e16feb36169c206824bb6324 I ran FTX Central the other day and it had two updates, one for my KBVS airport and Orbx Libraries. I have FSX & P3D both installed, (I only use P3D) and FTXCentral never registered that I had FSX before, now it asks which sim to select when I start it up. After this I started getting strange issues with my sim, my A2A Commanche throttle wouldn't work, then the sim would crash when selecting that plane, but would load just fine with a stock aircraft. Now the sim will not load at all, it will just CTD, i've received ai_player.dll in the event viewer, and ntdll.dll, and sometimes i receive no error that it crashes, it just goes right back to the desktop. I've tried deleting scenery.cfg and prepar3d.cfg files to have it create new ones, but it will still CTD. Tried deleting Scenery.dat files, deleted shaders, reapplied global, NA, EU, tried various airports in all regions, all still CTD. I can't figure it out. I have a lot of addons, one of which is MyTraffic 6, I'm going to try reinstalling that, but I don't think that will fix my Sim. I'm out of ideas. thanks.
  25. Re-opening this issue because the CTD comes back with BASE enabled. A re-install solved it for a few hours, but then it came back with no changes to my system. I'm getting CTD's at the follwing airports consistently during the "Loading Terrain" part of the startup. Santa Fe NM Albuquerque NM Eagle CO Just north of Aspen CO Interesting all are along the 106W longitude..... although further up north in Casper Wyoming, everything is fine. It seems to happen south of the 40N latitude. The sim works 100% fine with BASE unchecked in the scenery library. I can leave the LC and Library checked with no issue. Here's my troubleshooting steps: Aircraft Used - Default F-35 Startup Scenario = Default Jump to scenery using the world / go to airport menu Checked NVIDIA driver for the latest. Disabled Nvidia Inspector settings back to default Lowered Graphic Settings - AA/AF down to minimum Lowered Auotgen down to minimum Used the FTX Central to make sure library entries are in the right order Unchecked all 3rd party sceneries even though I have nothing active along the 106W longitude line. IF I remove the file 1_fix_lc_fsx.bgl from the C:\P3D\ORBX\FTX_OLC\OLC_AA\Scenery folder, everything works fine. It's just unclear to me what function that file has that I actually removed. The only other file in the scenery folder is REG_C.bgl. That isn't causing issues. So either that file is the culprit, or something is clashing with that file. Hoping I can get someone to look closer at this, or give me some insight what the bgl file that I removed does. Thank, Bob Donovan FSS0286565
  • Create New...