C310 and Beech99 have no flap and gear sounds. The737-300 flap sounds are intermitent. Clicking directlyon the .wav files reveals those are OK. Turning chaton or off does not make a difference. System is Windows XPon an Acer Athlon 64. Any ideas?Tom

>C310 and Beech99 have no flap and gear sounds. The>737-300 flap sounds are intermitent. Clicking directly>on the .wav files reveals those are OK. Turning chat>on or off does not make a difference. System is Windows XP>on an Acer Athlon 64. Any ideas?Are the corresponding sound files actually referenced anywhere in the corresponding files? Sounds are generally not by default mapped properly. Rather, aircraft maintainers need to map proper sounds manually. So, you may want to check the XML files in order to see if there is obviously something missing.

The XML files properly reference the sound file paths. Also,clicking directly on flaps.wav and gear.wav generates the proper sounds with Windows media programs. The strange thing is that other sounds, such as enginewhine, startup crancking with c310, etc. all seem to functionproperly, It seems as if the gear key (g and G) or the[ ] flap keys will not enervate the corresponding wav files.I also tried all levels of sound. What files are involved in sounds or keyboard bindings? Perhpas one may be corrupt. Or, couldsound hardware settings on the pc be at fault? I've triedto modify acceleration levels.Tom

Are there any OpenAL/Sound related warning/error messages displayed in the shell window?

The only warning/error messages are:WARNING: ssgLoadTexture: Cannot determine file type for "D:/FlightGear/data/FOO'Error: connect() failed in make_client_socket()SG_IO_OUT socket creation failedVOICE: no connection to 'localhost:1324'Note: All other sounds on pc applications and within FG {engine, chat, main gear touch-down rumble, nose-gear on runway noise, etc. function well.I've tried to replace sound related folders and filesfrom ealier FG versions to no avail. The 737 flapsand gear sounds are ok except the flap sound sometimesmisses a tick.A real mystery!!!Tom

Well, the connect() error message seems related to the new integrated support for the festival TTS engine, obviously the corresponding subsystem is running even though you don't have festival running on localhost-but it should not affect the other sounds either. Have you actually tried running FlightGear with an increased log level?

Turned logging to info level and seemed to findsomething suspicious."Playing audio after 14.98 seconds""Stopping audio after 0.8 seconds"The stopping figure appears to be a constant 0.8 butthe playing varies anywhere from say 14 to 39 and above.With the 737 where the flaps sound is audible, the timesare fractional such as .3 and .2 or even .03 and .02.Tom