The real question within my question is does LM really need 64bit to accomplish its current commercial goals (rather than ours)

 

It's a good question, but if that were the case, 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?  

 

But I would think a commercial client would probably have a bigger budget for hardware ... but adding hardware isn't going the do anything for VAS.  As it stands right now, I've had to reduce features/3rd party products to "try" and fit in the VAS limit ... my single GPU is now more than capable of running acceptable frame rates ... effectively rendering my need for a 2nd GPU unnecessary ... yet LM are spending resource on the 2.1 patch to provide multi-GPU utilization??

 

To some degree they already have restricted the LOD setting to 6.5 max which shows it's weakness when you load up photo real scenery.  So the option of NOT running any AutoGen and just go with Photo scenery has been handicapped.  I can make photo scenery look much better in FSX DX10 than I can in P3DV2 DX11.  But if they allowed higher LOD, we'd hit the VAS limit even sooner ... but again, isn't that another valid reason have a 64bit path?

 

I did a little XP10 64bit today, it looks great at night, but I tend to agree when it comes to day it's missing out ... even without as much 3rd party support, XP10 does NOT have the lighting that P3DV2 offers ... I get a much better sense of "depth" in P3DV2.  But I also fired up FSX today and I guess I've been spoiled by the lighting in P3DV2.

 

Anyway, back to more positive thoughts on VAS reduction ... something I hadn't done yet, modify the camera.cfg and added the CycleHidden=Yes entries so that I only ever cycle two views, VC and Locked Spot.  I noticed that the standard 4 view cyclic would increase VAS by 400MB.  I've also disabled FTX Vector, just too much of a VAS hit.

 

I'm looking at PFPX as my flight planner for P3DV2 ... anyone have thoughts about his product?   Will it run on a separate PC?  Does it provide P3DV2 compatible .PLN?

 

 

I'm wondering if its because I'm mostly flying in the Hawaii area that I don't have as much OOM's as some of you guys who may fly in very dense areas such as NYC or LA?

 

Yeah, I rarely get OOMs when I'm Island hopping ... St.Maarten for example or Hawaii, never an OOM even with 3rd party scenery not designed for P3DV2.

 

Anyway, back to more positive thoughts on VAS reduction ... something I hadn't done yet, modify the camera.cfg and added the CycleHidden=Yes entries so that I only ever cycle two views, VC and Locked Spot.  I noticed that the standard 4 view cyclic would increase VAS by 400MB.  I've also disabled FTX Vector, just too much of a VAS hit.

 

 

 

Rob, I'm wondering if your view settings contribute to your problems? I only use zoom x1 and widescreen. On my little puppy (i5 oc to 3.3 and a GTX 560Ti), I've not had an OOM yet? I have however seen my framerates plummet on occasion. It is an area I don't fully understand, but I am sure I read somewhere that a zoomed out setting can cause problems in high density areas.

I have however seen my framerates plummet on occasion. It is an area I don't fully understand, but I am sure I read somewhere that a zoomed out setting can cause problems in high density areas.

 

Sadly my OOMs were using one view and only one view with a zoom of 0.40 in VC.  At first I thought that it could be the TrackIR setup, but tried without TrackIR and didn't really see any significant difference in VAS.

 

Just about to run a test flight from KSFO to KPHX using the BAe-146 (QW version) ... clear skies, oddly clouds seem to make very minor differences in VAS usage.  Wish me luck

 

EDIT: I'm trying NOT to use the same default A36 that I've been using in many flights ... I know I'm going to want to use/purchase 3rd party Aircraft ... espeically the PMDG release when available, so I'm trying to make P3DV2 work with what I know I'll want to use on a "regular" basis.  If I fly the default A36 all the time, that's skewing my real world experience and what I want to be able to do with P3DV2.

Anyway, back to more positive thoughts on VAS reduction ... something I hadn't done yet, modify the camera.cfg and added the CycleHidden=Yes entries so that I only ever cycle two views, VC and Locked Spot.  I noticed that the standard 4 view cyclic would increase VAS by 400MB.  I've also disabled FTX Vector, just too much of a VAS hit.

 

 

Rob, this sounds interestiing. However, i edited the cameras.cfg in the way you did but VAS still is the same as before.......

I only use zoom x1 and widescreen.

 

I don't think that makes a difference to VAS. It will make a difference to performance (since less has to be shown on screen) but everything around you will be loaded into memory anyway.

 

 

 

i edited the cameras.cfg in the way you did but VAS still is the same as before.......

 

