I posted my entire CFG file, as I recall.

 

Yes you did Sir and I wasn't trying to suggest anyone should have to do this ... kinda the opposite actually ... it's just that there are too many other variables beyond one's CFG that can play into the equation of VAS.  I think it's assumed everyone knows how to avoid OOMs by now, just keep turning the sliders to the left and avoid add-ons.  Best analogy I can come up with is a race car driver saying "I've never crashed" and the common response from a team owner, crew chief, or other race car drivers would be "then you aren't trying hard enough"

 

 

 

You could list every last detail and it would not necessarily be of any use at all, as there are too many variables, within the system, the sim and the way you use it, so I doubt posting full cfg's etc. are going to be of much use.

 

Agree, that was sorta my point - just too many variables ... but computers don't operate on luck, cause and affect (1 and 0's) - there is always a reason.  The reason in your case is exactly what you've stated, you don't push it - it meets your expectations.

 

I am a little surprised P3DV2 had so many rather obvious bugs ... but in my case I think it was all the bugs combined with regular OOMs that has probably been the primary cause of my frustration with LM.  But they are at least being responsive ... so who knows what the future holds ... I'll "try" to stay positive, but I don't know how long I can keep it up ... I may end up just being another causality of expectations.

 

Anyway, I'll continue to share any findings I have on the VAS front and possible ways to help others maximize their flight sim experience with P3DV2.  But honestly, I really don't like having to do these long threads about VAS and how to work with it or under it ... like I said before I've been doing that for 8 years with FSX and it's frankly beginning to wear on me and hence my less than positive embrace of P3DV2 in it's 32bit form.

Why not just sit back and wait patiently for the first patch to be released? It may well turn out that many, even if not all, of these problems might be mitigated or fixed?

Why not just sit back and wait patiently for the first patch to be released? It may well turn out that many, even if not all, of these problems might be mitigated or fixed?

 

They haven't said anything about improving the memory management system in 2.05 or 2.1.

They haven't said anything about improving the memory management system in 2.05 or 2.1.

 

Indeed. I've read nothing about fixes that concern VAS. But we'll see. I hope they will hurry a little with the patch though because in all honesty the thought to ask for a refund if that patch isn't here before my 60 days period has ended is crossing my mind more and more... The only thing that is holding me back is that I don't know where to go then because P3D v2 has spoiled me. I can't imagine going back to FSX. But sticking with P3d v2 like it is now it becoming harder and harder. This evening I did a flight above FTX AU with the default Acclaim because with the A2A C172 I got OOMs with autogen at Very dense. But I also got them with the Acclaim. So ONE scenery addon and you have to lower settings to medium otherwise things crash. I also had to totally unexpected CTD's so... I am starting to lose my religion here... ^_^

Not specifically mentioned true, but nonetheless the huge list of fixes already done, plus the ones they are still working on just might wind up minimizing the existing VAS chaos...

In my experience, often seemingly unrelated "fixes" often have unanticipated consequences. :LMAO:

Instead of continuing to beat my head against the wall, I've just gone back to my development work for FSX. Eventually L-M will get these growing pains dealt with. These incremental updates aren't costing me anything but time. I'm simply not going to loose any sleep while waiting. Life is too short for that. ^_^

 

 

Not specifically mentioned true, but nonetheless the huge list of fixes already done, plus the ones they are still working on just might wind up minimizing the existing VAS chaos...

 

