NZFF

Hey guys. I'm slowly trying to get back into FS and currently in the middle of trying to setup and test things and got this "Your computer has run out of available memory. Please restart FSX and select different graphics scenery or traffic settings" Now this is what stopped me playing FSX in the first place years ago as I only had 2Gb RAM back (And frankly a donkey system) then but now it's a different system and theoretically shouldn't be giving me this issue.

i3-4130 3.4Ghz
8.00Gb Ram
GeForce GTX 550 Ti 1Gb
Win 7 Ultimate 64bit

Error happened 5 mins out of Taupo, over Ruapehu, default Airbus A321 using ORBX North Island and Active Sky with Ice AI Traffic (Only 3 planes around at the time however). Not sure if theres a setting in either Windows or FSX I have missed or forgotten to setup but hoping someone out there might have an idea...

Normally I run the latest games totally maxed out (Assassins Creed IV, Black Ops 2 etc etc...) but have toned down the FS settings to slightly less than max.

The other issue I get is every few minutes whether taxiing or flying the aircraft suddenly and quite violently lurches to the right. All speeds, all altitudes, tho doesn't affect when autopilot in use...

There's a lot of information around about this, although it isn't something I've ever had with FSX -- Prepar3D is another story, though.

Just bear in mind that this isn't a memory problem, it's a Virtual Address Space problem -- no matter how much ram you have, a 32 bit program like FSX can only access up to 4GB, and it can run into problems anywhere over 3GB. Search for 'FSX VAS'.

Solving this can involve figuring out exactly what is hitting your VAS usage the most, which may mean getting some sort of monitoring tool. However the usual suspects are larger than normal textures -- such as 2048 or 4096 environment, scenery or aircraft textures -- and extra-dense autogen. Having plenty of lovely addons is all well and good, but every time you add something it increases the VAS usage.

Hey Rob. Yeah have been looking at the info on the VAS usage. Not entirely sure the best way to go about playing with those settings. The addons I mentioned are literally (At this stage) The only 3 things I have installed, everything else is bog standard default (And the addons I haven't installed 2048 or 4096 textures so it's still 1024). As it sits right now there's 268Gb free on my prime drive and 133Gb free on my secondary so not sure if that can give me something to play with or not. The fixes (or at least aids) all seem to point to areas and settings I am not very familiar with

Hmm, looking back at your setup, there doesn't seem to be much reason for high usage. When I installed FSX on my 64bit, I had no end of crashes and problems, which I solved one by one just by searching for the appropriate error message, but as I said, OOMs were never a problem.

Maybe a VAS monitor might shed some light on it -- I use Process Explorer.

Here's a good description of the problem.As it points out, it doesn't matter how much ram, system memory, disc space or anything else you have.

It may be that you have some other issue -- in which case, a look at VAS usage when it crashes might show plenty of VAS left, in which case you'd need to look elsewhere.

Just downloaded that programme you mentioned right before refreshing this post. What is it specifically (Columns, numbers etc) am I looking for in there?

EDIT: Scratch that think I found it, Virtual size jumped to 1Gb just on startup alone

omitchell wrote:

QUOTE (omitchell @ Mar 11 2014,12:10 PM) <{POST_SNAPBACK}>

Just downloaded that programme you mentioned right before refreshing this post. What is it specifically (Columns, numbers etc) am I looking for in there?

EDIT: Scratch that think I found it, Virtual size jumped to 1Gb just on startup alone

Ok just reassigned about 11Gb of HDD space to virtual memory. Resized my VAS allocation size and switched from Active Sky to REX (Better load demand for texture files), lets see if this helps... (Failing that I have a monkey wrench to apply to nether regions...) Also loaded an OOM fix I found at Microsoft which alters some values in the registry. AKL-LAX

EDIT: Doing a flight with REX, PMDG 744, Ultimate Traffic 2 and updating weather, 90 mins in and no memory crash so far... Also flying it with just the keyboard as my old joystick has packed it in...