In the debug txt file these first 2 lines show up

 

Creating systems:
01 02 Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_StarterTruck.wav)

Can't access WAV file: 0 (Sound\PMDG/737NGX/Various/PMDG_737_AirTruck.wav)

 

I looked in the folder /Various and noticed the file names are different

 

PMDG_737_Airtruck_ext.wav

 

and

 

PMDG_737_StarterTruck_ext.wav

 

How can I fix this?

 

-David Lee

-- As a temporary fix I got rid of those error messages by copying the wave files, and renaming them to what the systems are looking for. Any help in figuring out why by default the ngx is looking for the wrong wav files?

How can I fix this?

 

http://support.precisionmanuals.com/kb/a112/important-and-nearly-foolproof-steps-to-running-your-pmdg-product-in-prepar3d-v3.aspx

 

Always best to check the stickies and support pages.

http://support.precisionmanuals.com/kb/a112/important-and-nearly-foolproof-steps-to-running-your-pmdg-product-in-prepar3d-v3.aspx

 

Always best to check the stickies and support pages.

I am using FSX Acceleration, not P3D. I did not find anything in the knowledge base when searching sound or pushback. That link does not apply to FSX?

 

EDIT I think I see now what you mean, but I was not talking about P3D error debugging, rather the 737NGX_debug_log.txt file in FSX\PMDG\PMDG 737 NGX

 

- David Lee

I am using FSX Acceleration, not P3D. I did not find anything in the knowledge base when searching sound or pushback. That link does not apply to FSX? - David Lee

You didn't specify and getting error logging turned on isn't easy, so I had to make an assumption. Just turn error logging off.

You didn't specify and getting error logging turned on isn't easy, so I had to make an assumption. Just turn error logging off.

I added an edit to the post after you replied. sorry.

 

"I think I see now what you mean, but I was not talking about P3D error debugging, rather the 737NGX_debug_log.txt file in FSX\PMDG\PMDG 737 NGX" - David Lee