The problem with P3D is it doesn't actually appear to have been Beta tested at all, or maybe we're the Beta team? who knows.

 

I suspect most of the beta testers were add on vendors... Having mostly  addon vendors as beta testers is, they would test mostly their products to make sure they work with P3D. I doubt Orbx or Flightbeam would install others add on and test P3D.    If they had included lots of us to Beta test we would have alerted them with more issues to fix. This is of course purely my conjecture.

 

If they had Megascenery they would have noticed how the water from MS and default P3D  does not merge well... or the rain effect in wideview or even OOMs when we combine addons. 

Two days ago I couldn't honestly answer this. Today.. I can.. No you won't see a reduction.  You may even see an increase

 

So that means that they barely touched the memory management system at all?

It's an emotional rollercoaster reading your FS posts Jeroen :lol:

 

OpusFSX sure does add a lot of volumetric fog now.     So just turn it off / reduce it. 

 

It's clear from your posts that your hobby is all about top end visuals;  nothing wrong with that, but that is probably why, the extra volumetric fog has pushed your system over the edge.

 

I hope you find peace again soon    - on any sim!  :smile:

Have you figured out yet why no-one has responded to your post? This thread is about some poor soul suffering from OOMs <_<

Be nice to test a flight or shoot an approach or something  other than roll out and rotate, but my ffing Joystick doesn't work. But thanks for response :mellow:

I'd stop doing that if I were you and start simply fying. Those short testingflights will turn out to be useless when you start doing some normal flights. You'll encounter situations you will never encounter in those short testflights.

Lol I know this is the correct approach. I have a free day tomorrow and will use it wisely. My plan is to simply delete the cfg and let P3D build a new one. Then I'm going to fly one of my standard flights with the default settings which I have done many many times. Sit back and simply enjoy it.

 

I'm not sure which version of opus I have. I did update it a while back but as I use as2012 exclusively for FSX it's not something I've used much but will try it first just to see how it goes.

 

Someone mentioned 'burn out' I call it my natural curiosity. Although I brought it on day one, due to circumstances I've actually only been able to play around with it for a few hours ever since.

@J van E:

 

Ever thought about your PC is actually not really good enough to run the ambitious settings you demand from P3D?

I mean, an i5 2500K - a 3 year old GTX580 card with 1.5 VRam, and on top, 1600 Mhz CL8 Ram...

 

Turn down the settings, or get new hardware, or maybe better: 

Back to FSX.

Good point

@J van E:

 

Ever thought about your PC is actually not really good enough to run the ambitious settings you demand from P3D?

I mean, an i5 2500K - a 3 year old GTX580 card with 1.5 VRam, and on top, 1600 Mhz CL8 Ram...

 

Turn down the settings, or get new hardware, or maybe better: 

Back to FSX.

 

Not saying he shouldn't turn down settings but your frowning upon his hardware is a little pompous.. Take away the 580 and if he just upgraded just the CPU and RAM the results he might see (and not a lot) is in benchmarks due purely to architecture changes, HT, and nothing more. An i7 isn't magically going to make P3D use less memory, and some 3000MHz Gskill RAM won't help that either.. His card is by no means top of the line but it isn't like he's running a Voodoo2 in there either.

 

 

So that means that they barely touched the memory management system at all?

 

They did, but added a lot more overhead to the core which counteracts any memory management improvements

Sorry I just had to laugh when I saw the title and the OP. Jeroen, you just need to step back and take a breather. Whoa. One minute your like a kid in a candy store and next your raining evil on it. I have installed REX textures and I have opus weather and in heavy clouds and rain at CYVR it does dip but still not enough to make it unflyabble by anymeans. And that was with the ERJ. FSDT CYVR and FTXG is installed as well. I am no where close to the VAS limit. Now I just found a smoking deal on a 770 on Craigslist and I think that makes a huuuge difference particularly when encountering clouds.

 

Couple things I would do since you've done all these tweaks, is rebuild a new CFG. I didn't have the latest beta of opus so maybe that's an issue? Revert to a previous version. And as others mentioned dial back the settings. Repeat. Dial it back. Seems that a setting still means a higher value than fsx. I have never got an OOM yet and I have quite a few payware already. Put in that tweak into fsuipc to see the current remaining VAS in the title bar. Its worth it. You can monitor it that way.

 

The losing focus is a problem so click on the menu bar or main screen occasionally if the fps dips.

 

The biggest thing we can do is give LM feedback on any issues. If there is only a few reporting something its lower priority. As Arwen pointed out, its only a week by this evening. Let the dust settle. Let the 3PDs find out the differences and adjust accordingly. I've read a number of dev posts that are so excited on the possibilities now with programming language I didn't quite get but all kinds of limitations of fsx are gone. There is enormous potential. Give it some time.

 

