Sign in to follow this  
TrevorS

"Out of the blue" OOM warning sounds when changing views

Recommended Posts

I've never had this problem before. I have the PMDG 777 and FS Labs concorde and have always changed views continuosly between VC and spotview.

All of a sudden now, when I change views in these two aircraft, I get the chime that I am low on VAS and I see a significant drop in the VAS ( I am using FSUIPC to monitor VAS).

What can be the cause of this?

Assistance to solve this one would be greatly appreciated.

Regards

Trevor

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

PMDG has some excellent advice in the PMDG 777 Intro Guide on VAS.  When you run out of VAS, it means your settings are too high for your FSX.cfg AND display driver settings.  Real weather (especially when nasty) and photo scenery or commercial scenery and high Autogen settings will also speed up the loss of VAS.  Most of the time OOM's occur at the end of the flight while landing at a commercial airport like FSDT's, FlightBeams, Taxi2Gate, etc. 

There are tons of topics on OOM's and there are no other solutions other than the above until FSX goes to 64 bit (which will never happen). 

Topic moved to CTD Forum.

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hi Jim

"None of the above" !!

No settings have been changed. No change of drivers. No weather. Default scenery. OOM warning occurs within the first minute as soon as I change views.

 

This is a SUDDEN problem. Never had it before. That's why I have posted. It has nothing to do with my settings - they have worked OK for years.

 

Trevor

Share this post


Link to post
Share on other sites

I would run Process Monitor as configured on Page 17, AVSIM CTD Guide (see link in my signature).  This will tell you all that is running and loading during the flight.

I'll send this topic back to the FSX Forum.  Thought you were getting an actual crash.

Best regards,

Jim

Share this post


Link to post
Share on other sites

What is so weird is that this is only happening with PMDG 777, PMDG 737 and FSLabs concorde.

The default aircraft are OK as well as AS A320, Level-d 767, CS 707/727

I have an nvidia GTX 1060 6Gb card using the  376.33 driver.

 

???????

Trevor

Edited by TrevorS
to add info

Share this post


Link to post
Share on other sites
22 minutes ago, TrevorS said:

What is so weird is that this is only happening with PMDG 777, PMDG 737 and FSLabs concorde.

The default aircraft are OK as well as AS A320, Level-d 767, CS 707/727

I have an nvidia GTX 1060 6Gb card using the  376.33 driver.

 

???????

Trevor

Those are "lighter" payware aircraft. PMDG and FSLabs are FAR MORE demanding in FSX in terms of VAS usage. Near killing!

Share this post


Link to post
Share on other sites

I understand, but you are missing the point.

Two days ago the PMDG aircraft did not have this problem!

 

Trevor

Share this post


Link to post
Share on other sites

Something did change and it will take a process of elimination to find it. First place I would check is your "windows update" and the "uninstall programs" folders for anything that got installed/updated recently. Are you on Windows 10? It has a nasty habit of upgrading drivers without telling you and this could be your problem. If you don't find anything suspects in those places I would start disabling addons and external programs one by one to see if you can find a culprit. That's all I can think of for now.

Ted

Share this post


Link to post
Share on other sites

Do you have an Nvidia video card? Try installing the 376.33 drivers, do not run windows update after because it will install the broken vas leaking .53 version

 

All Nvidia drivers after .33 for me, leak vas, even if you see your vas usage is not approaching 4gb, the sim still gets an OOM. There is some vas leak bug that Nvidia has ignored and I doubt they will fix it since they are concentrating on making the new card work good in DX12, not DX9 or DX10.

Share this post


Link to post
Share on other sites

Did you check your virtual memory? sometimes it changes because of some dark reason and then this might happen to. I have it at 3072 Mb and then I don't get problems but before a while it went down to 1000Mb and with some troubles. Changing views with heavy addons creates a sudden increase in virtual memory.

Herman

Share this post


Link to post
Share on other sites

Good point.  This should always be set to system managed size.  Anything else and you will get into trouble with FSX.

Share this post


Link to post
Share on other sites

Thanks for all the responses everyone. I still cannot determine what suddenly changed.

Using PE, I see that when FSX opens with a default flight at default airport, the VAS usage is already 3.1 to 3.3 !!!!!

1.   Can someone please tell me what the VAS should be at start up

2.   How do I fix this problem. Everything on the sim is default except the planes. My settings are all medium. Using a GTX 1060.

3.   Should I uninstall and re-install FSX. Will this help??????

4.   HELP plz!!!!!!!!!!!!!!

 

Trevor

Share this post


Link to post
Share on other sites
31 minutes ago, TrevorS said:

Thanks for all the responses everyone. I still cannot determine what suddenly changed.

 

You haven't confirmed or said what nVidia driver you're using as asked by 777300lrf a few posts up. A lot of people had that driver update by Windows not realizing it and caused VAS issues.

Share this post


Link to post
Share on other sites
32 minutes ago, cmpbellsjc said:

