bob34 Posted October 25, 2015 Share Posted October 25, 2015 Hi everyone. After an afternoon of troubleshooting CTD's in v3 when I begin my approach to Aspen (default scenery), disabling FTX Global Base enables me to fly in the area again. Re-enable and I get the CTD. I've disabled the libraries, but that wasn't the culprit. The quickest way for me to get the error is load up a flight at KEGE. It CTD's while the Loading Terrain progress bar is in progress. Type of aircraft makes no difference, time of day makes no difference, Terrain texture detail makes no difference. Denver area and Colorado Spring work fine. It seems the Eagle area is where the issues are. Anyone else encounter this? Fix this? For staff - here's the Diagnostic Reporter Code: otadf2e437f6ec99799eee59571175e5d9 System specs below and let me know what else I can provide. Thanks, Bob Donovan Order # FSS0286565 CPU: AMD FX8350 - no overclock RAM: 8gb Vid: Nvidia GTX 970 HDD: Samsung 850 SSD FTX Global Base with no additional landclass or mesh. Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 25, 2015 Share Posted October 25, 2015 Welcome. Your scenery.cfg file would suggest that you have a very large number of other developers' products installed? Is is not possible to "disable" global base, can you clarify what you do to disable it? Can you view the Windows error report and see what is causing the "CTD"? Thank you. Link to comment Share on other sites More sharing options...
bob34 Posted October 25, 2015 Author Share Posted October 25, 2015 Ni Nick. Thanks for responding. I do in fact disable global base which clears up the error at KEGE / ASE and further west to Grand Junction. -> Interesting, Boulder and Denver do not get the CTD. <- To disable Global Base, I am going in the library from the world/scenery library menu (from a safe airport) and un-checking Global Base files. This clears the error up when I switch back to these airports. The first time I saw the error was on a flight from KMSP to KASE and I CTD's about 15nm NE of Aspen. It's been a day of troubleshooting since. (this pic has "base" checked, but I meant to uncheck it for the screenshot.) Here's the Windows Report: Problem signature: P1: Prepar3D.exe P2: 3.0.10.14945 P3: 560b4abe P4: g2d.dll P5: 3.0.10.14945 P6: 560b4b9c P7: c0000005 P8: 000e00e6 P9: P10: Hope that helps. Bob Link to comment Share on other sites More sharing options...
Nick Cooper Posted October 25, 2015 Share Posted October 25, 2015 It may not make any difference but the OLC scenery library entries should be just above the Bathymetry entry. You might use the FTX Central Insertion Point tool to do this. Apart from these, the rest of FTX Global is a set of replacement textures and cannot be easily removed. The other small change that it makes is to increase the amount of autogen, you might try turning the setting down a little. A check of Google shows that the g2d.dll error seems to be almost always connected to a scenery addon. Global is not a scenery addon in the same way that airports are but you have a myriad of scenery addons from various developers, I fear I can't be of much more help. Link to comment Share on other sites More sharing options...
bob34 Posted October 25, 2015 Author Share Posted October 25, 2015 Ok Nick. Thank you. First I'll try reducing autogen and maybe that's the silver bullet. If not, I'll keep checking/un-checking down the list. You're right, I have a ton of add-on scenery and some if it is getting old. No doubt something's colliding and causing a CTD. I was taking a shot in the dark that someone else might have encountered this before. I'll report back to see if I can nail it to an exact add-on or setting. Cheers. Link to comment Share on other sites More sharing options...
bob34 Posted October 26, 2015 Author Share Posted October 26, 2015 A reinstall of Global Base fixed the problem. Who knows what it could have been, but it was a stubborn problem as I disabled each of my software packages without success. It's fixed, I'm happy. Bob Link to comment Share on other sites More sharing options...
bob34 Posted October 26, 2015 Author Share Posted October 26, 2015 Problem came back today. Santa Fe and Albuquerque too. Something along that longitude line. Disabling Global Base makes the problem go away. Enabling it, and CTD loading Terrain. I let FTX central re-order the scenery priority. Is there something along that longitude line in the scenery that could cause airports to the east to be fine, but airports on and west to fail with Base enabled? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.