After moving the Gaugesound.dll over, it's apparent why. . . .Prepar3D doesn't like that file, lol. It's a minor thing really, the airplane, otherwise is perfect. Thanks for the information.That specific gauge contains the custom sound module, as well as the two EDM-700 engine monitors (CHT and EGT).
The reason why it "failed" is that you didn't copy over the GaugeSound.dll file found in the root folder of FSX.
I've removed the dependency for GaugeSound.dll from the sound module, and all projects moving forward will use the new sound module, including the C310R I'm setting up for P3Dv2.x...
. Even all the gauges that are supposed to be clickable are that and the GPSs also work.
Pat, the gauges all work fine, everything is clickable, but that one "gau" file locks it up if I try to load the 310. After what "n4gix" mentioned about the Gaugesound.dll file, I thought I'd give it a try. . .that locked the sim up and gave me a "Fatal Error". So, without the "MilVizC310.gau" gauge all is well.Ed, not sure if it is any help to you but I installed the Milviz C-310R straight into P3D V2 and have had no problems with crashes. The couple of short flights I have done were uneventful actually bordering on boring
I might add that as yet, even though I have downloaded it I have not installed the hot fix.
No I haven't Pat. To be honest, I'm not heavily into systems, Navigation, etc with any airplane I fly. I'm sure there are things I'm missing by not having the custom sound module and gauges but for the type of flying I do. . .they're of little consequence. For all the planes I've installed (with a few exceptions), I've just copied over what I need from the FSX folders.
That's odd. I've had GaugeSound.dll in my P3Dv2 folder since I first installed it with no issues whatever...After moving the Gaugesound.dll over, it's apparent why. . . .Prepar3D doesn't like that file, lol. It's a minor thing really, the airplane, otherwise is perfect. Thanks for the information.
