I installed the Phenom 300 V1.3 (without Navigraph ext) into P3Dv3 and the first time I flew it I had clicks, dings, fans whooshing, "five hundred", etc. Second time and thereafter I no longer get any clicks from pushing knobs, toggles or buttons, no ding when I turn on the seatbelt signs, no fan sounds. I do get altitude callouts (500, 300) and the obnoxious glidescope nag. Engine spooling, landing gear, flaps, exterior sounds all work. Problem seems limited to the interior, the autopilot and dashboard knobs and buttons.

 

Problem persists using the GTN750 or the default G1000 MFD. GTN750 sounds all seem to work properly.

 

The Phenom 100 (also Carenado) does not have sound problems. The sound directories have basically the same files in each so I didn't accidently erase files.

 

Carenado tells me they're working on something and have no timeframe.

 

Any ideas?

I am seeing this in FSX. I even reinstalled the aircraft but still no clicks, whirring, and get this no seatbelt chime! All sounds like the flaps, gear, callouts, seem ok.

P3D V3 provides content error logging by default ... check that error log file to see if you see any issues listed for the Phenom 300.

 

Cheers, Rob.

I am seeing this in FSX. I even reinstalled the aircraft but still no clicks, whirring, and get this no seatbelt chime! All sounds like the flaps, gear, callouts, seem ok.

I can't help with FSX but I got everything working by making a P3Dv2 registry key pointing to my v3 location and making a dummy folder in %appdata%. Reinstalled the Phenom 300 into "v2" ..... "click" "ding" etc.

P3D V3 provides content error logging by default ... check that error log file to see if you see any issues listed for the Phenom 300.

 

Nothing of any substance. Complains about some remarked lines in an XML file I converted from SPB.

My problem turned out to be self-inflicted. It seems there are 2 "glideslope" alarms in the avionics. One in particular had a loud male voice that I found annoying whenever I tried to "duck under" on short final. So I disabled it in FSX/Sound/Carenado/etc. Turns out that if you disable a .wav by changing the name, it causes unintended consequences. Once I restored the name, all was well again. Yet another example of the rule of flightsim that when everything is working, then it stops working. First place to look is the last thing we changed. Pointed out to me by Carenado support, who by the way were very helpful and respond quickly.

My problem turned out to be self-inflicted. It seems there are 2 "glideslope" alarms in the avionics.

I know the obnoxious files you're talking about. I renamed them to xxxxxx.wav.off

Maybe you are seeing the causation I did for the loss of the clicks???

I know the obnoxious files you're talking about. I renamed them to xxxxxx.wav.off

I must be drinking. Renaming the file to ".off" is what caused the problem in the first place. What I wound up doing is running the sound file thru Audicity and lowering the volume to a whisper.