September 23, 20232 yr So... I came back to P3D v5.3 from MSFS and now starting to regret the move... 😁 I don't remember having frequent terrain.dll crashes in the past and now I start getting them specifically around Texas (Houston). Are there any new insights around this error? I've looked into the Avsim CTD guide and saw it may be related to autogen but I haven't changed those settings and even upgraded my GPU 1080Ti -> 3080Ti since leaving P3D. I've ran a chkdsk and nothing came up, I've also ran sfc /scannow and got an indication that some corrupted files were fixed but not sure that will fix the issue. On thing I did notice is now that I have new Razer v2 headphones I get some cracking noise when panning around as if the graphics are influencing the sound coming into the headphones which may be a sign of system overload? Could it be my RAM (16GB) is not sufficient? I run locked frames in Nvidia control panel and unlimited in-game with medium autogen settings. Could it be related to AIG models? The only new addons I use are AIG, FSHud and the ifly Max but the crashes happen only around Texas. Appreciate any help... Shom MSFS2024 running on Win 11, 4K screen, Z790 AORUS ELITE AX-W, i9-14900K, MSI 3080Ti, Corsair 2x32GB 6000 MHz, 1+2TB M.2 NVMEs
September 23, 20232 yr Maybe look here. Terrain.dll crash Any recent windows updates? Edited September 23, 20232 yr by newtie ..
September 23, 20232 yr 2 hours ago, Shomron said: don't remember having frequent terrain.dll crashes in the past and now I start getting them specifically around Texas (Houston). Are there any new insights around this error? While this suggestion I'm about to make may not resolve your issue, it's a first step I always take to trouble shoot as it's the easiest thing to do. Delete the generated shader and scenery index files prior to starting the sim. Both will dynamically regnerate automaticaly when the sim is started, noting the first restart after clearing will take a bit longer while the files are regenerated. Shader generated files (.cso files) can build up to thousands over time, clearing them out lets P3D start with a clean slate. The scenery index files hold the lookup tables for scenery and are a finite number, regenerating them updates with current details. Once you've restarted P3D set up and save a test flight for testing the issue in a repeatable manor. Locations: C:\Users\<windows login account name>\AppData\Local\Lockheed Martin\Prepar3D v5\Shaders C:\ProgramData\Lockheed Martin\Prepar3D v5\SceneryIndexes_x64 Where <windows login account name> is your Windows login account name. I keep a desktop folder with a series of shortcuts to these sort of locations for easy access. Cheers Ryzen 5800X clocked to 4.7 Ghz (SMT off), 32 GB ram, Samsung 1 x 1 TB NVMe 970, 2 x 1 TB SSD 850 Pro raided, Asus Tuf 3080Ti P3D 4.5.14, Orbx Global, Vector and more, lotsa planes too. Catch my vids on Oz Sim Pilot, catch my screen pics @ Screenshots and Prepar3D
September 24, 20232 yr Author 14 hours ago, newtie said: Maybe look here. Terrain.dll crash Any recent windows updates? I always keep windows up to date, issue is I haven’t been using P3D for a while so would not be able to trace a specific update causing this. 13 hours ago, Rogen said: While this suggestion I'm about to make may not resolve your issue, it's a first step I always take to trouble shoot as it's the easiest thing to do. Delete the generated shader and scenery index files prior to starting the sim. Both will dynamically regnerate automaticaly when the sim is started, noting the first restart after clearing will take a bit longer while the files are regenerated. Shader generated files (.cso files) can build up to thousands over time, clearing them out lets P3D start with a clean slate. The scenery index files hold the lookup tables for scenery and are a finite number, regenerating them updates with current details. Once you've restarted P3D set up and save a test flight for testing the issue in a repeatable manor. Locations: C:\Users\<windows login account name>\AppData\Local\Lockheed Martin\Prepar3D v5\Shaders C:\ProgramData\Lockheed Martin\Prepar3D v5\SceneryIndexes_x64 Where <windows login account name> is your Windows login account name. I keep a desktop folder with a series of shortcuts to these sort of locations for easy access. Cheers Thank you, will do that. I’ve actually done the P3D cfg and shaders rebuild but still getting CTDs. I’ll do the same for the scenery indexes. Shom MSFS2024 running on Win 11, 4K screen, Z790 AORUS ELITE AX-W, i9-14900K, MSI 3080Ti, Corsair 2x32GB 6000 MHz, 1+2TB M.2 NVMEs
Archived
This topic is now archived and is closed to further replies.