You haven't confirmed or said what nVidia driver you're using as asked by 777300lrf a few posts up. A lot of people had that driver update by Windows not realizing it and caused VAS issues.

He did in post #5.  It was my first thought too until I saw this.

On ‎2017‎-‎03‎-‎26 at 0:49 PM, TrevorS said:

I have an nvidia GTX 1060 6Gb card using the  376.33 driver.

Sorry Trevor.  Wish I could help. (I have P3D, so I can't get a default benchmark for you)

Share this post


Link to post
Share on other sites

 

2 minutes ago, netshadoe said:

He did in post #5.  It was my first thought too until I saw this.

 

Yep, I missed that.

Share this post


Link to post
Share on other sites
3 hours ago, TrevorS said:

Using PE, I see that when FSX opens with a default flight at default airport, the VAS usage is already 3.1 to 3.3 !!!!!

What's a PE?  If you are using the FSUIPC utility to monitor your VAS (you said you were in your OP), then 3.1 to 3.3 is how much VAS you have remaining, not the amount of VAS used.  So, you have almost 4GB's of VAS remaining when you open up FSX with your default flight.  Very good!  Do not see your problem.  If you are near running out of VAS, the FSUIPC utility will show 47500 or lower, meaning you have about 475 MB's left.

If you used the AVSIM CTD Guide to set up your FSUIPC utility to monitor VAS (page 16), it will provide you with a further explanation.  You should have checked that you want a normal log file created when you run FSX.  When you shutdown FSX, go to the Modules folder and open up FSUIPC.txt (this is the log of your last FSX session).  It will show you how much VAS you had at startup and how much you had when you finished the flight. 

Here is my last fsuipc log -

Spoiler

********* FSUIPC4, Version 4.962 (8th February 2017) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
fsx.exe version = 10.0.61637.0
Reading options from "G:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 10
Module base=16DC0000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
        0 System time = 14/02/2017 12:07:25
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.61637.0
        0             api.dll: 10.0.61637.0
        0        controls.dll: 10.0.61637.0
        0      fs-traffic.dll: 10.0.61637.0
        0             G3D.dll: 10.0.61637.0
        0        language.dll: 10.0.61637.0
        0            sim1.dll: 10.0.61637.0
        0        visualfx.dll: 10.0.61637.0
        0         weather.dll: 10.0.61637.0
        0          window.dll: 10.0.61637.0
        0 ----------------------------------
       15 Trying to connect to SimConnect Acc/SP2 Oct07 ...
       31 FS path = "G:\FSX\"
       93 LogOptions=00000000 00000001
       93 -------------------------------------------------------------------
       93 ------ Setting the hooks and direct calls into the simulator ------
       93 --- CONTROLS timer memory location obtained ok
       93 --- SIM1 Frictions access gained
       93 --- FS Controls Table located ok
       93 --- Installed Mouse Macro hooks ok.
       93 --- Wind smoothing fix is fully installed
       93 --- G3D.DLL fix attempt installed ok
       93 --- SimConnect intercept for texts and menus option is off
       93 --- All links checked okay
       93 -------------------------------------------------------------------
       93 SimConnect_Open succeeded: waiting to check version okay
       93 Trying to use SimConnect Acc/SP2 Oct07
       93 Opened separate AI Traffic client okay
     4703 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
     4703 Initialising SimConnect data requests now
     4703 FSUIPC Menu entry added
     4718 G:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     4718 G:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
     4968 Monitor IPC:024C (S32) = 3592760
    14890 Monitor IPC:024C (S32) = 3505568
    24890 Monitor IPC:024C (S32) = 3492520
    34890 Monitor IPC:024C (S32) = 3476264
    55015 Monitor IPC:024C (S32) = 3486428
    58765 Weather Mode now = Theme
    58765 C:\Users\JimY\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
    65015 Monitor IPC:024C (S32) = 3475964
    78953 Monitor IPC:024C (S32) = 3474564
    84953 Monitor IPC:024C (S32) = 3470192
   111609 G:\FSX\SimObjects\Airplanes\FA-18\FA-18.AIR
   115015 Monitor IPC:024C (S32) = 3375308
   125093 Monitor IPC:024C (S32) = 3374584
   135078 Monitor IPC:024C (S32) = 3381336
   145140 Monitor IPC:024C (S32) = 2828092
   155140 Monitor IPC:024C (S32) = 2595060
   164656 User Aircraft ID 1 supplied, now being used
   164968 Monitor IPC:024C (S32) = 2219348
   165421 System time = 14/02/2017 12:10:11, Simulator time = 12:07:31 (20:07Z)
   175000 Monitor IPC:024C (S32) = 2231408
   175484 Starting everything now ...
   176796 Advanced Weather Interface Enabled
   184984 Monitor IPC:024C (S32) = 2263516
   195015 Monitor IPC:024C (S32) = 2261612
   205031 Monitor IPC:024C (S32) = 2264428
   215062 Monitor IPC:024C (S32) = 2251180
   225031 Monitor IPC:024C (S32) = 2176256
   235093 Monitor IPC:024C (S32) = 2185868
   245093 Monitor IPC:024C (S32) = 2306412
   255109 Monitor IPC:024C (S32) = 2469188
   265140 Monitor IPC:024C (S32) = 2494796
   275156 Monitor IPC:024C (S32) = 2494768
   285171 Monitor IPC:024C (S32) = 2482600
   295203 Monitor IPC:024C (S32) = 2559056
   305203 Monitor IPC:024C (S32) = 2552364
   315218 Monitor IPC:024C (S32) = 2549356
   325250 Monitor IPC:024C (S32) = 2557460
   335250 Monitor IPC:024C (S32) = 2557424
   345281 Monitor IPC:024C (S32) = 2557724
   355296 Monitor IPC:024C (S32) = 2552148
   365328 Monitor IPC:024C (S32) = 2489516
   375359 Monitor IPC:024C (S32) = 2490696
   385359 Monitor IPC:024C (S32) = 2467916
   395406 Monitor IPC:024C (S32) = 2551432
   405406 Monitor IPC:024C (S32) = 2466912
   415406 Monitor IPC:024C (S32) = 2464944
   425468 Monitor IPC:024C (S32) = 2444048
   435468 Monitor IPC:024C (S32) = 2450680
   445500 Monitor IPC:024C (S32) = 2443044
   455531 Monitor IPC:024C (S32) = 2173648
   465562 Monitor IPC:024C (S32) = 2107472
   475593 Monitor IPC:024C (S32) = 2109624
   485593 Monitor IPC:024C (S32) = 2104908
   495609 Monitor IPC:024C (S32) = 2069860
   505656 Monitor IPC:024C (S32) = 2075208
   515687 Monitor IPC:024C (S32) = 2074252
   525718 Monitor IPC:024C (S32) = 2077184
   535750 Monitor IPC:024C (S32) = 2072088
   545765 Monitor IPC:024C (S32) = 2071712
   555781 Monitor IPC:024C (S32) = 2073356
   565796 Monitor IPC:024C (S32) = 2073440
   575812 Monitor IPC:024C (S32) = 2068644
   585843 Monitor IPC:024C (S32) = 2068680
   595859 Monitor IPC:024C (S32) = 2065556
   605906 Monitor IPC:024C (S32) = 2059164
   615890 Monitor IPC:024C (S32) = 2059184
   625906 Monitor IPC:024C (S32) = 2062108
   635937 Monitor IPC:024C (S32) = 2073060
   645984 Monitor IPC:024C (S32) = 2061640
   656000 Monitor IPC:024C (S32) = 2052244
   659062 Sim stopped: average frame rate for last 482 secs = 27.3 fps
   659062    Max AI traffic was 116 aircraft (Deleted 0)
   665109 System time = 14/02/2017 12:18:30, Simulator time = 12:15:44 (20:15Z)
   665109 *** FSUIPC log file being closed
Minimum frame rate was 14.4 fps, Maximum was 30.0 fps
Minimum available memory recorded was 2004Mb
Average frame rate for running time of 494 secs = 27.1 fps
G3D fix: Passes 24961, Null pointers 0, Bad pointers 0, Separate instances 0
Maximum AI traffic for session was 116 aircraft
Memory managed: 234 Allocs, 234 Freed
********* FSUIPC Log file closed ***********

Note at the end of the log, it shows me the avg FPS, max AI loaded, min fps and max fps, minimum avail memory recorded (2004 MB's), etc.  I usually save these logs and save them with something like - KDCAKLAS_FA18_ASN_MyTraffic_GEX_FSDT_KLAS (this is not the actual file name for the log shown in the Spoiler).  If I don't save it, then it will be overwritten when I restart FSX.  Sometimes I will just save the information at the end of the log.  It provides some very valuable and useful information.

3 hours ago, TrevorS said:

Should I uninstall and re-install FSX. Will this help??????

You should never ever uninstall/reinstall FSX without first deleting, moving, or renaming your FSX.cfg, restarting FSX and letting the config rebuild.  You can also delete, rename, or move your scenery.cfg and it will be rebuilt too.  This pretty much brings you back to the default configuration depending on what you have installed.  The experts tell me that renaming your FSX.cfg is equal to a complete reinstallation of FSX.

So, based on the info you provided, you have no problems.  Your sim is running great!  If you want even more FPS and VAS, I recommend getting GEX.  GEX replaces your default textures and are optimized.  I gained about 100 FPS by installing GEX as I usually see 200 fps with a default aircraft at a default airport with the default textures and not touching the sliders in the FSX settings.  I install GEX and the fps pop up to 300 fps (not steady but it reaches that amount).  But no one wants to fly with a default config as those settings are totally unrealistic.

Hope this helps.

Best regards,

Jim

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this