Hey guys,just got concorde x and my fsx hardrive is currently at 42gbs space left and i have noticed since i have went under 60gb hardrive space the game is starting to give me grief :(i was just on my left downwind leg after 3hrs 18mins flight time into kennedy intl and i got the virtual memory error.i am thinking this is a problem is happning because my hardrive almost full.i defrag everynight.my pagefile is something crazy with fsx on it's at used 6001mb and 10357mb availiable so how can i get this virtual memory error sorted i have 8gb ram and its not even touching it got like highest of around 4gb used.thanks just want this fixed hope i dont need a reinstall.cheersHayden.

What OS you using matey?

I have experienced multiple OOM errors with ConcX as well. Usually at JFK. I think there's a memory leak associated with the excessive use of 2d panels.

Don't feel bad, it's not your physical RAM causing the problem, I just had an OOM in Orbx PNW this morning...I'm curious to see what your Virtual Address Space was up to when it crashes... you can download Process Explorer and set the tabs to virtual size to view that level:http://technet.microsoft.com/en-us/sysinternals/bb896653

yeah was on approach to jfk it just locked up just used the lat long to go to my last ins point was using around 2gb virtual and 4.6gb of my 8gb ram thats all i can find so far and im using win 7 64I TRIED TO USE A PROFANITY HERE - AREN'T I STUPID!eers.and i had a demo of fsdreamteam that activated like 40 seconds before the OOM error was running smooth as silk though 25fps was lowest i had at 8000ft

What is your LOD_RADIUS in fsx.cfg at? Also your TEXTURE_MAX_LOAD?

yeah was on approach to jfk it just locked up just used the lat long to go to my last ins point was using around 2gb virtual and 4.6gb of my 8gb ram thats all i can find so far

Not at all interested into task manager reportings.Download Process Explorer in the download link that Ryan posted, edit columns, and set Virtual Size to show. Then report this number, how much does it show usually when you get such crash. Test some heavy airports with Concorde X.

Word Not Allowed I've been flying Orbx land again with 6.5 LOD, but with easy on the fps aircraft, such as Carenado's T210... ugh I'm still getting oom's/g3d's. Today I crashed after about 30 min of flying, departed KHQM, then flew south made a touch and go at some sm strip, then off to KCLS where I ended with a g3d before I could land argh! VAS was around 3.4GB if I recall. I'd love to think it's not VAS exhaustion causing these issues but I feel it is at the very least, directly related to VAS.I ran a test in the same area with LOD 4.5 and VAS was around 2.7GB... but the scenery looks like garbage, especially in the distance. I like those fancy Orbx product screen shots but I'm sure they've upped the LOD and most of them and I wonder if the testers really fly for more than an hour with LOD greater than 4.5Argh... I won't be purchasing any more Orbx stuff until I can iron this out.

Word Not Allowed I've been flying Orbx land again with 6.5 LOD, but with easy on the fps aircraft, such as Carenado's T210... ugh I'm still getting oom's/g3d's. Today I crashed after about 30 min of flying, departed KHQM, then flew south made a touch and go at some sm strip, then off to KCLS where I ended with a g3d before I could land argh! VAS was around 3.4GB if I recall. I'd love to think it's not VAS exhaustion causing these issues but I feel it is at the very least, directly related to VAS.I ran a test in the same area with LOD 4.5 and VAS was around 2.7GB... but the scenery looks like garbage, especially in the distance. I like those fancy Orbx product screen shots but I'm sure they've upped the LOD and most of them and I wonder if the testers really fly for more than an hour with LOD greater than 4.5Argh... I won't be purchasing any more Orbx stuff until I can iron this out.

I've seen a limit being around 3.4 for some sceneries as I mentioned in my thread in FSX forums. It seems that anything above LOD 5.5 is going risky. This includes Orbx too.It is connected to VAS, and I don't remember VAS ever acting like this. I am pretty sure that on my older machine I was able to fly without problem with VAS 7.5. I bet it has something to do with old drivers... though I tried drivers from February, and no change.I know what you mean with 4.5. But try this: 5.5, wideview in fsx.cfg to true, in 2D panel leave 100% zoom, in VC set 60% and external 60%. I'm pretty satisfied with that solution.John has stated that he's flying with 4.5 on some thread. But who knows what really goes on behind the screens.And again... it's not Orbx only fault - this is FSX problem, as it also shows on Aerosoft LOWI and EDDF when you overfly them. Just so you know: I did a simple test of flying towards AS EDDF FL330, default MS aircraft. Paused flight couple of miles from the airport, so much that I have about 1 minute flight to it. So I upped the LOD that much, that when I load the flight I get VAS state of 3.4. At 3.5 it would crash just when EDDF was about to be loaded (runways would appear, but no terminals, buildings), g3d.dll error. If I lowered the VAS a little, for example to get VAS 3.2, no problems in loading.You can't blame scenery producers for that. This MUST be FSX thing.

VAS problems are generally caused by 1). fragmentation of the pagefile and 2). having too small a pagefile.Assuming a machine with 8 GB RAM - both issues can be avoided on modern systems by a). creating a fairly large, custom pagefile on the C: root by unchecking the 'Automatically Manage paging file size for all drives', then setting 'Custom size' and 'Maximum size' equal to 8 gig (8168) in both boxes. Following this - add a second pagefile to another drive in the same proportion, so that the total size - 16 gig is roughly double that of your system memory.

