Tom: okay so far I can't see anything wrong. You did remove/rename the dsd .gau from folder gauges? Doublechecked the gcacalls.ini? To correspond with the file names used in the GCA\calls folder? Dawson's gauge present in folder panel?
I have got my 737 with a purely mechanical install of [Window15] (never mind not consecutive), gauges installed in Vcockpit 01 (also not consecutive), so as to force that type of errors .... but APC greets me just fine, even without dialing in anything via AILA. It's the 15 mile error message, after which it shuts off, as it apparently does on your setup, only without the voices. So, it's very likely something in the areas just mentioned.
Also found a FS9 portover plane (a Connie!), installed the GCA stuff, and all's correct and present.
Post by Tom/CalClassic on Feb 12, 2019 12:41:26 GMT -5
Yes, I made sure to remove the sound gauge from the Gauges folder. In fact, I tried removing all addon gauges from that folder, leaving default gauges only.
OK, I think I might have found a reason, if a bizarre one. It turns out that there is a sound problem in my FSX, and I don't have a clue about it. In all the jets in my FSX folder (default and addon) they have no engine sound in the cockpit, 2D or VC. I have flaps sounds, wind sounds, etc. but no engine sound. In external view, airplane view, and any other view I do have engine sound, but not in the cockpit. All my default piston aircraft (Cessna, DC-3, etc.) do have normal engine sounds, as do all my classic addon aircraft. The voices do not play in any view, BTW. Nor do they play when installed into a plane (like the B307) that does play engine sounds (aliased from the Default DC-3).
So I assume that this anomaly is also causing the voices not to be heard. Very odd. What is more bizarre is that a while back I created a checklist gauge which plays wav files using a similar but older dsd sound gauge and those voices play just fine in a CV-340. AND your gauges (once edited to be FS2004 compatible) and Doug's new sound gauge play just fine in FS2004 on this very same computer!
So it appears this is probably not due to your gauges, but a weird interaction between Doug's new sound gauge and my admittedly flawed FSX installation.
Odd indeed! Maybe try an earlier version of the DSD gauge? This one is fairly recent. On the other hand, my aged FSX SP2 has no problems with it. If memory serves, Doug mentioned somewhere that his new versions had a revised lookup logic especially concerning Win 10. Are you on Win 10? I am...
Tom, Sent you one back! Thanks so much for the 3 files! Works like a charm now. I get both APC and PAR voice. I only got to fly one actual PAR approach during my flying career back in the 80's and that was to the North Bay, Ont. airport which was a joint military/civilian field. I was flying a Piper Aztec from Buffalo, N.Y. and the approach controller asked me if I wouldn't mind a PAR approach as he needed to conduct a minimum number of those approaches per month to stay current I guess. Now I can recreate that flight!
Tom, as it is a problem that may come up with other FSX users, I'd be grateful if we could follow up Doug's suggestion if it isn't too much trouble. In the B737 panel folder I linked earlier is a functioning "Monitor" panel with a "Test" subpanel, to which I have now added a readout of the L:Simconnected variable. It might be instructive to see what you get on your setup. The edited Mon.xml (to go into the Monitor folder) is here:
Post by Tom/CalClassic on Feb 15, 2019 14:06:41 GMT -5
I first tried replacing the fsx.cfg file and that didn't work, but I then noticed that the engine sounds and voices would play if I were looking backwards in the cockpit but not forwards. Aha! It must be something about my sound system. So I then started looking at hardware. I ran the speaker check program and only the front speakers were playing. What was confusing was that the front speakers were connected to the rear speaker jacks, so I reversed them. Now only the rear speakers played. Then after about an hour of plugging and unplugging different cords into different sockets (both computer and speaker), I finally figured out that my Logitek subwoofer/sound center was only outputting sounds to the rear speaker ports. After thinking about replacing the entire sound system, I first tried turning the system off and back on at the little control box, and noticed another button I had never noticed before - Matrix. It was pushed in. After popping it out - all speakers now play, I have engine sound in all planes, and your voices come through just fine.
You mean that's all it was? It's always something...
Thanks for all your help and sorry for being one of those people that complain about a problem with someone's software, only to discover it was a hardware issue that most people would have probably figured out in seconds. Not me...