That's my hope also ... but I'm going to remain cautiously reserved after reading about how memory allocation/release is a handle in C/C++ (it's that information that really made it clear to me 64bit is a must as the problem is more fundamental than just code optimization and fixes).

 

I know my continued push for 64bit isn't popular to some even annoying ... but "it's time", we really do need to get our flight simming world into a 64bit future (said it 8 years ago and saying it again today) and LM have avoided making any official comment to such a future.  And that brings me to my real concern - 64bit isn't even officially on the plate ... I can patiently wait for patches and updates and new features (cloud shadows on water, oh boy that'll be another VAS consumer), I can do the VAS shuffle, I can avoid buying PMDG aircraft because of VAS usage, I can turn down the sliders ... this is exactly what I'm having to do (again).

Indeed. I've read nothing about fixes that concern VAS. But we'll see. I hope they will hurry a little with the patch though because in all honesty the thought to ask for a refund if that patch isn't here before my 60 days period has ended is crossing my mind more and more... The only thing that is holding me back is that I don't know where to go then because P3D v2 has spoiled me. I can't imagine going back to FSX. But sticking with P3d v2 like it is now it becoming harder and harder. This evening I did a flight above FTX AU with the default Acclaim because with the A2A C172 I got OOMs with autogen at Very dense. But I also got them with the Acclaim. So ONE scenery addon and you have to lower settings to medium otherwise things crash. I also had to totally unexpected CTD's so... I am starting to lose my religion here... ^_^

 

In 2.1 they'll introduce a small system which will tell you what add-ons to disable or what settings to turn down in order to stop OOMs. That's the only future "improvement" they're planning for Prepar3D 2.0's "robust memory management system".

 

Ask for a refund. It seems very unlikely that you'll ever be able to fulfil your desire; run FTX AU with the A2A C172 and high autogen settings.

 

I know my continued push for 64bit isn't popular to some even annoying ... but "it's time", we really do need to get our flight simming world into a 64bit future (said it 8 years ago and saying it again today) and LM have avoided making any official comment to such a future.  And that brings me to my real concern - 64bit isn't even officially on the plate ... I can patiently wait for patches and updates and new features (cloud shadows on water, oh boy that'll be another VAS consumer), I can do the VAS shuffle, I can avoid buying PMDG aircraft because of VAS usage, I can turn down the sliders ... this is exactly what I'm having to do (again).

Actually they did talk about a 64-bit version and it's still in their plans, it's just really far away. Prepar3D 3.0 probably.

 I think it's assumed everyone knows how to avoid OOMs by now, just keep turning the sliders to the left and avoid add-ons.  Best analogy I can come up with is a race car driver saying "I've never crashed" and the common response from a team owner, crew chief, or other race car drivers would be "then you aren't trying hard enough"

 

 

Beyond that, there is still a group of P3d2 users who get crashes for reasons other than pushing their hardware to the limit and/or using incompatible add-ons. That's just the nature of a new release of any app that allows the user so much flexibility.

 

To be honest with you, if I was LM, I would have encrypted the CFG file somewhere in another file so that users couldn't mess around with it. Many video games were set up like this, but then high end users found where the configuration file was "buried" and how it could be edited. But at least that took some effort.

 

Further, I would make sure that the app would only recognize certain video driver settings, so that people couldn't mess around with NI. Anything that needed to be changed would only be accessible from the P3d2 UI. But LM felt the need to keep the FSX tweaking community alive and I can see the benefit of that also.

.....I can't imagine going back to FSX.

 

 

This is the crux... I've been up and down like a roller-coaster with v2, and each time I'm about to chuck in the towel I load a flight and have a great experience... or load FSX and feel disappointed [or try XP-10 and feel sick ]. Maybe if I had gone for the 'pro' licence I would feel different, as that is a load of money if you're unsatisfied... I justify the licence I bought as I genuinely use the sim to teach my eight year old [as best I can] things about aerodynamics and flying in general, which is something he has been doing at school... so, my conscience is clear.

 

Today I had my first OOM, yeah baby :rolleyes:  But I had to force it... I downloaded OrbxAU-SP4 and set it up so I was attaining a satisfactory frame rate, which for me is to maintain 30fps or as close too as possible [20fps is my absolute min]... With that I flew for several hours with no issues at all (apart from some strange lines above Orbx trees when viewing them from below, and the odd agn spike)..... I then put everything up to max and took off from YMML... I was getting about 8-10 fps and autogen spikes all over the place, a total mess, but still no OOM. So I started cycling the views, and when I hit 'top down' and zoomed-out....BAM! my first, ever OOM.

 

So I re-started and put the sliders back to sensible levels and carried on OOM free, and this is what it looks like [below]. If it gets no better than this then I will be happy, as it still looks far better than FSX even with the sliders a couple of notches to the left from max.. or more.

 

I do hope LM improve things, and am sure they will, but for me its just something to relax with, and not get stressed-out over.... quite the opposite.

 

There is worse things in life than this... its also nice to be back in Orbx AU too, even if PNW is my favorite.

 

 

 

Today I had my first OOM, yeah baby

 

Welcome to club OOM-pa ... if you stick with the A36 it's pretty good in most situations and has a smaller VAS footprint.  Like I suggested earlier in this thread restrict yourself to just two views (spot and VC) helps.  And finally, use the FSUIPC autosave feature for those longer flights ... typically if I take off from a 3rd party airport, I will run out of VAS just as I approach my destination 3rd party airport, so the autosave feature really helps out here.  

 

Other 3rd party aircraft I turn down the autogen even more so I just have a couple of trees and a few houses, my airport -- it's pretty empty world, but works.  I fear what I'll have to do when PMDG and/or FSGRW release for P3DV2 ... at that point, I may have to do what I did in FSX, Photo Scenery and no Autogen at all.

 

And yes, P3DV2 can have good moments ... lots of little ones about 3-5 minutes long  LOL

 

But agree, can't get too consumed with this (which I often do) ... got plenty of other things to do in life.

 

Cheers, Rob.

 

 

Actually they did talk about a 64-bit version and it's still in their plans, it's just really far away. Prepar3D 3.0 probably.

 

Can you show me (link) where they have committed to 64bit ... I know they have "talked" about it, but I haven't read any accountable commitment to it.

Can you show me (link) where they have committed to 64bit ... I know they have "talked" about it, but I haven't read any accountable commitment to it.

 

http://forum.avsim.net/page/index.html/_/pri-news/lockheed-answers-community-questions-r1819

 

While they can't confirm its release date, it surely is in their roadmap.

Welcome to club OOM-pa

 

Why thank you... I feel part of the clan now.

 

But, with a degree of seriousness I do understand the frustration, even if I try not to get too emotionally involved. If this is your hobby and you invest a lot in it, then you want things to work. If I wanted to use PMDG or similar aircraft, as that was my point of interest, then it would be a different matter and I would feel rather dejected... I'm happy to bumble around in slow basic stuff, doing some sightseeing, or challenging myself in some interesting weather.

 

It will be interesting to see if the first patch will make a difference, even if it is by indirect action... memory leaks and other bugs (of which there is a huge list) may well be exacerbating the OOM issues... we shall see soon hopefully.

While they can't confirm its release date, it surely is in their roadmap.

Which means what exactly? I'd suggest that, at present, it's no more than a aspiration.

I'd question why include slider options that no one could obtain under a 32bit environment or provide for 4096 textures -- that only opens a door -- why code for a door they don't want open?  

 

Absolutely, unless they really believe there is enough upside in memory management improvements.   Seems doubtful though...

Absolutely, unless they really believe there is enough upside in memory management improvements.   Seems doubtful though...

They may simply laying the foundations for possible future growth. Which does not necessarily mean that growth is Immanent.

 

Not being a downer here, it's just I have seen us go off before expecting things not ever directly promised, then getting frustrated and angry.

 

Hopefully that's not the case here.