VAS problems are generally caused by 1). fragmentation of the pagefile and 2). having too small a pagefile.Assuming a machine with 8 GB RAM - both issues can be avoided on modern systems by a). creating a fairly large, custom pagefile on the C: root by unchecking the 'Automatically Manage paging file size for all drives', then setting 'Custom size' and 'Maximum size' equal to 8 gig (8168) in both boxes. Following this - add a second pagefile to another drive in the same proportion, so that the total size - 16 gig is roughly double that of your system memory.

And what if you don't have a pagefile?Mind that, I don't have a pagefile since I first got my first 2GB, long long time ago. With 2GB, I had issues, yes, that is why I very quickly upgraded to 4GB, and since then, never ever did I have one single problem, until now.I could bet that this VAS problem, is not connected to the pagefile and I will be happy to make a test for you, maybe this weekend.

I had some issues in ALL long haul flights.Different planes and different settings change only the quantity of time after which the oom will happen.If I fly a small and simple GA plane I have few of VAS used.If I switch to 737 NGX the VAS usage increase a lot.In the same way, if I use a lod_radius of 4.5 I have few VAS usage, if I set lod_radius to 6.5 the VAS usage increase dramatically.But this is only the start condition of the flight.Along the flowing of the time, the VAS usage increase ever, more or less quickly, but increase.After some time, many hours if I started in a 172 with lod 4.5, 10 to 45 minutes if i used 737ngx with lod 6.5, the OOM error will come.It seems there is some memory leak in FSX engine (at least when used in Win7x64).It cannot free completely the VAS from all loaded texture.Each time you fly over a complex scenery FSX load a lot of textures and it seems to me it never will unload completely when you are overflying another country. Also, changing many times views from Virtual Cockpit to 2D to external to map ecc. will accelerate the process of VAS "consuming".So, when you after several flight time are near the limit of VAS and enter the zone over a complex scenery, FSX simply cannot unload all the texture needed to make space for the new ones and produce the OOM.Theese are, in my opinion, the reasons why OOM's happens more frequently in certain zones or with certain planes.I tried also different versions of uiautomationcore.dll and someone reduce this behavior more then other, but no one eliminated it completely.I use two workaround to live with this:1) Create different fsx.cfg; one with high graphic and lod 6.5 for vfr flights, one with low graphic, lod 4.5 ecc for PMDG flights, one for... at your wish.2) Activate the "autosave" function in FSUIPC just to not start from beginning a long flight after having an OOM in the final stage.If I'm wrong and someone found a good repeatable and verifiable solution to OOM problems please post it.It would make happy me and a lot of other simmers :-)

Hi Kos; The OP said he has

42gbs space left and i have noticed since i have went under 60gb hardrive space the game is starting to give me grief .......... i got the virtual memory error. I am thinking this is a problem is happening because my hardrive almost full.

I agree. He has a VM error, and I gave two reasons and options to fix it. You have shown a third option that might be viable, depending upon how he has his paging system setup.If he has Windows managing his pagefile, with the limited space that he has - he will get VM "problems", because Windows is looking for that pagefile, and it doesn't have that space on the disk. This is most likely the case at this moment.If he doesn't have a pagefile - then his system needs one - or he has a memory problem.The downside to having a pagefile, is that if he doesn't have a pagefile - Windows won't look for one, and the risk is, if ever an app, perhaps running alongside or on top of FSX, such as new AI or newer, highly detailed graphics grows, or he encounters an app with memory leaks - he risks a memory allocation crash with nowhere to put any log file...That being said - with 8 gig of ram, and never had a VM issue myself - is it actually necessary to have a pagefile? You are obviously successful without one, and one of my other fs friends recently put 24 gig of ram into his new machine, and could easily run without one, so I'm going to turn mine off altogether for a couple of months just to see if there's any issue. There's a ton of inconclusive discussion on the weeeb re this issue, but I happen to think you're right, and it might be time to actually do just that.

This MUST be FSX thing.

Yeah it certainly is. I realize I came across stating it was Orbx's fault when its clearly not. But I can't really spend the money on their stuff because it makes g3d's easier to come by because of FSX's old poorly written code.

Yeah it certainly is. I realize I came across stating it was Orbx's fault when its clearly not. But I can't really spend the money on their stuff because it makes g3d's easier to come by because of FSX's old poorly written code.

I see it from another perspective:FSX was coded for FSX. Not for FSX+ORBX+REX+GEX+UTX+NGX+FT+FSDT+XXXXXXX... And ORBX was made for FSX. And at it's default settings, it's not crashing, now is it?It is our choice to run as we like, and it should be our expectation that it crashes if we don't understand what's under the hood.In the end, lowering to default 4.5 LOD is going to relieve you of any problems. But you/we can't live with it... it's our problem. Not FSX old poorly written code. The code is alright for the time when it's been written.

hey all been busy tonight sorry for the delay.my pagefile was 8gb i have increased this to just over 12gbi have checked my cfg and the LOD is at 4.5im thinking its either my hardrive is struggling to keep up as it is degraded because theres not as much space and its taking longer to find the info. or its concorde x thats the problem as i never have a problem with my pmdg my frames do drop to around 15-20fps becausing im running gen x 1-4 rex 2.0 mega airport heathrow and addon planes etc.i think a reinstall with all my big scenery stuff and rex2.0 on my 1TB hardrive that i keep all my other games.i will try it tonight with the pagefile at 12gb and see whats what and i will download that program thing as mentioned above and monitor whats going on when using the concorde in highly built up places.thanks.hayden