FSDreamTeam forum
Products Support => Los Angeles support FSX/P3D => Topic started by: glez18 on September 24, 2011, 12:41:56 am
-
Hi, when turn on FSX with PMDG B737 after 5 mins aprox fsx ctd and message say out of memory reload fsx, any sugestion?
Efrén
-
Does it happen with a default airplane ? Do you use a 64 bit OS ? PMDG suggests using 64 bit OS for the NGX.
-
Does it happen with a default airplane ? Do you use a 64 bit OS ? PMDG suggests using 64 bit OS for the NGX.
Win 7 34 bits, work fine other airports fsdt like LSZH LSGG PHKO... etc, i was try with MD11 pmdg in aproach it is the same.
Efrén
-
Win 7 34 bits
Now I'm confused...it's 32 or 64 ?
work fine other airports fsdt like LSZH LSGG PHKO... etc, i was try with MD11 pmdg in aproach it is the same.
That's not what I've asked: have you tried with a DEFAULT airplane ? The MD11 is not a lightweight airplane either.
-
Does it happen with a default airplane ? Do you use a 64 bit OS ? PMDG suggests using 64 bit OS for the NGX.
Win 7 34 bits, work fine other airports fsdt like LSZH LSGG PHKO... etc, i was try with MD11 pmdg in aproach it is the same.
Efrén
Of course, those airports are not as heavy. How much memory do you have ? What display card do you have ? And how much memory does your display adapter have ? If you have a 32bit version of W7, you are going to get OOM's, under certain conditions, a 64 bit is highly recommended. Lot's of variables here, and using the NGX will show up any weakness in your system, more so than any other aircraft released so far. Also HD textures are going to suck your system dry of resources, and until you adress those issues, I would suggest to use lighter memory hungry aircraft.
-
Win 7 32 bits, 4ram, intel quad core, 1t hard drive, video 1gb, i never had this problem until now klax with a carenado cessna 152 or Skyhawk Aerosoft no problem.
Efrén
-
Win 7 34 bits, work fine other airports...
Depends on how much memory you have. The 32 bit versions only see memory under 3 GB, if you have more like some of us... I just upgraded froim 32 bit XP to 64 bit W7, and having that extra 5 GB makes a major difference in performance. Until I can afford to replace the processor with an iCore...
-
Win 7 32 bits, 4ram, intel quad core, 1t hard drive, video 1gb, i never had this problem until now klax with a carenado cessna 152 or Skyhawk Aerosoft no problem.
Efrén
As it was said before the problem shows the technical bounderies of fsx running at its limits on a 32 bit OS. Although you have 4GB of Ram a 32 bit OS would not let you use this amount of Ram for FSX only. It is more like 2GB for the simulator and 2GB for the OS. The simulator itself has to share its address space with the graphics card. If you have an extreme card like a 1,5 GB or more you will run into trouble. The only way to get more stability on a 32 bit OS is to reduce slider settings when using high end aircraft.
On the other hand you could upgrade to an 64 bit OS and 6 GB of Ram. For FSX as an 32 bit application it is not necessary to have more Ram (8GB or more) as no 32 bit application running under a 64 bit OS can address more than 4GB of Ram. As said before an extreme high end card with 1,5 GB to 3 GB card has to share significantly more of this address space leaving less for the the simulator what causes instability. But with Win 7 64 bit the simulator at least gets the full 4GBs for the application only. This should solve most of the problems. ;D
-
Win 7 32 bits, 4ram, intel quad core, 1t hard drive, video 1gb
32 bit OS, with a 1GB video card is a big no-no, because the 1Gb memory is *subtracted* from the available memory, since the OS can't address more than 4Gb in total, including vram, if you want to use pmdg airplanes, you really need to use a 64 bit OS, especially with an 1Gb card.
-
The combination of klax and the new 737 ngx will eat allot of memory I saw about a high 3.0 of memory being used with pmdg ngx they will have a update coming up which will have a lower res textures and some others things that will help with the load.
-
Hi,
have OOM all the time on final approaches.
OS = W7/64bit, 6GB Ram, PMDG 747-400,
FSGlobal2010, Ultimate Terr.USA.
Any idea on this?
Thanks
Gerd
-
me too.
Just tried to land (the second or third time) with the PMDG7,37NGX, coming from KSFO. Not a very long thing. I used the ASE-weather, it was very cloudy. I use Win7 64bit, 16GB RAM and a GTX470 with 1,3GBG RAM. Autogen is set to normal. Normally this should be enough to land, but I wasn't able to do so. To exclude the PMDG I'll try the CS757 the next time.
greetings Kai
-
Ialsol get out of memory with LAX its frustrating you are about 7 miles out and then it hap;pen you get the error message out of memory, a lot has to do with the plane that you are flying and do you have a 32 or 64 bit windows 7 which I have and 6 gb and 580 gtx 1.5 gb but since I run my alirlines high with ut2 at 75 percent just will have to tone that down to about 60 percent and autgenn is at max.
-
Hm, I made it to the first taxiway after landing with my NGX. Then I got an OOM. I never new this before and all was running rock stable. I also have several other "high performance" airports. and the NGX is running well, too.
I have also Win 7 / 64 with 8GB RAM and 1GB Ati 5770 video card. Any suggestions? Will do some further tests soon.
-
You don't seem to understand that, it's not a "single" addon that cause OOM errors, it's the COMBINATION of EVERYTHING you have at an airport and, most important, your settings.
First, having more than 4GB will help, but more than 6GB will probably won't make any difference, since FSX can't allocate more than 4GB, and the remaining 2GB should be enough to run Windows itself.
If you have OOM, which usually happen only with very complex airplanes, is because your settings are too high, try lowering the "Scenery Level of Detail Radius".
With KLAX, a memory saving feature is to turn off HD Textures, at the cost of image sharpness.
-
At what autogen setting does KLAX start to loose objects?
Cause right now, I am at Very Dense...and can deal with it...but if I wanted to make a video...and turn it down to Dense or Normal...would I loose airport objects or are they hard coded in?
Thanks...and sorry to jump on the thread..
-
At what autogen setting does KLAX start to loose objects?
The autogen density only affect the Autogen, KLAX objects are affected by Scenery Complexity as they should, but I believe that at Very Dense they already all in.
-
Thank you. I also just tried it a Dense, and really didn't notice any difference either except faster rendering. But then again, I didn't really test all areas.
Great work!
-
Windows 7 64 bit
Intel Core i5
8 GB Ram
1 TB Hard Drive
Airbus X from Aerosoft
Active Sky 2012
REX
On Final, the game cuts off & says you ran out of memory, restart FSX :( I was just about to land too...
-----------------------------------------------------------------------------------------------------------------------
Ok after trying it again last night, I did get the out memory error again but this time it atleast let me land & its when I was taxing to the gate that I got it last night.. I still don't understand though, I flew to KPHX Flightbeam the other day thats loaded with HD & never got that message & never have had any problems with any other airports so far from FSDT but what is it about LAX thats giving my pc such a fit.. If thats the case what Virtualli is talking about with the HD stuff than I would of thought I would of gotten something at PHX too but I never did that or I completely lucked out that day I flew there...
I am able to take off from LAX no problem, Atleast I did the other day with no issues & has kept my settings the same & haven't changed them at all... I think its just a minor bug issue at LAX to tell you the truth because have had no issues at LAX or KPHX which is made of HD quality. Something is telling me there is just a small glitch at KLAX because like I said it let me land last night & start to taxi, I didn't even get that far the other night.. It was on final approach the other night when I flew into LAX that I got the out memory error & last night it let me land & taxi before it cut me off.. That sounds like a small glitch too me..
-
KLAX doesn't have anything to to with this, except for the fact that, such a large airport with so many parking spots all very close together (so there's a lot) is able to attract a lot of AIs.
And, HD textures in KLAX DO NOT take more memory than an normal scenery, because they are not used to increase resolution to what it would otherwise be if it used regular textures, but to gain speed, because there are 16x less of them comparing to, say, KDFW, which means the overall memory usage of HD textures is the same as if the scenery used many 1024x1024 textures instead of few 4096x4096.
REX, instead, use 4096x4096 textures for clouds to INCREASE quality so, of course, they take more memory.
Your settings are simply too high, lower them OR use DirectX 10 (KLAX is compatible with it), which takes less memory compared to DirectX 9.
-
Google 'kosta memory fix'
You need the reg file memory patch by ms.
-
Windows 7 64 bit
Intel Core i5
8 GB Ram
1 TB Hard Drive
Airbus X from Aerosoft
Active Sky 2012
REX
On Final, the game cuts off & says you ran out of memory, restart FSX :( I was just about to land too...
-----------------------------------------------------------------------------------------------------------------------
Ok after trying it again last night, I did get the out memory error again but this time it atleast let me land & its when I was taxing to the gate that I got it last night.. I still don't understand though, I flew to KPHX Flightbeam the other day thats loaded with HD & never got that message & never have had any problems with any other airports so far from FSDT but what is it about LAX thats giving my pc such a fit.. If thats the case what Virtualli is talking about with the HD stuff than I would of thought I would of gotten something at PHX too but I never did that or I completely lucked out that day I flew there...
I am able to take off from LAX no problem, Atleast I did the other day with no issues & has kept my settings the same & haven't changed them at all... I think its just a minor bug issue at LAX to tell you the truth because have had no issues at LAX or KPHX which is made of HD quality. Something is telling me there is just a small glitch at KLAX because like I said it let me land last night & start to taxi, I didn't even get that far the other night.. It was on final approach the other night when I flew into LAX that I got the out memory error & last night it let me land & taxi before it cut me off.. That sounds like a small glitch too me..
Also, give this a whirl. I'm currently testing it and can say thus far all seems good. More testing to do, but initially it seems to assist greatly.
http://www.ntcore.com/4gb_patch.php
It's been created by a computer whiz named Daniel. You can also shoot off an email to him with any questions. Good luck with it!
Rgds,
Steve
-
http://www.ntcore.com/4gb_patch.php
It's been created by a computer whiz named Daniel. You can also shoot off an email to him with any questions. Good luck with it!
This patcher doesn't do anything on FSX, it was needed for FS9, because FS9 wasn't compiled with the /LARGADDRESSAWARE flag, so it was limited to see 2GB only without this patch.
FSX with the SP2 or Acceleration is already flagged as such, so that patch doesn't do anything.