Maybe this could have something to do with the OOMs:

 

"Texture loading engine causing multiple texture sets to load" at http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=4373

 

Daz

 

 

​

 

Interesting! Could well be it!!! Unfortunately only the list with things they are looking into gets longer and not the list with solved issues…  ^_^

Maybe this could have something to do with the OOMs:

 

"Texture loading engine causing multiple texture sets to load" at http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=4373

 

Daz

 

 

​

 

Yes, that could well be it. Orbx has acknowledged that default textures are mixing with FTX Global textures, so there could well be an issue with textures being loaded multiple times. Also, there is the known tree texture bug already mentioned. 

 

I did some more testing this morning trying to see if any change in settings could solve the OOM problem.  I left the autogen at very dense, as I'm not willing to compromise that. As mentioned before, LOD is already at a reasonable 4.5, and textures are 1024x1024. I set AI traffic to 0 and turned building shadows off.  Neither eliminated the OOM. In fact, when taking off from Belfast City, I had an OOM just after takeoff with 1.6 GB shown in free VAS--a new record! However, the OOMs are fairly unpredictable.  Another flight with the exact same settings allowed me to fly around Belfast for 10 minutes before an OOM--this time near the 1 GB mark.

 

I also tried deleting the shader cache.  That did allow me to fly for 30 minutes, but I still had an OOM once free VAS approached 1 GB, so that is not a solution.

 

In my monitoring with different settings at different locations, the lowest I have ever been able to get free VAS before an OOM is 750 MB.  

 

 

Orbx has acknowledged that default textures are mixing with FTX Global textures, so there could well be an issue with textures being loaded multiple times.

 

No, that has to do with a bug/oversight in the installer. FTXG overwrites the default textures so it's not possible that P3D loads the FTXG and the default texture for that same specific spot at the same time. But maybe textures for various seasons are loaded at the same time or something like that…? 

No, that has to do with a bug/oversight in the installer. FTXG overwrites the default textures so it's not possible that P3D loads the FTXG and the default texture for that same specific spot at the same time. But maybe textures for various seasons are loaded at the same time or something like that…? 

 

ok, that makes sense. Whatever it is causing this, let's hope LM and/or Orbx are on it. I'm encouraged by LM's list of fixes in the works. I'm sure they will solve it eventually.

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=4582

http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=4551.0

 

 

The issue occurs ONLY with POP_FREE_AUTOGEN=1 and when autogen tree density is set to max.
The issue does NOT occur with POP_FREE_AUTOGEN=1 and when autogen tree density = dense (2 cranks below maximum)
The issue does NOT occur with POP_FREE_AUTOGEN=0, no matter the autogen tree density.

change POP_FREE_AUTOGEN=1 -  POP_FREE_AUTOGEN=0 (Appdata/LM/P3Dv2/Prepar.CFG)

It's a big mystery. Last night I loaded up P3D2 and took a flight with the A36 from the default airport. All went fine. Then I moved to ENEV with Norway freeware activated in the scenery library and took off. Two minutes after take off: OOM (VAS usage spiked from 2,5GB to around 3,4, then OOM). Nothing new, but I decided to see if I could replicate the error. I restarted P3D2, picked ENEV and the A36 in the startup screen and launched the flight. Flew around for 30 minutes, no OOM. Repeated the process, and did another 30 minute flight, still no OOM and VAS usage at a comfortable 2,5GB. So from what I can gather, it has to be something about changing certain things in the menues or moving airports after a flight is started that sparks the OOM. So for me, as long as I set up the flight in the startup screen and don't enter any menues during flight, all seems fine.

 

 

So for me, as long as I set up the flight in the startup screen and don't enter any menues during flight, all seems fine.

 

Which makes it impossible to load a flight plan… And if you have that weird tree texture problem you also HAVE to use the menu. Not using the menu isn't an option, really. But obviously something is simply wrong and LM has to solve this.  ^_^

