Hi,

Yesterday I received an error message with Out of Memory for the first time.

I wanted to fly from KPHX to KCLT and I have both airports as default scenery.

After about an hour of flight I get the message saying Out of Memory.

The error always happens in exactly the same place.

I have autosaves with Volanta and by chance a safe was made before the message came.

If I load this safe, it crashes immediately.

Then I took a save file that was about 20 minutes old.

I can load that, but when I get to exactly the same place it comes out of memory again.

I find this very strange because I never had this error.

I have 32GB RAM and 12GB VRam and have never had any problems.

and where I fly there is no scenery, just ORBX North America... But I don't think it's because of ORBX... There's nothing else there.

Do you have any ideas what I can try?

Are you running out of VRAM or RAM?  I suspect it's VRAM but needed to ask.  Also, it would be helpful to know your system specs and what settings you are using.  Are you using an addon aircraft and if so which one?

One other thing to consider is to start a flight close to the location where you get the condition and see if it still occurs.

I'd use the tool in Orbx Central to re-sync your scenery, and maybe go to each of the Orbx regional sceneries and landclass in OC and run the "verify files" tool for each of them as well, as a corrupt scenery bgl or texture could do this.

Another possibility is an AI plane within your "reality bubble" with a bad texture.  If you've got a saved flight that definitively triggers the crash, try turning AI traffic completely off and load the saved flight to test.

@Säbel57

It's not VRAM but RAM... But in both cases I had enough during the crash.

I fly with PMDG 747-400

 

@Bob Scott

Thanks for your tip

I'm going to try ORBX today.

Yesterday I did another flight, before that I deleted the p3d.cfg file and recreated it.

It crashed again in exactly the same place.

Here is the video from CTD:
https://youtu.be/xT-CciDUFP8?t=4551

I had the task manager open and to see RAM usage.

When it happened I had a RAM consumption of 13GB out of 32Gb... So still enough.

Unfortunately, I don't know why it still crashes. There was enough RAM and VRAM.

It always happens between waypoint JSSUA and MAXXO... about 16.4 nm before MAXXO

With PMDG 747-400.

I have over 2000 hours with P3D and have traveled all over the world.

And in the area where I was traveling there was only ORBX Global and North America.
Both airports KPHX and KCLT are standard scenery
I never had such an error... And I think it's an error... Because I have enough RAM..

There is also a swap file... actually everything works... Why it crashes, I have no idea

 

If you're the same person reporting this on the LM forum (RAMMSTEIN) then is this happening when you're inside the aircraft? Or is it only happening when you're viewing the world from space?

Yes I am 🙂

Yes, it happens in map mode or in the cockpit

@Lenovouser have you establised if this crash happens regardless of vehicle being used?

Have you even done a disk scan?

Have you verified that all scenery files are clear of any corruption, either by getting Orbx Central to verify the

scenery or re-download and install afresh ?

 

I strongly suspect a corrupt file.

One more thing ( as Columbo used to say ) does it suddenly crash and show the message or does it start stuttering and show increased disk activity and then

eventually crash out?

 

PS. I just re-read my post and I sound like a certain well know & frequent poster on LM forums.......Marty??? 😄😄

Edited December 21, 20232 yr by Sparkrite

55 minutes ago, Sparkrite said:

@Lenovouser have you establised if this crash happens regardless of vehicle being used?

Have you even done a disk scan?

Have you verified that all scenery files are clear of any corruption, either by getting Orbx Central to verify the

scenery or re-download and install afresh ?

 

I strongly suspect a corrupt file.

One more thing ( as Columbo used to say ) does it suddenly crash and show the message or does it start stuttering and show increased disk activity and then

eventually crash out?

 

PS. I just re-read my post and I sound like a certain well know & frequent poster on LM forums.......Marty??? 😄😄

Your questions look ok to me.

Have you tested the Op’s flight to verify your setup does not give an error?

"PS. I just re-read my post and I sound like a certain well know & frequent poster on LM forums.......Marty??? 😄😄"
Does Marty? (LM forums) sign posts with real name?

The topic: V5.4 OUT OF MEMORY on P3D forum is here:
https://prepar3d.com/forum/viewtopic.php?t=150112

Edited December 21, 20232 yr by vonmar
added info

@ Lenovouser

 

Do you use AIG Traffic?

 

See:

 

Yes, I use AIG, I also tried it without AIG, again the same error.

I didn't try it with ORBX yesterday.

So in Central, fix the scenery etc.

I'll try to repair the files and test again

32 minutes ago, Lenovouser said:

Yes, I use AIG, I also tried it without AIG, again the same error.

I didn't try it with ORBX yesterday.

So in Central, fix the scenery etc.

I'll try to repair the files and test again

"Yes, I use AIG, I also tried it without AIG, again the same error."

You mean disabled AIG, correct?

Just a bad AIG e.g. aircraft file in your setup can cause the problem.

Uninstall AIG and test again.

 

OK, I understand that you should try everything. But sometimes I think that I try certain things pointlessly.

Yes, I can deactivate AIG and go through the trouble of deleting everything and reinstalling it, which would take hours again.

Will my problem just be fixed?

It's not like I have this error all the time, and everywhere...

After flying for 2000 hours I have found a point where the memory is running out and here is AIG to blame?

somehow I don't think so.

I also find testing with F35 pointless... you can do it, but what's the point? You won't always fly an F35.

On 20.12.2023 at 16:53, Bob Scott said:

Ich würde das Tool in Orbx Central verwenden, um Ihre Szenerie neu zu synchronisieren, und vielleicht zu jeder der regionalen Orbx-Szenerien und Landklassen in OC gehen und auch das Tool „Dateien überprüfen“ für jede von ihnen ausführen, als beschädigte Szenerie-BGL oder Textur könnte dies tun.

Eine andere Möglichkeit ist ein KI-Flugzeug in Ihrer „Realitätsblase“ mit einer schlechten Textur. Wenn Sie einen gespeicherten Flug haben, der den Absturz definitiv auslöst, versuchen Sie, den KI-Verkehr vollständig auszuschalten und den gespeicherten Flug zum Testen zu laden.

I have to try this out, I think there is a mistake somewhere

1 hour ago, Lenovouser said:

I also find testing with F35 pointless... you can do it, but what's the point? You won't always fly an F35.

No of course you wont ! However like a lot of fault finding it is by a process of elimination. If you use a default aircraft and it still crashes at the same point, well then we know that it is unlikely to be a faulty aircraft causing it. The same conclusion can be drawn from disabling AIG or indeed any other addon etc..

We still don't know if you have even done the basics of checking for file/disk structure errors.

On 12/20/2023 at 10:27 AM, Lenovouser said:

and where I fly there is no scenery, just ORBX North America

I find the above somewhat contradictory. Orbx NA has literally thousands of files with mutiple Gigs of data. If any file is corrupt and it is called it WILL most likely cause an error. This in turn may lead to a CTD.

I don't know why you chose to ignore what I suggested above as it is simple and relatively quick to do and is certainly one of the fundamentals in trying to pin down unexplained crashes. To save you having to scroll back I'll quote it here:-

19 hours ago, Sparkrite said:

@Lenovouser have you establised if this crash happens regardless of vehicle being used?

Have you even done a disk scan?

Have you verified that all scenery files are clear of any corruption, either by getting Orbx Central to verify the scenery or re-download and install afresh ?

 

Edited December 22, 20232 yr by Sparkrite

I don't ignore any suggestions and am grateful for every suggestion.

But there were a few suggestions and I can't test everything in one day because I also have to work.

Since it still crashes with F35 and without AIG I will try the other suggestions.