I posted a reply to another thread and thought it might be something that I could share.There is an issue that has been described as being annoying and I would not have discovered it unless I read a post by aceridgey in which he states that he could not silence the morse sound no matter what he did. It is a simple fix and the remedy is to make the right NAV radio silent by swithing to an unused frequency, that is the fix for the time being until it is fixed. I checked to see if both NAV radios (Right and LEFT) were tuned to the same ILS, and they were not. I then selected a freq. of 109.50 and switched it to the ACTIVE on the left NAV radio (Pedestal) and heard the morse code when the 1-NAV selector was pressed (lit) and the morse beep stopped once I depressed it. I did the same from the right seat where I switched the same freq. 109.50 into the ACTIVE slot on the right side. I depressed all the 1-NAV-2 selectors (which were lit) yet the morse beeping continued until I switched the ACTIVE freq. with the STANDBY on the right side. One should only hear the morse signal when the MIC SELECTOR switches are pressed, in this case the morse sound is heard even with the switches depressed.This is a minor issue but a major annoyance and I hope that it relieves some stress for some of you that have been trying to resolve this issue.

Yeah I've now started to have those issues as well. But since I never really get on the sim that much anymore, this might come in handy to figure out if and when it happens again, thanks! Also anyone using the saitek radio panel?. I've noticed a small issue where the radios show 0.00 when switching from com1 to com2 for example. Anyone noticed this?

In trying to solve your problemlast week, I activated the ILS by pressing the mic selector and got the annoying tone. Now for some reason, my LD767 has that annoying morse code everytime that I can't get rid of - no matter what frequency it is on. I deslected every mic button, yet I stll get it. I finally got rid of it by turning off the ILS freq by getting a "----" in that freq field.Go figure!

Paul,Try pressing Crtl+1,2,3 and 4 I have read that it might work.

This is usually fixed by opening whatever plane you use for the default, I use the 172, going to the audio panel on the radio stack, and checking that only the Comm1 is lit (and the marker beacons if you want them), then save it.

Hello,do you by any change use Ezdok with camera's assigned to CTR-1, CTRL-2, etc?In that case, make sure that those keyboard assignments are removed in the options, controls menu in FSX, because they turn the nav audio's on and off.Furthermore, (bug in FS), CTRL-4 cannot be removed via options, controls. You have to assign this to a unimportant function, like tail hook or something.Hope this helps,Wijnand (EHBK)

Edited February 18, 201214 yr by wijnand

Paul,Try pressing Crtl+1,2,3 and 4 I have read that it might work.

I think it worked for me! I deleted any FSX control assigned to ctrl+1/2/3/4 and I didn't get it last night!Will keeep testing

That is great news Alex, I was playing around with the Ctrl/number keys and thought I had created the same issue as I could not silence the beeping. I finally did silence the morse beeping after a while.Paul replied to my support ticket regarding the beeping and said if confirmed as a bug that it will be fixed in the next SP or a future one.

I think it worked for me! I deleted any FSX control assigned to ctrl+1/2/3/4 and I didn't get it last night!Will keeep testing

Bingo!I had this issue after assigning EZDok cameras to ctrl-1,2, etc

Edited February 19, 201214 yr by ZachLW

That is great news Alex, I was playing around with the Ctrl/number keys and thought I had created the same issue as I could not silence the beeping. I finally did silence the morse beeping after a while.Paul replied to my support ticket regarding the beeping and said if confirmed as a bug that it will be fixed in the next SP or a future one.

Bingo!I had this issue after assigning EZDok cameras to ctrl-1,2, etc

Super, I am glad we have solved this together

My problem is that it's the DME ident (ctrl-4) being set to on. Unfortunately, I reassigned ctrl-4 to something else, and I think now I'm stuck with DME ident forever on, unless someone else knows a solution? Maybe there's a config file that can be edited.-Tim Latona

Actually this has come back to bite me, I thought i fixed it with the ctrl+1 ctrl +2 etc but its still here