I am trying to determine the source of a mysterious chime I am getting when flying in FSX. The chime is similar to what one might hear when the seat belt sign is activated, the flight attendant is called, or when an elevator you're waiting for arrives at your floor. The chiming can start anywhere from 30-90 minutes into a flight, and it repeats about every 2 seconds and is generally incessant for 5-15 minutes until an OOM occurs. The chime comes from the headphones or external speakers, and not from the motherboard speaker.

 

I am not looking to engage in a discussion of OOMs, VAS, graphics settings, etc. I am aware of all these issues, and none of the many proposed solutions has worked for me. At this point, what I am seeking is an explanation about what software or hardware might be emitting or causing this chime. If I can determine this, I can then perhaps address the OOM issues in a more specific fashion, as they appear to be related. When it comes to an OOM, the chiming is like the canary in the coal mine.

 

I have not been able to find any posts about such a chime and am at a loss to know what hardware item or software is generating it. I am running no monitoring software that might emit such a chime. And none of my hardware manufacturers is aware of its hardware emitting such a chime. It occurs when flying both simple GA aircraft and complex aircraft such as the PMDG 737NGX.

 

If anyone has experienced this chime in these circumstances or is aware of its source, your input will be greatly appreciated.

 

Thanks,

Robert

You don't have ezdok camera do you ? When that is in edititing mode it makes a repeated chiming noise...

 

-hth

Indeed I do run ezdok, and will explore this further. I've never noticed this as a repeating chime and recall only hearing it when I press the "2" key twice to save a camera setting. But then again, I only knowingly use a small part of ezdoc's features. This is a promising insight well worthy of exploration. If ezdok editing is somehow being activated unbeknownst to me, this might well be causing the chime and - more importantly - draining my system of resources and causing the OOMs. I will check this out and report back.

 

Thanks for the input.

Robert

With latest version of FSUIPC 4.80, Pete Dowson forgot to turn of a warning signal when you are about to run out of memory. This can lead to an app crash such as tho OOMs you are experiencing.

 

Solution is to update to latest FSUIPC module. I believe it is 4.827

Pressing '3' will enter Ezdoks edit mode and cause the repeated chimes you describe.

With latest version of FSUIPC 4.80, Pete Dowson forgot to turn of a warning signal when you are about to run out of memory. This can lead to an app crash such as tho OOMs you are experiencing.

 

Solution is to update to latest FSUIPC module. I believe it is 4.827

 

Er, no I didn't forget to turn it off. It is there to warn of an impending OOM. It isn't the CAUSE of an OOM as you are implying.

 

I did originally put the code in when I was experiencing an OOM, and it helped enormously because i then found out what was doing it. I did forget to remove the code, but later i decided to leave it in because it should prove genuinely helpful to many. What I then forgot to do is document it!

 

I could make the warning optional, but since the consequence of an OOM is os dire I would have thought that a warning would be desirable. I'll remove it if that's what folks want!?

 

BTW, the FSUIPC impending OOM warning chimes are a double beep or whatever at 10 second intervals, not 2. And they are the standard Windows "exclamation" sound, on the current default sound device -- just a pair of "MessageBeeps" in fact. Messages are logged to the FSUIPC log at the same time:

 

**** WARNING! Free memory is very low!

 

Pete

 

Er, no I didn't forget to turn it off. It is there to warn of an impending OOM. It isn't the CAUSE of an OOM as you are implying.

 

Thank you for clearing that up Pete. I did not mean to misinterpret you. I am glad to get the explanation from the right source. I like to get the warning personally so I can cut the resources and avoid the OOM.

 

The question now, is this the sound the poster is hearing before his OOMs ??

The question now, is this the sound the poster is hearing before his OOMs ??

 

A quick check in the FSUIPC4.LOG file would show.

 

Pete

Oops, didn't know about that FSUIPC detail. Nice idea, Pete.

I would wish for a code basis (of the sim) really allowing for the 64bit space though. Stating this because I'm always flying like with two of my planes in e.g. the London area. It works out fine so far, but I can see that VAS being very close to the edge and staying away from it just because I'm flying very modest FSX settings. OT, sorry.

 

The question now, is this the sound the poster is hearing before his OOMs ??

Spot on.

Pete,

 

Thanks for the update....lately, I've been flying the PMDG 737 NGX with FS2Crew (Voice), and landing at complex airports. And out of the "clear blue," I hear this low volume chime. I thought at first it was part of FS2Crew.....so I was about to post a message on their forum.

 

Now I know what it is.

 

So please leave this feature in, or if too may object, give us the option of toggling the chime on/off.

 

This is a nice feature to help us "better tune" our resources to avoid OOM crashes.

 

Bill Clark

I actually get a chime when I spin the Saitek Cessna Trimwheel through more than 360 degrees. I don't use FSUIPC. Would anyone care to comment ?

I actually get a chime when I spin the Saitek Cessna Trimwheel through more than 360 degrees. I don't use FSUIPC. Would anyone care to comment ?

Prob your plane is. If you don't have the latest fsuipc, it would hardly be a OOM warning. Anyway, it is a windows chime, not like a door bell.

 

Oops, didn't know about that FSUIPC detail. Nice idea, Pete.

I would wish for a code basis (of the sim) really allowing for the 64bit space though. Stating this because I'm always flying like with two of my planes in e.g. the London area. It works out fine so far, but I can see that VAS being very close to the edge and staying away from it just because I'm flying very modest FSX settings. OT, sorry.

 

 

Spot on.

This was something I came across some weeks back CP, it works a treat. So Hope Pete keeps it in.

http://forum.simflight.com/topic/71348-oom-warning-given-by-fsuipc/

Well, I've been testing away here and can confirm that the chime I was hearing was indeed generated by fsuipc.The fsuipc.log file confirms this and it otherwise conforms to what Peter says. I was mistaken when I said it occurred every 2 seconds; I guess when it sometimes goes on for 15 minutes it seems like it is ringing every 2 seconds.

 

In any event, the mystery of the chime is now solved. Thanks to those who chimed in, especially Peter.

 

Now, I'd be a happy simmer if I could only solve why I'm plagued by these OOMs, especially when several friends who run essentially the same hardware, essentially the same FSX software, and who use identical settings and tweaks do not encounter them. But that's for another post.

 

Thanks again.

Robert

I don't use FSUIPC at all. And it is indeed a Windows chime, not a doorbell. Suspect it's something in the Saitek support.

Well, I've been testing away here and can confirm that the chime I was hearing was indeed generated by fsuipc.The fsuipc.log file confirms this and it otherwise conforms to what Peter says. I was mistaken when I said it occurred every 2 seconds; I guess when it sometimes goes on for 15 minutes it seems like it is ringing every 2 seconds.

 

In any event, the mystery of the chime is now solved. Thanks to those who chimed in, especially Peter.

 

Now, I'd be a happy simmer if I could only solve why I'm plagued by these OOMs, especially when several friends who run essentially the same hardware, essentially the same FSX software, and who use identical settings and tweaks do not encounter them. But that's for another post.

 

Thanks again.

Robert

Robert, read the link I just posted.

 

I don't use FSUIPC at all. And it is indeed a Windows chime, not a doorbell. Suspect it's something in the Saitek support, but saw this thread and thought it was worth a punt in case anyone else had seen it.

That could be a tricky one to pin down. Not famil with Saitek, so maybe someone who uses the same can help.