• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA Experimental OOM fix (api.dll)

Heretic

Resource contributor
Messages
6,830
Country
germany
The talk about VAS and OOMs in the other thread reminded me of this one.

This "patched"/modded api.dll popped up on Avsim in 2012, but went under pretty quickly. Apparently, the program termination upon reaching 2GB VAS was removed.
See here for the reference thread (cached version to circumvent the dumb guest restriction):
http://webcache.googleusercontent.c...&cd=3&hl=de&ct=clnk&gl=de&client=firefox-beta

A month or so ago, some german flightsimmers were interested in it and managed to get hold of someone still in posession of a patched api.dll. He sent it to me and I uploaded it.

There have not been any conclusive returns of experience with this file (I don't have tested it myself as I don't get OOMs) and it's probably yet another placebo, but if someone runs Acceleration (Not just SP2!) and feels a bit playful, it might be worth trying out.
Or maybe just taking a look at it and debunking its usefulness outright. It would at least help to settle the subject once and for all.

Download:

hxxp://www.mediafire.com/download/9n3v52w9naakybh/api.zip

(xx=tt)

RTFR; no support of any kind, you're on your own; do backups!
 
Yeah... that kind of stuff makes me quite nervous. He hacked out the message and instead allows the program to continue to run after it's run out of memory. Who knows how well or poorly FS will behave at that point.
 
Yeah... that kind of stuff makes me quite nervous. He hacked out the message and instead allows the program to continue to run after it's run out of memory. Who knows how well or poorly FS will behave at that point.
One would likely have a audio-visual presentation of the GIGO effect!
 
When I receive an OOM message I simply ignore it if I am near my destination or an alternate field. One can continue to fly
if one does NOT acknowledge the OOM message and simply bring FSX back to the forefront.

The only problem with that is that textures will no longer load and in some cases instruments may cease to register
but at least you can 'get down' and hopefully save the hours of that flight that would otherwise be lost.

As to this 'fix', I installed it last night with no issues and on three test flights fro KBFI to KPDX where I HAD
been getting OOM warnings I was unable to create that condition again. My VAS remained around 77000
where as before it dropped down to 35000 on one previous flight on that route and on another I received
an OOM error near KPDX but managed to land. I can't explain why those three hops after changing the api.dll
resulted in less VAS usage, compared to the three flights over the same route with the same aircraft
and weather conditions where I had very low VAS readings and the one OOM occurance.

So, I can not comment on the effects of this 'fix' yet. The one thing I did notice was that I had to
reconfirm various previously "Trusted" entries when I went to fly an aircraft for the first time
since changing the api.dll....a bit annoying but tolerable if it allows me to reach an absolute
value of "0" for VAS before bad things happen.

I currently have a Lua script that displays a message when my VAS gets below 500000, just to
give me a 'heads up' before reaching the FSUIPC4 'ding' level. I keep an eye on that when flying
in the OrbX PNW/CRM/NRM areas where I see a heavy load on my system. Using this display
I may be able to determine at what level of VAS the texture load failure occurs as a point of
reference.

Paul
 
Thanks, Paul!


I currently have a Lua script that displays a message when my VAS gets below 500000, just to
give me a 'heads up' before reaching the FSUIPC4 'ding' level. I keep an eye on that when flying
in the OrbX PNW/CRM/NRM areas where I see a heavy load on my system.

Link: http://forum.simflight.com/topic/75637-oom-warning/#entry461708

I've just tested the other method and it works as well: http://forum.simflight.com/topic/75637-oom-warning/#entry461664
 
I use the border at the top left to display my current 'mode' for my FSUIPC4-programmed controllers so I can't
display the VAS using that offset noted in the link to the forum posts. That's why I chose to implement the
display of VAS on one of my existing xml gauges as well as using the Lua display that opens for 2 seconds
when the the VAS is below 500,000 in case the xml gauge isn't in focus at the time.

Paul
 
Are LUA disdplay popups by the unregistered version?

The other method, in any case, is.
 
I'm pretty certain you would need the registered version of FSUIPC4 to have access to the included
Lua library functions. I rely on so many of the features provided by the registered version that I can't
imagine 'flying' without it :)

Paul
 
Back
Top