This is what I'm confused about.

I see people saying to shut down background programs, but I don't think it makes the least bit of difference since FSX only uses a fraction of a strong computers resources anyway.

It don't matter if you shut down everything, FSX is still only going to use 4GB and suffer OOMs.

 

I think the confusion enters the picture when people are running less than 4GB RAM because at that point it's physically impossible for FSX to request upto 4GB regardless of /3GB switch ... the OS will require some RAM so it can't give it ALL to FSX. For any 64bit Win7 or Win8, 8GB RAM should be your minimum -- given the cost of RAM $50-$60 for 8GB it should be a no brainer purchase ... heck RAM is cheaper than some FSX add-ons.

 

Background tasks can take away RAM also, and if you are RAM constricted (4GB or less) I can see why some look to stop background processes. A background process running will use CPU and RAM ... if you have CPUs and RAM to spare, it's a non-issue, if you don't then you need to manage those background tasks.

 

XP10 is a good demonstration of what can be accomplished in a 64bit native address space ... XP10 is by no means perfect, but it's moving in the correct direction for "unlimited" 3rd party vendor support. The problem we're facing with FSX and 3rd party right now is that they are trapped in a 32bit address space -- how do you do a "next generation" more realistic version of your product (with more features) when it consumes more of that limited 32bit address space?

 

As more and more Add-Ons get better and do more we can't buy them because they'll require some other compromise/sacrafice to keep us under the 32bit address space ... this can't be sustained indefinitely regardless of market potential.

 

Anyway, in the here and now, I hope the process I use to OOM management helps others stay under the OOM and reach their destination airports safely

I hope an Admin will re-word my title, I really wasn't trying to bash UTX at all ... my apology if it comes across that way.

 

No worries, Rob. It's quite clear from your postings that you weren't blaming UTX.

 

Scott

I'm going to start using the trading "tit for tat" mentality when flying in FSX.

If I want AI traffic, I will try shutting down some scenery, etc.

I pretty much only use AI leaving and arriving at an airport feel a bit more comfortable with this option.

Ok ... hoping an Admin renames my title as it wasn't intended to "bash" UTX.

 

I don't have that authority Rob or I would have. I'll see what I can do though. If we can't change it though I wouldn't be too concerned. I think you have done an adequate job telling everyone you didn't mean to bash UTX. I missed that 9.5 LOD in your config and that is a known cause of OOM's. I have been somewhat successful at 7.5 but I don't keep it there long especially when the sim frames start falling.

 

Best regards,

Jim

 

I hope an Admin will re-word my title, I really wasn't trying to bash UTX at all ... my apology if it comes across that way.

 

There you go Rob. Thanks for the heads up Jim.

 

Kind regards,

Thank you Stephen, appreciate it.