I think Rob means that when you actually cycle through all the views, VAS will go up: it's not that simply editing the cameras.cfg will magically lower VAS. Instead of editing the cameras.cfg you might also NOT cycle through all views (like I do) to prevent VAS from going up. However, if you frequently use a specific view which is not the first in line, editing the cameras.cfg might help because you don't have to go through views you don't need but that will raise VAS.

 

 

Rob, this sounds interestiing. However, i edited the cameras.cfg in the way you did but VAS still is the same as before.......

 

Interesting, did you edit the cameras.cfg for the aircraft you were using also?  You need to allow each view you cycle a few seconds to start loading textures -- 4 views will consume about 400MB additional VAS in my setup.  Also do NOT edit the cameras.cfg in your P3DV2 root, only the one in ...AppData\... and the specific aircraft one.  This ensures I only have two views during a cycle (S or A key) ... I can still change to other views obviously, via the menu.  

 

I did find another bug tonight ... if I save a flight while in external locked spot view, exit P3DV2, then load the flight directly from desktop/folder (double click the .fxml to launch) it brings me back to my external view, but if I try to cycle (S or A key) views it just flashes some objects white and the view never changes.  Work around was to manually select the view (VC in my case) from menu which would then load the VC.

 

Well I was about 3/4 quarters of my way thru KSFO to KPHX flight and must have accidentally hit the ATC IFR destination change button and P3DV2 crashed ... got the known bug:

 

Faulting application name: Prepar3D.exe, version: 2.0.9448.0, time stamp: 0x528edbe6

Faulting module name: uiInterface.dll, version: 2.0.9448.0, time stamp: 0x528edbd9

 

Oh well, flight saves every 2 minutes, so I'll start it up again tomorrow ... too late to finish this flight tonight.

 

 

I think Rob means that when you actually cycle through all the views, VAS will go up: it's not that simply editing the cameras.cfg will magically lower VAS.

 

Yes, that's exactly what I mean, sorry if I wasn't clear.

The key to implementing this compatibility process is development resources ... I have no idea the size of the development staff working on P3DV2 ... so far I've counted up 5 names/references (there could be more).

Rob, there are twenty names engraved on the "foundation stone Easter Egg" included in Prepar3D v2.

Installed FTX AU SP4 for P3D v2. Got OOMs every few minutes. I got them so often at one moment that FSUIPC didn't even get the time to create new autosaves. Finally decided to lower autogen from Very dense to Dense... and after that OOMs stopped. I only flew for half an hour though. FTX is very autogen heavy but still... this is crazy. Something is terribly and utterly wrong with P3D v2. What's the use of all those new options when you can't even enable them on a fast PC due to VAS problems. Let's hope LM fixes this soon... if they can.

I think Rob means that when you actually cycle through all the views, VAS will go up: it's not that simply editing the cameras.cfg will magically lower VAS. Instead of editing the cameras.cfg you might also NOT cycle through all views (like I do) to prevent VAS from going up. However, if you frequently use a specific view which is not the first in line, editing the cameras.cfg might help because you don't have to go through views you don't need but that will raise VAS.

 

 

Interesting, did you edit the cameras.cfg for the aircraft you were using also?  You need to allow each view you cycle a few seconds to start loading textures -- 4 views will consume about 400MB additional VAS in my setup.  Also do NOT edit the cameras.cfg in your P3DV2 root, only the one in ...AppData\... and the specific aircraft one.  This ensures I only have two views during a cycle (S or A key) ... I can still change to other views obviously, via the menu.  

 

 

Gentlemen,

 

thank you for clarifying that :Peace:

 

I edited on aircraft.cfg of my AXE and it indeed seeams to use little lower VAS.. Will continue testing..

 

Thank you !!!

 

Carsten

 

 

Installed FTX AU SP4 for P3D v2. Got OOMs every few minutes. I got them so often at one moment that FSUIPC didn't even get the time to create new autosaves. Finally decided to lower autogen from Very dense to Dense... and after that OOMs stopped. I only flew for half an hour though. FTX is very autogen heavy but still... this is crazy. Something is terribly and utterly wrong with P3D v2. What's the use of all those new options when you can't even enable them on a fast PC due to VAS problems. Let's hope LM fixes this soon... if they can.

 

