Help!

falcon409

falcon409

Moderator
Staff member
I have run into a real problem and have no idea where it originates or why. Yesterday I decided to load some of my custom scenery for the Southwest Regions, in particular my home airport North Texas Regional (KGYI). It started to load the "terrain data" but only got as far as 17% and CTD. I tried multiple attempts, even to go so far as try other airports close by. . .all failed. I removed the airports from the scenery library and tried again. . .all failed. I moved as far out as El Paso to the west and Pensacola to the east. . .all failed.

There was a recent update to P3D which I had not installed and so I completed that (client only) and also uninstalled the scenery module and all that entails and reinstalled the latest scenery and related "cab" files. I was able to load the default KGYI airport but noticed that the Orbx scenery was not active so I ran FTX Central to correct it. Since that time I have again been unable to load anything in the southwest region (at this time I'm not looking at Orbx as the culprit but that could be an area that gets scrutiny later).

I have activated the "debug" feature within the Prepar3D.cfg file in the hope that this may give me some indication of what. . .or where the problem is. What I need to know, from someone who actually knows for sure, where does the debug report get stored? I've looked everywhere within the P3D file/directory structure and see nothing that appears to be an error report. I'm at a loss as to why this suddenly has popped up. Obviously I haven't tried every single airport in the US to narrow down the offending areas, but I have been flying in the Northeast for quite a while as I help beta test the C-119 and have no problems at all.

Any help would be appreciated.
 
Hi Falcon,

Are there any Windows error reports when P3D crashes? These may provide a hint. Any files that would have been installed just prior to the crashes? Even if you have deactivated the scenery, maybe there was some other type of file corruption, such as a traffic file, altitude file, editing of P3D autogen files.
 
scotth6 said:
Hi Falcon,

Are there any Windows error reports when P3D crashes? These may provide a hint. Any files that would have been installed just prior to the crashes? Even if you have deactivated the scenery, maybe there was some other type of file corruption, such as a traffic file, altitude file, editing of P3D autogen files.
Click to expand...
No, none of that actually. As much as I was hoping to find something simple, it appears that Orbx Landclass could be where the problem lies. I deactivated all Orbx and the scenery file loaded just fine. I then started reactivating each file for the landclass and have hit on one that has taken about 10 minutes and only loaded 22%. That might be one area of concern. still an ongoing process.
 
Fixed. . .Loading 4 specific LC files in the scenery library took approx 30 minutes. The Custom scenery did eventually load once the library was finished, but there was obviously a problem there. I uninstalled the LC portion of Orbx, downloaded and reinstalled it and it appears the glitch, whatever it was, is gone. Now back to the C-119 Beta.:jump:
 
You must log in or register to reply here.
Back
Top