V2 is by no means perfect. To expect such is unreasonable. Heck its arguably beta materiel but hell we've been complaining about fsx for 7 plus years of all the tweaking,limitations,bugs,instabilities, with a rinse repeat recycle mentality and now LM has taken the reigns and we jump down its throat. Step back. There is no way they could sort all these issues or find them without it going on to many many machines.

They are more than willing to listen and resolve the issues. That's a lot more than I can say about Microsoft.

 

 

In case you are talking to me ^_^

 

Sorry Jeroen, I thought Josh was your abbreviated name.  My mistake.

 

I've left my LOD at the default 4.5.  I've also found that any attempt to control my 580 from NI seriously impacts frame rates.  If I leave everything Application Controlled then I can happily maintain 30fps in most situations.

 

I'm still in two minds as to whether to order a 770 or 780 ...

What is embarrassing is a lot of people are getting this with default scenery and even planes and more and more and more lower settings to derpy levels. Could you imagine forking over for  a batch of professional licenses and  setting this up in a class room training session and having a student who pays a handsome chunk of change for flight lessons get an OOM error?

 

The difference is that aviation training programs don't need HD clouds and textures and maxed out autogen to fulfill its' purpose in the classroom.  Desktop simulation in the training environment is primarily a procedures and familiarization trainer (e.g. maneuvers, cockpit familiarity, checklist procedures, navigational training, etc).  Ever used one at a flight school?  It's pretty much FSX or X-Plane with every slider on low.  They want smooth performance (for instrumentation purposes) and don't care what it looks like outside of the cockpit.  LM knew the market they were developing for when they chose to develop a 32-bit platform (as opposed to a 64-bit).

@styckx: 

 

Why is that "pompous" ? - and I really don´t frown, it´s just a matter of fact IMO.

 

http://forum.avsim.net/topic/415988-haswell-i7-4770k-vs-i7-920-960-bloomfeld/page-2

 

Upgrade is needed, i5 is what? - 3 year old tech now?

@styckx: 

 

Why is that "pompous" ? - and I really don´t frown, it´s just a matter of fact IMO.

 

http://forum.avsim.net/topic/415988-haswell-i7-4770k-vs-i7-920-960-bloomfeld/page-2

 

Upgrade is needed, i5 is what? - 3 year old tech now?

 

It's still a very powerful system. You don't absolutely need a maxed out overclocked up-to-the-minute system to run P3D v2 or FSX at decent settings. The Sandy Bridge processors are still very powerful by today's standards. The thread you linked is about upgrading from an old Bloomfield CPU, which is much older and definitely a lot slower than Sandy Bridge.

 

Also, the i5 has always been around. It's essentially an i7 without hyperthreading, which makes little or no difference in FSX and P3D.

Again, I would have hoped that for "simulation" purposes the ATC and flight models would have been the focus. But clearly the graphics WERE the focus of this upgrade. If we are meant to turn all the sliders down to zero, why spend so much time on moving the workload off the CPU and onto the GPU? I'm not so sure that this wasn't aimed at folks like us as much as it was aimed at the commercial market.

 

And yes, I have indeed used a simulator at a flight school.  ^_^  

 

And again, I fully support P3D, hope it succeeds and will continue to fly it and comment on it. I am not a hater in any sense!

I've found some serious bugs in P3D2. I run moderate settings, and have less clouds, autogen and water effects than I have in P3D1.4. Only cockpit shadows enabled. No addons installed. Just a joystick.

 

1) Parked at KJFK I turned off everything and pushed all sliders to the left. Then I gradually increased settings. I went from VAS of 1,4GB to 3,4GB. Not surprising, but when I went back and turned down all the settings. Guess what, no VAS change, still at 3,4GB with zero traffic, zero shadows, zero autogen etc.

 

2) Various flight with moderate settings. Start off with VAS of around 2,0-2,4GB. As the flight progresses, VAS increases. A few times adjusting settings, checking map view, I'm going over 3 GB. Reset flight, still at 3GB. Save flight, reboot P3D, and I'm back to normal levels.

 

Something is wrong as P3D seems unable to clear VAS usage.

Thanks for all the support, tips, etc. all! ^_^

Concerning dialing back the settings and similar tips: I can tell you that's not the problem. I already dialed back my settings before I started to get problems. The OOM's came after I started to fly in heavy weather. It seems the clouds are causing havoc somehow on my PC. I even went as far to completely disable tesselation, lower the radius, shadows off, autogen down etc and even when I flew the default Maule... OOM!

 

The coming days I will fly with less clouds and certainly not OpusFSX and see how it all goes. I didn't have OOM's at ALL this week (and never had them with FSX) but as I said, when I loaded heavy weather, the problems began. I will also do some more testing with REX because I have the idea the problem mainly pops up when I have REX clouds installed. (I use REX only for the clouds.) Whenever I restored the default clouds, I seemed to get no OOM's or less: I'm not sure but I will test that later on. I do have a flight saved with ALWAYS gives me an OOM in a few minutes so that's easy for testing. ^_^