When I got the OOM report, EVGA Precison X was showing 2.3Gb of vram usage, nothing else was open in my computer expect by ASN, PFPX, xacars, none of them request more vram than 12gb of my total.

 

That's my point, something is very wrong sim to crash this way. I had crashes before but around 3.4 ~ 3.6 and using PMDG 777 and in heavy scenario areas.

 

Approaching EDDF is very simple scenario.

Vram is video RAM. Not rhe same as virtual memory. What graphics card are you using and what screen resolution and AA?

AS Howard said - the 12G of ram on the card have nothing to do with Virtual Adress Space - that is limited to 4G in a 32bit system. You used 2.3 - so something requested more contiguous space than you have.

 

For example - you used 2.3 - that means you have essentially 1.7 g remaining *BUT* if the LARGEST CONTIGUOUS section of that 1.7G was only 300MB - if you got a request for 301MB - you'd get an OOM with 1.7G remaining.

 

Reboot and try the flight again - see if you can repeat the OOM. Might have just been a fluke.

 

Vic

I assume before blaming LM that you did a few other flights such as the reciprocal or even between two other airfields or at least more than one flight?

It could well be something in the sceneries that is causing the issue.

Before this flight I did LIRF LOWW, but then I closed the sim, opened it again to do the next flight.

Vram is video RAM. Not rhe same as virtual memory. What graphics card are you using and what screen resolution and AA?

This, plus he's running super VAS intense addons (Orbx, Aerosoft airports)... No wonder there's an OOM

Did objectflow get updated?

Did objectflow get updated?

 

Yup

Yes I know the 32bit has the limit of 4gb between vram and ram, my point is, ram usually is low on P3D, about 1gb at most, the bottleneck usually is vram, what about that miracle of managing the memory?
I'll keep flying P3D, but my point is, I won't spend more money on this platform, I'm done. ONLY if I see a real miracle or 64bit platform on v4, apart from that, will keep the v3, because I feel I should keep using the v2, the problems still the same.

It sounds like you may be blaming the wrong thing. 

 

I recommend you read these 2 articles for more insight into your particular issue;

 

http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx

 

https://blogs.technet.microsoft.com/markrussinovich/2008/11/17/pushing-the-limits-of-windows-virtual-memory/

 

Good luck.

Seems P3D gets the blame for everything.

Seems P3D gets the blame for everything.

 

Nice, I thought it's what ever is the newest addon that gets the blame for the OOM's. What ever that is added on top of the heap that breaks the glass ceiling. I wonder if this crash was even an OOM as it's often blamed for regular crashes as well.

Incredible, I have never ever experienced an OOM on my system...

 

Photoscenery with custom ag ( dense - very dense ) on top of it, AI traffic, 4 cloudlayers and 130 visibility, 110 cloud draw distance, cloud coverage max,

FTX global + UTX terrain where I do not have photoscenery.

All major airports....

 

As I only fly in Europe I have the default NA, SA, Asia,,Australia disabled in the library.

 

Oh, aNd I also have Night Environment detailed...

And did I mention that I use 3 screens for outside view..?

 

My system can only use the same amount of VAS as anyone else..

AS Rome, AS Zurich , AS Frankfurt, I can fly to and from them without an OOM..

Seems P3D gets the blame for everything.

So true. It is unfortunate when people incur a problem that is an anomaly that nobody else experiences and blames it on the app and not their own setup or system.

Never have OOMs here - just default scenery, max texture 2048, OPTIMIZE_DENSE_CLOUDS=1, ah, and the weather injector ( ASN )....

 

PMDG 777 ( from time to time ) but mostly just the imported FSX 747-400 is in use ( because I use P3D just for the visuals - and it doe a great job in this area... )

 

We have to know our limitations...