Prepar3D Debug Level / LOG files stored?

[Akila 39]

I have noticed every time I enable or disable some 3rd party scenery my P3D crashes

as soon as it tries to load the default flight (after building the Scenery DB progress Bar)

(it mainly happens when I enable/disable UTX via the UTX setup tool)

it's like it can't compile the Scenery DB as it remembers the last DB before I enabled/Disabled the scenery.

the only way around it is to reboot my computer then everything is fine.

 

note: that it only happens if I already ran P3d once without rebooting my machine, then after closing P3D I do the scenery change and try starting P3D again.

if I reboot my machine, and never ran P3D after the reboot then I can change the scenery and it would be ok.

I just can't change scenery twice without rebooting my computer 1st.

 

the crash is in the form of having this Windows popup window giving me the option of "close Prepar3D? or "Search for on line solution"

my question is how do I enable P3D in debug level mode and where are the log files of P3D stored?

 

details from the pop up window

Problem Event Name:	APPCRASH
 Application Name:	Prepar3D.exe
 Application Version:	1.3.3708.0
 Application Timestamp:	4f516cc9
 Fault Module Name:	g3d.dll
 Fault Module Version:	0.0.0.0
 Fault Module Timestamp:	4f516d2d
 Exception Code:	c0000005
 Exception Offset:	0003a49a
 OS Version:	6.1.7601.2.1.0.256.4
 Locale ID:	1037
 Additional Information 1:	0a9e
 Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
 Additional Information 3:	0a9e
 Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
 http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
 C:\Windows\system32\en-US\erofflps.txt

 

This is from the Eventview:

Faulting application name: Prepar3D.exe, version: 1.3.3708.0, time stamp: 0x4f516cc9
Faulting module name: g3d.dll, version: 0.0.0.0, time stamp: 0x4f516d2d
Exception code: 0xc0000005
Fault offset: 0x0003a49a
Faulting process id: 0x2b8
Faulting application start time: 0x01cd3cc272e13d60
Faulting application path: E:\Lockheed Martin Prepar3D\Prepar3D.exe
Faulting module path: E:\Lockheed Martin Prepar3D\g3d.dll
Report Id: bade8724-a8b5-11e1-987f-002354f343aa

[Zeus67 15]

I suggest you post the same info in the official P3D forums, they may have some ideas about what to do.

[Akila 39]

I did, no answer from there. that is why I posted it here as well.

[la-180 8]

Joel, your eventviewer is showing a g3d.dll error. If you do a search for that here or on any of the major forums, you'll find hundreds of posts about this.

 

Usually turning the autogen or scenery sliders back a notch or two will resolve this. However, I also found that by copying my fsx.xfg and renaming it to p3d.cfg and putting it in the right place, I was able to get rid of the g3d.dll error in P3D.

 

Hope this helps.

Jack

[Akila 39]

Hi Jack. thanks for your reply, however none of those issues are

related to mines.

if you read carfully my post you will see it is only if I loaded P3D once and then changed the scenery (activated/deactivate) externally and reload P3D again.

the issue is only valid if I loaded P3D before I changed the Scenery, if I reboot the machine then everything is fine.

My question was not really on getting the help on my Issue, but how to enable Debug logging and where the log files are stored.

I belive I'll be able and debug it myself, I just need to know where to find the log files.

[FSMP 95]

g3d.dll errors are a know issue with both FSX & P3D.

 

Untill such time that Lockheed finds the cause, and corrects the code to stops these errors in P3D, there is a temporary solution.

 

Install FSUIPC (lastest version for P3D),

This will traps, and prevents most g3d.dll errors, allowing the sim to continue running.