October 29, 20178 yr Hi, Doing a bit of housework on P3D and I have a few questions. 1. I've been told to rebuild my terrain.cfg in order to try and solve my terrain.dll CTD's. Is this simple as moving the terrain.cfg to a different folder, running P3D and letting it build a brand new one? Or is it just better to rebuild the p3d.cfg which will reset everything back to default? 2. I'd also like to completely reinstall my ORBX products. I use FTX Central 3 and I've noticed there isn't an option to uninstall the scenery libraries. How would I go about successfully reistalling ORBX Global, LC Europe, the libraries and FTX Central? Is there a certain order to uninstall then install? Thanks for the help! Regards, Flemon [email protected], GTX960 2GB, 8GB RAM, 120GB SSD, 1TB HDD, Windows 10 P3D v3, AS A320/21, ORBX Global and Europe, ASN, HDE Cloud and Sun Textures, Chaseplane, vPilot (earlier version due model matching), WOAI for model matching (no AI in-sim)
October 29, 20178 yr You're going to get a lot of suggestions. Mine is to head over to the official Orbx forums and read through the stickies for the information you need. www.orbxsystems.com -J 13700KF | RTX 4090 @ 1440 | 64GB DDR5 | 2 x 1TB SSDs | 1TB M.2 NVMe
October 30, 20178 yr Author Unfortunately the stickies there are for reinstalling ORBX assuming you've reinstalled the whole of your flightsim or OS. What I'm doing this just reinstalling ORBX products. Can I just use the 'uninstall' button in FTX central and then reinstall? Or is it more complicated? [email protected], GTX960 2GB, 8GB RAM, 120GB SSD, 1TB HDD, Windows 10 P3D v3, AS A320/21, ORBX Global and Europe, ASN, HDE Cloud and Sun Textures, Chaseplane, vPilot (earlier version due model matching), WOAI for model matching (no AI in-sim)
October 30, 20178 yr On 29/10/2017 at 2:02 PM, flemon said: I've been told to rebuild my terrain.cfg in order to try and solve my terrain.dll CTD's. Is this simple as moving the terrain.cfg to a different folder, running P3D and letting it build a brand new one? Hello Follow the steps in this order 1) Delete your terrain.cfg file, Copy the TEX below and Paste it into your windows search bar, click on the result and delete your terrain.cfg file %PROGRAMDATA%\Lockheed Martin\Prepar3D v4 2) Then Launch Prepar3D to the first screen and close it, Your terrain.cfg file will generate again as default 3) After this Launch the FTX Central control panel and wait 10 \ 15 seconds, as this will configure your terrain.cfg file again for Orbx use After this you are ready to launch Prepar3D and test On 29/10/2017 at 2:02 PM, flemon said: I'd also like to completely reinstall my ORBX products. I use FTX Central 3 and I've noticed there isn't an option to uninstall the scenery libraries. How would I go about successfully reistalling ORBX Global, LC Europe, the libraries and FTX Central? If you need to reinstall any Orbx products navigate to the location below and Delete the version TXT file you wish to reinstall again Prepar3D v4 ► ORBX ► User Documents ► Versions Then Launch the FTX Central control panel and navigate to the scenery you wish to reinstall and click Install Click here for an example of FTX Trees and Global Base Click here for an example of the Orbx Libraries
October 30, 20178 yr May I ask: what could possibly corrupt the terrain.cfg? I had an terrain.dll crash recently and I have no idea what could have caused this. Are there any drawbacks regarding the workflog Elaine proposed? How do sceneries using the add-on.xml variant go along with a rebuild of the terrain.cfg? Any culprits there? In my case, I started to add an "layer=xxx" entry to all my addon sceneries added via the add-on.xml version to keep them below the ORBX stuff. Anything to consider in such a setup? Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
October 30, 20178 yr Author Thanks very much Elaine! [email protected], GTX960 2GB, 8GB RAM, 120GB SSD, 1TB HDD, Windows 10 P3D v3, AS A320/21, ORBX Global and Europe, ASN, HDE Cloud and Sun Textures, Chaseplane, vPilot (earlier version due model matching), WOAI for model matching (no AI in-sim)
October 30, 20178 yr 9 hours ago, AnkH said: May I ask: what could possibly corrupt the terrain.cfg? Hello Any Add On that modifies the terrain.cfg file can possible cause a corrupt "terrain.cfg" Basically sometimes stuff just gets messed up. At worst Prepar3D will not launch throwing out all types of errors. One of the lighter symptoms of a corrupt terrain.cfg file would be patches of water where land is supposed to be. For Orbx Scenery you can just delete this file, Launch and shut down Prepar3D, then launch FTX Central and that's it sorted. For other Scenery Add On's like UTX which I'm pretty sure also modify this file, I don't use this Scenery so I am not sure if there is a Control Panel like Orbx Central that will automatically Insert these entries back again, that i don't know. 9 hours ago, AnkH said: I had an terrain.dll crash recently and I have no idea what could have caused this With Prepar3D v3 using high Scenery \ Mesh settings would cause this among other things, In a lot of causes setting the Mesh to 5 and lower via Prepar3D > Options would fix this. With Prepar3D v4 its hard to know because different users are claiming x, y or z have resolved this terrain.dll error, Like removing an overclock, updating drivers, refreshing the scenery.cfg and the terrain.cfg file and so on Some folks recommend refreshing the terrain.cfg file as a process of elimination because it is a small and quick step to try, and of course additionally to this lowering all your Settings and then test 9 hours ago, AnkH said: I started to add an "layer=xxx" entry to all my addon sceneries added via the add-on.xml version to keep them below the ORBX stuff. Anything to consider in such a setup? All your 3rd party scenery Airports and Photo scenery (non Orbx) need to be Above the FTX entries, Only for best results of course
October 31, 20178 yr 4 hours ago, Poppet said: Any Add On that modifies the terrain.cfg file can possible cause a corrupt "terrain.cfg" Basically sometimes stuff just gets messed up. At worst Prepar3D will not launch throwing out all types of errors. One of the lighter symptoms of a corrupt terrain.cfg file would be patches of water where land is supposed to be. For Orbx Scenery you can just delete this file, Launch and shut down Prepar3D, then launch FTX Central and that's it sorted. For other Scenery Add On's like UTX which I'm pretty sure also modify this file, I don't use this Scenery so I am not sure if there is a Control Panel like Orbx Central that will automatically Insert these entries back again, that i don't know. After running FTX Central, I cycle each of the UTX configurators (USA/EU/Canada) by going to the Terrain menu in each configurator. I disable UTX using the "Quick Ultimate Terrain Enable/Disable" menu option, then immediately re-enable it. This makes sure the UTX terrain.cfg entries are rewritten in case they were overwritten/corrupted by FTXC or another installer. The most common symptom of an ORBX conflict (for me anyway) was dry land where lakes and oceans should appear. Regards Bob Scott | President and CEO, AVSIM Inc ATP Gulfstream II-III-IV-V Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090 Samsung 55" JS8500 4K TV@60Hz, 3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090 Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus, TM TCA Officer Pack, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case
October 31, 20178 yr 7 hours ago, Poppet said: All your 3rd party scenery Airports and Photo scenery (non Orbx) need to be Above the FTX entries, Only for best results of course Ok, that's diametral different from what I used to have since my FSX days and also FTX Central default settings. I know you can adjust the entry point of FTX, but so far I used FTX Central "out of the box" and like this, it always puts everything from ORBX back on top of the scenery library (with the exception of the global stuff, of course). You are now telling me that for example the Aerosoft Airports have to be on top of the ORBX stuff such as the ORBX Libraries etc.? Really? Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
October 31, 20178 yr Hello When you launch the FTX Central control panel this will check and arrange the FTX entries Only for you, In some case you will just need to pop into the Library Insertion point tool and arrange the OpenLC below the FTX Airports and Regions and so on but usually all will be good by default If you have other non Orbx Scenery, they recommend the following scenery order 1) 3rd Party Airports and Photo Scenery 2) Orbx Libraries 3) FTX Airports 4) FTX Regions 5) And so on............ If you are Installing scenery using the add-on.xml method, these will be fine as they will stay at the Top of your scenery library Using the old way where you can move Scenery up & down, well these non Orbx Scenery's will need to be moved Above all of FTX stuff I done a Basic write up about Troubleshooting Prepar3D v4 & Orbx, Click here and have a peep at Correct Scenery order for Orbx there is also an additionally link at the bottom of that paragraph with a more In-depth look at the correct scenery Order.
October 31, 20178 yr 9 hours ago, w6kd said: After running FTX Central, I cycle each of the UTX configurators (USA/EU/Canada) by going to the Terrain menu in each configurator. I disable UTX using the "Quick Ultimate Terrain Enable/Disable" menu option, then immediately re-enable it. This makes sure the UTX terrain.cfg entries are rewritten in case they were overwritten/corrupted by FTXC or another installer Good Information, Thanks Bob
October 31, 20178 yr 15 minutes ago, Poppet said: I have done a Basic write up about Troubleshooting Prepar3D v4 & Orbx, Click here and have a peep at Correct Scenery order for Orbx there is also an additionally link at the bottom of that paragraph with a more In-depth look at the correct scenery Order. Ok, great. I will try to rearrange my scenery.cfg according this guide then. Means I had the ordering wrong all the time and did not even notice it ;-) Thanks for the heads up! Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
November 1, 20178 yr Update: I now adjusted my FTX Central settings as outlined in the link from Elaine. All my addon sceneries now above the FTX stuff etc. And guess what? Nothing changed. I am happy, at least the moving around did not break anything and I have now the correct order. Greetings, Chris AMD Ryzen 7 9800X3D, 2x32GB DDR5 6000MT/s RAM, MSI RTX 4090 Ventus 3X, Windows 11 Home, MSFS2024
Archived
This topic is now archived and is closed to further replies.