That's what killed me about v2.. There is no trust factor with it.. That's why I refunded.. Nothing worse than a game you have no confidence in. FSX as flawed as it is in areas I trust to run for hours at a time no matter what..  v2 I never trusted and expected it to crash at any time..  I don't mind throwing away addons for v2 but the fact nearly any and all signs of backwards compatibility are sketchy, or non-existent  at best beyond "hey it loaded!!" is a huge problem for me.. I eagerly await 2.X to see what is accomplished here.. 

Which makes it impossible to load a flight plan… And if you have that weird tree texture problem you also HAVE to use the menu. Not using the menu isn't an option, really. But obviously something is simply wrong and LM has to solve this. ^_^


Did you try loading a flight plan direcly from the prepar3d flight plan folder ...

I have a much higher trust factor that the issues with P3Dv2 will be fixed than that the still quite significant issues with FSX will be fixed.  :lol:

Update and Synopsis:

After numerous posts in 3 different forums, it seems that the consensus is that this is a P3D issue and not an add-on issue (FTX Global). It has been reported with both default planes and add-on planes. P3D seems to have a bug that is triggered with certain settings and/or if the menu is accessed in flight. The bug is that a message appears stating that P3D has run out of memory even when Windows reports 1 GB or more free (of the 4 GB available).  This seems to occur only in high autogen areas like dense forests or urban areas, but the OOM occurs even if autogen is not set full right on the slider.  Either there is a sudden crash in VAS or the program is erroneously reporting an OOM when none exists. My system is Windows 8, but I believe some others have experienced this with Win7 as well.

 

I'm waiting on an acknowledgement from LM of this bug, as it has now been confirmed by 5+ users. They have done a great job of responding to other known bugs, so i'm sure they will investigate.

Did you try loading a flight plan direcly from the prepar3d flight plan folder ...

 

No, I didn't. I wonder how that would work…? Aren't you mistaken flight plans with saved flights?

 

What could work though (I think, haven't tested it) is to save a default flight while a flight plan has been loaded. The next time you want to fly with a specific plan, you have to edit the saved flight and change the name of the linked flight plan OR save a new flight plan under the exact same name (if you don't mind not saving all flight plans separately). 

 

BTW If accessing the menu causes problems you can't only load a flight plan but you can't also create one with the included planner. Not that I want to because it sucks, but still.

 

Anyway, as I said, LM simply needs to fix this. And everything else too.  ^_^

Open p3d with fxml file in the flight plan folder it works ...and indeed I am   mistaken flight plans with saved flights but it works with  flight planner  just have to save it back to save flight

+1

just have to save it back to save flight

 

 

So... you have to start a flight, load a plan in the P3D planner, save the flight, quit P3D and the load the plan from the P3D folder to avoid having to use the menu during a flight? I just tested my trick and it worked like a charm. I use Plan-G to create flightplans. I usually do simple short VFR flights so nothing too complicated and hence I never use old flightplans and hence I have no need to save them all. In fact, I rather don't because it only clutters up the folder with documents. So what I have done is this:

 

1. I created a plan in Plan-G and saved it (well, exported it) as 'Flightplan.pln'.

 

2. I started my default flight, loaded 'Flightplan.pln' using the P3D planner and after that I saved my default flight. Now that Flightplan.pln is saved within my default flight!

 

3. The next time I create a new plan in Plan-G, I simply save it again as 'Flightplan.pln'. When I start my flight in P3D (after picking the desired plane, location, weather and time) I start the flight and my new flightplan is immediately loaded! So now I don't need to access the menu at all anymore. I didn't like to load that plan everytime anyway so this is a win win situation. ^_^

 

Obviously when you get wrong tree textures you need to access the menu anyway... Again, LM simply needs to solve this but whatever they do, I will keep on using this trick to load my latest plan automatically because I didn't like to do that anyway. Pity I didn't think of this when I was still using FSX.