That is very troubling :( I've never had an OOM in FSX no matter how hard I pushed it. I've ran Orbx AU with Orbx YMML at max settings, or near as... and the only thing I suffered was awful performance [maybe 5fps] The only thing I was not running was complex aircraft... as in just small GA stuff from Carenado or similar.

 

I was waiting for FTX PNW but I might just try AU, even though I'm not that interested in flying there, just to see what happens. I've yet to see an oom in v2, even running max autogen, coupled with full UK photoscenery and UK2000 airfields, so it will be interesting to see if it will push it over the edge for me too.

 

I can't see how this is system specific, so it seems LM will have to address this somehow, or quite frankly we're buggered :unsure:

 

It will be interesting to hear others experience with AU and P3Dv2.

 

 

I've yet to see an oom in v2, even running max autogen,

 

The odd thing also is that some don't seem to get any OOMs at all. BTW In all my years of flying in FSX (which was from the day it was released) I never ever had an OOM. I didn't see that OOM message until I got it in P3D v2. I had times where I had LOADS of addons active in FSX and no OOM at all.

I can't see how this is system specific

 

 

It's not entirely system specific -- well OS version and physical RAM and VRAM do play a part - but it's assumed (perhaps falsely) most people know you need 4GB VRAM, 8GB RAM, and a 64bit OS to run P3DV2 well.  

 

The thing is when many folks post "never had OOMs" they rarely include all their settings, add-ons (and settings within those add-ons), config changes, etc. etc. etc. ... I don't blame you folks for not doing so because it can be extremely time consuming an exhaustive process to post every single little detail about your P3DV2 configuation, add-ons and hardware setup.

 

A good example of what I mean, take the Sim720 Control panel (see pic below), EGPE Inverness (this is listed as P3DV2 compatible).  If I check a single additional option say "Static People", I will OOM at that airport (even in the default A36) within 3-4 minutes.  Now consider that's just one add-on airport with configuration options ... now multiply that by ALL the other combination of variables (display settings, screen resolution, lighting settings, reflections, shadows, scenery enabled/disabled, DLL.XML, EXE.XML and on and on -- all these contribute to VAS usage) and you can easily see that statements like "never had OOMs" doesn't really provide any helpful context.  Not trying to be harsh, but I do understand why people don't post everything ... but the times those people do start posting "some" (not all) setting one soon see their are differences.  But sometimes even the smallest of a difference in one persons settings can result in major VAS differences.

 

Now add another huge variable in the OOM equation, the very specific flight location and path, views used, aircraft used, FMC no/off, GPS on/off, etc. etc.  And finally many of us manage all these variables just for a specific flight from A to B so we can get the best of what we have.

 

I can only hope I'm not doomed to do this careful configuration process for another 8 years ... because frankly, I just don't have the time anymore and ultimately will stop flight simming which means no more 3rd party purchases.  Being around AVSIM for a while, I have a hunch many have come and gone exactly because of this process having to make it fit in a 32bit address space.

 

 

Rob

 

EDIT: And this is no detriment to Sim720, they just wanna build the best reproduction of Inverness they can ... why?  Because that's what sells and what customers want.

 

The odd thing also is that some don't seem to get any OOMs at all. BTW In all my years of flying in FSX (which was from the day it was released) I never ever had an OOM. I didn't see that OOM message until I got it in P3D v2. I had times where I had LOADS of addons active in FSX and no OOM at all.

 

 

This is an interesting point and FSX is a 32 bit app (I've bolted on lots of terrible stuff and hadn't hit an OOM either). I wonder if the way the "no popup" autogen is being batched and loaded based on the LOD radius has something to do with it...

 

Rob, another thing - do you have another testbed to try Win 8.1? I haven't hit an OOM yet with P3D (with building autogen at very dense, REX, FF ORBX regions, and Opus weather), even though I have a much lower-end rig than you, and that's the only other thing I can think of. Also, do you have any TML tweaks in your cfg?

 

 

The thing is when many folks post "never had OOMs" they rarely include all their settings, add-ons (and settings within those add-ons), config changes, etc. etc. etc. ... I don't blame you folks for not doing so because it can be extremely time consuming an exhaustive process to post every single little detail about your P3DV2 configuation, add-ons and hardware setup.

 

I posted my entire CFG file, as I recall.

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. Maybe some will be lucky and not suffer OOM's in v2 but it seems, as has been stated many times, that LM's changes and additions to the platform have pushed it into an area where they are far more likely to be encountered... even if you didn't see one in FSX.

 

I'm not being smug, or clever in saying I've never seen one, it is simply the way its been, but reading all these accounts of them cropping up in v2 makes me worry this will not be the case for much longer. So far I know I have not pushed the sim very hard, and my needs are simple compared to some, so maybe I am less likely to be troubled.... I know I will be seriously put off using v2 if I do start getting them however.

 

I will download Orbx AU later and if I can max it out and not suffer a single OOM after several hours flight, I will gladly post anything anyone wants to know, if it will be of use.