My planes on others installations of Prepar3D are crashing when clicking certain switches. On the testers computers, they are getting crashes that are based on the GaugeSound.dll. Normally this happens on my systems when a sound is missing, but the sound is not missing and is actually heard, followed by a system 'pop' sound and then a CTD crash.

A typical message;

**Problem signature:
Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 1.3.3708.0
Application Timestamp: 4f516cc9
Fault Module Name: GaugeSound.DLL
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 3eb140e0
Exception Code: c0000005
Exception Offset: 00001725
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Another crash on another testers computer;

Problem Event Name: APPCRASH
Application Name: Prepar3D.exe
Application Version: 1.3.3708.0
Application Timestamp: 4f516cc9
Fault Module Name: GaugeSound.DLL
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 3eb140e0
Exception Code: c0000005
Exception Offset: 00001725
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Would this be caused by the location of the GaugeSound.DLL file? For instance, normally, in FS9 and FSX, the GaugeSound.DLL goes in the main primary FS folder. However, perhaps P3D see's this as a module. In FS, we would create a Modules folder and place our DLL's in there. Could it be that we should now be placing the DLL's in a 'new' folder in P3D called Addons/Our Addons? Would this be a normal route to take?

Also, do we have to manually edit in the 'True' setting into the main XML to activate a DLL now? For instance, in FSX, it would ask us if we wanted to use that new DLL. In FS2004, it automatically incorporated the new DLL.

I do not presently have a technology that can activate XML's, so I am hoping this is not necessary.

I hope that what I am doing wrong is easily seen and that Team P3D can show me how this is properly done, which route to take.

Kind regards,

Bill
LHC