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

 

I wish you could make this aural warning optional, or maybe just a text warning: It is useful, but very annoying when I know a plane pushes the limits of my system, but I can't enjoy it because all I get is a 'ding' every ten seconds because FSX is too idiotic to use more than 4 GB VM. 

I wish you could make this aural warning optional, or maybe just a text warning: It is useful, but very annoying when I know a plane pushes the limits of my system, but I can't enjoy it because all I get is a 'ding' every ten seconds because FSX is too idiotic to use more than 4 GB VM.

 

It is optional in all versions since 4.84 in July 2012! Simply defaulted on. Just turn it off in the INI file. Don't you read any documentation? It's also mentioned much earlier in this very thread. Why pick out a very old post  (nearly 18 months ago now!) to quote without reading further?

 

Pete

Well now that this topic is bumped, I can only set pre rendered frames to 1 in my Nvidia panel. Why can't I select 0? I have the latest drivers