Quote from the LM forum:

There are two major things in v2.1 that we are currently working on.

1) The new validation we put in to help folks build better content actually rendered a lot of older content unoperational. Long story short, old comments in gauges and panels (that are technically errors to the compiler, but were never reported so no one really knew) could render parts of them non operational. We continue to add to our ContentErrorLogging system (search for it in the learning center if you're not sure what it is) to report warnings and errors to content developers. Little things help add up to OOMs, performance issues, etc, so we want to give as much debug information to content developers as possible so they can make the most optimized content for Prepar3D v2. We are going to keep looking into making this easier and more effective. But, in the mean time, we've actually already fixed this issue, but are sending the patch out to a couple third parties to help us verify everything is back to normal.

2) Paging/stutters/OOMs/etc. We are looking into this. If you basically 'outkick your coverage' (american football term) then you can get in a bad state where your system can't keep up with paging everything in. We are working on continuing to clean this up and make it better. We also realize other folks are having stutter issues and the like, and are looking into all of this. We will involve more folks in helping us test this, as it has a LOT of variables.

 

Original post here: http://www.prepar3d.com/forum-5/?mingleforumaction=viewtopic&t=5696

Great stuff, that kind of support for their product is refreshing to say the least.

 

Sent from my Mobile thing

I appreciate the update on progress.....but

does not look like anything to remedy OOM's escallation will be out soon?

I appreciate the update on progress.....but

does not look like anything to remedy OOM's escallation will be out soon?

 

sounds like they still blame us and our "settings" for the ooms...

Read it again, the adjustments will ease the OOM load. There is nothing that can be done for anyone who has an FSX sliders right complex, but hopefully this fixes will enable us to increase the sliders further without bleeding memory.

 

Sent from my Mobile thing

Read it again, the adjustments will ease the OOM load. There is nothing that can be done for anyone who has an FSX sliders right complex, but hopefully this fixes will enable us to increase the sliders further without bleeding memory.

 

Sent from my Mobile thing

 

But how much are they going to ease the OOM load? Bringing it back to 2.0 levels is not enough; it will definitely be much better than 2.1, but still worse than FSX.

 

I'm hoping that this is not the last patch. In the DirectX 11 developer blog they promised lots of future graphical enhancements.

Edited February 25, 201412 yr by ChaoticBeauty

This is good news!

Good news. I know LM is working hard to correct a lot of issues that belong to them. I backed off a little on my sliders and no OOM's.  I downloaded 2.1 version the day it came out and I have only had one OOM and that was when I was testing the the sliders to see how far I could go before an OOM.

Its refreshing to see LM's responsiveness to user of its software. Hopefully P3D will only get better.

Excellent news! Keep up the good work P3D-team!

Good news. I know LM is working hard to correct a lot of issues that belong to them. I backed off a little on my sliders and no OOM's. I downloaded 2.1 version the day it came out and I have only had one OOM and that was when I was testing the the sliders to see how far I could go before an OOM.

Good advice.

But how much are they going to ease the OOM load? Bringing it back to 2.0 levels is not enough; it will definitely be much better than 2.1, but still worse than FSX.

 

I'm hoping that this is not the last patch. In the DirectX 11 developer blog they promised lots of future graphical enhancements.

you also believed in the Mayan calendar, right? who says it is the last patch or what level of fixes they are providing?

how about we wait, even with your half empty glass, and give them a chance to work through the issues? the other option of course is going back to fsx and waiting for the aces team to do the same.

you also believed in the Mayan calendar, right? who says it is the last patch or what level of fixes they are providing?

how about we wait, even with your half empty glass, and give them a chance to work through the issues? the other option of course is going back to fsx and waiting for the aces team to do the same.

 

That first line was kind of harsh, don't you think? 

 

And many of us have gone back to FSX, and a more stable platform. I have never had an oom in FSX in the 7.5 years I have been flying it.

mayve harsh, but the incessant whining really gets boring. some people would complain even if told they were about to win lottery. we have a developer who is actively changing and supporting their product faster than X plane or fsx and people still complain.

how about we wait and let them fix it for everyone rather than complain that the upcoming patch will not be enough?

For some, the only possible fix is going to 64 bit. Anything but going to 64 bit is an extreme disappointment for them.

 

This may make a few of the posts easier to understand.

 

Hook