Interesting! Is that what was different to last week when you didn't have OOM's?

 

 

 

 

Or they could just make it so that nothing can be added, edited, or modified.

 

That would certainly solve the tweaking problem  :lol:

 

How is Flight doing BTW ?  :lol:

 

Flight? I never installed Flight...since I never cared for the original philsophy behind it. Not sure why you even asked me that Q.

 

 

Maybe some of you could fly around ENBM Bomoen and see what happens.

 

Your wish was my command, only because it has been quite saddening to see you "lose the faith" so to speak.

 

I have done a couple of flights from ENBM with the Orbx dense clouds and only FTX Global. It was interesting to say the least. Unfortunately time is not on my side, so did have time to test further. 

 

The first time, I changed from my home location (it's summer here now) to ENBM and sat on the runway as the new winter textures loaded. Frames solid at 30FPS. Headed west and within 3 minutes my frame rates plummeted to 10 to 13! Choppy ride indeed.

 

Second time, I changed the textures to summer and within 3 minutes there was a slight drop in frames to 25 or so. Nothing less.

 

I dont have time for a few days to do more, but I wonder if there is a problem with FTXG winter textures? Try the same flight in summer and see if all is ok?

 

Just thoughts, hope you get it sorted

 

 

f you're running an older system, then we hope for the price you can be satisfied and find a smoother and more immersive training and learning platform that is being supported and actively developed.
Wes Bard
Software Manager - Prepar3D® Team

 

Thanks Wes.

I will give it a go tomorrow night for you J.

Tonight I did a flight in fsx from KJFK fsdreamteam v2 to flightbeams KIAD a 4096 airport in the PMDG 777, with opus ofc.

Auto gen max. All scenery full snow hard winter. No OOM.

If it's global it's not a problem in fsx that's for sure.

But I will try your flight out tomorrow night for you. In winter and summer and report back.

I'd like a add a little advice here or actually cite NickN's "bible" as a way of matching your hardware's capabilities to any flight sim app. First of all, do not assume that just because you installed and ran P3d2 that somehow LM figured out the default settings that will work best for your hardware.

 

Sure, LM probably figured out your maximum screen resolution, but unlike other modern 3D apps, they don't seem to have an algorithm that matches the in-app P3d2 settings with your specific hardware. Most of the sliders are somewhat in the middle of the range, but not all are. LM has no clue as to what image quality is acceptable to you and your hardware. Some flight simmers might tolerate 12-15 fps and be able to look at an incredibly realistic simulation of both the aircraft and the environment. Others would rather have a finely tuned, crash-resistant experience and get 30-40 fps, but by doing so, sacrifice some "eye candy". It's all personal preference. Do you fly complex aircraft? Do you fly in and out of big airports? maybe you just fly a simple GA plane in rural areas and you don't care whether other aircraft are visible. How could LM know exactly what your experiential goals are? And even if they did, they can't be cognizant of your hardware setup.

 

But back to the "advice". First of all, if you already messed with the initial default settings, rename Prepar3d.cfg and let the app rebuild it from scratch. Now, open the in-app display settings and turn everything down to levels like "sparse", "medium", "normal" or even "low". If you want to be more methodical, go to this thread:

 

http://www.simforums.com/forums/solved-blurry-terrain_topic45007.html

 

and scroll down to NickN's posts about configuration, as he has good ideas as to what settings should be turned down initially and which have little effect on performance, image quality, CTDs and OOMs. P3d2 is a bit different, because of it's heavier use of your GPU than FSX's use, but the general concept is the same. This process is not called tweaking, but rather tuning. You start lower than the target values and work your way towards the targets. A good number of people here start with the default values and work their way upward, a process that is designed to eventually fail and definitely cause frustration.

 

 

We EXHAUSTIVELY tested out of the box, and with several addon developers. However, some legacy addons that work just fine in FSX or 1.4 might cause crazy memory leaks in v2 - it's a possibility. They might also do things that used to be supported, and we might've missed something with backwards compatability. We're seeing a lot of OOMs reported with weather addons, so we'll partner with those devs and see what the culprit is and work to get it fixed. Same as we've done with scenery and aircraft devs too, it's a never ending cycle  But a challenge we are excited to meet and are up to and work on every single day.

We sincerely appreciate your support and you as a customer! Keep the feedback coming, if you see wonky things happen with addons, try doing it without them, or tell the addon providers to come find me and we'll partner with them to work out the issues that might have come up.

Wes Bard

Software Manager - Prepar3D® Team

 

This statement is so powerful IMO. I had remarked about this in another thread.

First defending their commitment of working hard to make it work. There is only so much you can do with beta and releasing to a gigantic amount of users with different PC scenarios, will unleash and find bugs. 

2nd, is the admission of possibility of missing something. Lots of devs everywhere blame the user immediately and can never admit the problem might be on their end. 

3rd Dynamic and observant. They see a big pattern developing with WX addons, and are taking the initiative to work with them all to sort through these issues. 

4th Is another assurance that they have dedicated commitment. This is so reassuring for the future.  And the excitement and enthusiasm they have embracing not just corporate clients but simmers. They mentioned they appreciate the help that users are helping others on other forums (like avsim). Awesome. 

Good stuff to hear.

I've been tinkering and have pretty much found the slider limits that will keep me OOM-free.  I'm at a point where P3Dv2 looks better than FSX and flies far more smoothly, making me very pleased with the purchase.

 sooooooo.......... is there a reason why you posted that, but neglected to tell us what "limits" are keeping you OOM free? Im not sure what value your posts adds to this thread. Obviously most of us are having issues. Share your secret please. 

Interesting! Is that what was different to last week when you didn't have OOM's?

 

No, FTX Global was the first add-on I installed after checking P3D ran fine. I did so because it was the only 2.0 ready add-on. The difference with last week is that I added an add-on plane to the bunch, Norway freeware and heavy weather. And after my testing from yesterday I conclude that something in FTXG is giving a memory spike: during the last week my VAS was moderate because I didn't have those add ons yet and so the spikes, if they were there, didn't peak to the VAS limit. However, not I've got more add ons in play, the spikes DO reach the limit and hence the OOM. 

 

The idea of a spike suddenly going over the edge seems a right one because usually VAS slowly builds up and it may also be an explanation for PE showing odd (low) numbers for VAS at the time of the OOM: VAS wasn't slowly build up but jumped and that spike might not be totally seen or measured by PE which is why the numbers were off. Just guessing.

 

 

The first time, I changed from my home location (it's summer here now) to ENBM and sat on the runway as the new winter textures loaded. Frames solid at 30FPS. Headed west and within 3 minutes my frame rates plummeted to 10 to 13! Choppy ride indeed.

 

Second time, I changed the textures to summer and within 3 minutes there was a slight drop in frames to 25 or so. Nothing less.

 

I dont have time for a few days to do more, but I wonder if there is a problem with FTXG winter textures? Try the same flight in summer and see if all is ok?

 

Interesting, thanks for testing. I did fly with summer textures btw. That frame drop on its own is odd already. Did you use a default plane or an add-on? Of course the frame drop could also have come from a weather add-on because a few of them seem to have problems in P3D.

 

I will give it a go tomorrow night for you J.

Tonight I did a flight in fsx from KJFK fsdreamteam v2 to flightbeams KIAD a 4096 airport in the PMDG 777, with opus ofc.

Auto gen max. All scenery full snow hard winter. No OOM.

If it's global it's not a problem in fsx that's for sure.

But I will try your flight out tomorrow night for you. In winter and summer and report back.

 

TIA. I never had OOMs in FSX though, so I think the problem has to do with FTXG in P3D itself. Some memory leak. It could very well be that there is only ONE little file in the FTXG that's causing this problem! It's too bad if FTXG is really the cause because default textures suck big time… I really don't want to fly with default textures! I wish there was a way to monitor or check which files are loading at a certain time? There must be a way for devs also to check things like this!

 

Anyway, as I said and as Wes said in his quoted posts: P3D 2.0 seems to be rock solid and if someone here had to dial down settings to prevent OOMs, they must have been caused by an add-on and not P3D itself because I can't get P3D default to OOM. Seems you were right, Brian Doney...!  ^_^

 

Still, I would like to see some more P3D/FTXG users test this. It could very well be (I guess) that FTXG only causes problem on my PC for some reason.

I have FTXG installed as well as FSDT and FB airports and the VAS is very well behaved.  Im using FSUIPC to monitor it right within the menu bar that is constantly updating and it always has at least 1gb free. Could be a glitch in the area your flying in?  Also Mr Bard said that weather engines are not behaving too well at this point. But at least they are more than willing to work with them and figure out the issues. Such a pleasure to see. 

 

Btw, Jeroen, Great humble attitude on that OOM thread at the P3D forum. Dont see and hear that often.  And they didnt take offence, but very professional, and courteous, and set the matter straight.  Clearly they very willing to cooperate with FSX users.  (although its funny they keep using "the other platform")

 

 

Could be a glitch in the area your flying in?

 

Could very well be! As I said, maybe it's just one file causing my problems. So if you find the time to fly around ENBM for 10 to 15 minutes (set the sim to summertime), be my guest.  ^_^ Just like you there are others who don't have any problems with FTXG and I understand (or at least presume) it has been thoroughly tested during beta. I do wonder though if you did lower some settings to avoid OOMs and if you ever had one in P3D?

 

And yes, LM is very willing to cooperate with us all: it's a great experience after never having real contact with the devs of FSX (apart from Phil visiting the forums sometimes). Not used to this at all!  ^_^​ But very positive and they really are committed to making this work for everyone!

BTW I posted about this on the Orbx forum and asked if they can help me how to properly test this. It's of course always better to take this up with the dev instead of speculating about it on another forum…  ^_^

..... Just like you there are others who don't have any problems with FTXG and I understand (or at least presume) it has been thoroughly tested during beta....

Jeroen

 

I'm beginning to doubt how well it (and other products for that matter) has been "beta tested" particularly given the fix list that JV has just posted-all 3 of those issues should have been picked up in beta imo!!

 

I see you've also asked them re the texture loading too...great post and I'll be watching that with interest.

 

Chin up pal...you'll get it sorted!!

 

Regards

 

Steve

 

 

 

 

Yes, I saw those three fixes too. It's a bit odd indeed. 

 

We'll see how it all works out! And I indeed hope to get it sorted…  ^_^ As I said, those default textures don't cut if for me.