Terrifying indeed!   I see you were at 18.6 fps. How did FSX handle it before you went P3D2?

 

Terrifying will be trying the same scene with a complex addon.  I love to see what happens in that scene when ConcordeX is loaded up.  Too bad it cannot be installed in P3D at this time.

Terrifying will be trying the same scene with a complex addon.  I love to see what happens in that scene when ConcordeX is loaded up.  Too bad it cannot be installed in P3D at this time.

 

That scenery would OOM in FSX with the default trike. I remember the complaints when it came out.

X-Plane doesn't have the level of detail (remember, it's a "plausible" world and thus makes a bunch of crap up to fill in scenery).

 

"A bunch of crap up to fill in scenery ": :good:

 

http://forum.avsim.net/topic/427442-various-shots/

BTW, I went over to the P3D forums and found no posts referencing OOM errors, at least not on the first few pages.

 

You guys who are getting them need to do what they asked and go post about it. We have a developer willing to find and close memory leaks finally. Take advantage of it. Give them the situation you encountered it, what plane, scenery, etc.

 

As for why you are getting them and why people are seeing high VAS usuage, I suspect it's because default settings put LOD at 6.5 and TMR at 4096 in P3Dv2. In FSX, unless these are tweaked via the cfg, they are significantly lower (4.5 and 1024) and these are huge VAS suckers.

 

In FSX, I never got OOM at 4.5 LOD. I got them all the time at 6.5.

 

Lower these settings and see what happens.

They are not memory leaks. Memory leaks are a very specific thing and this is not it. It's simply overloading the memory, in a sense.

"A bunch of crap up to fill in scenery ": :good:

 

http://forum.avsim.net/topic/427442-various-shots/

 

You are using OSM in those shots, so that doesn't really contradict his assertion. 

 

OSM is nice if the area is covered well, you have the HD space for it's large file sizes, are willing to take the time to do it, and you are ok with very limited coverage. 

I can confirm that - though the spectre of OOM will never be gone until P3D moves to 64-bits -VAS footprint varies with the installed RAM of your video adapter. I just moved from a 1GB Radeon to a 3GB nVidia 780 GTX and there was a significant drop in VAS. No doubt, cards with 2GB or less will be caching texture data in precious system RAM (FSX-style). That cost can be steep if you're trying to shuttle 4K textures around.

Does P3D2 exhibit the same habit as FSX of slowly consuming memory over time (I hate to use the term 'memory leak' for fear of aggravating Tabs ) resulting in an OOM when you're T7 is on final approach into KJFK after a ten hour flight?

I've been starting process explorer at the start of quite a few testing sessions. On my system it starts at around 2.3

 

Because I'm trying lots of options during a session, Ive been adjusting settings then flying to see the result. This changing settings and flying is constant at times. I'm also going from airport to airport and checking the results to see what each setting does.

 

Although in say New York with shadows it raises to 2.4 It's very stable. To be fair it's very early days and I don't have any type of testing strategy in place.

Something's probably loading in that sucks up that remaining 600MB of VAS quickly before Process Explorer can show it. You're already really close to the limit. Saturating the video memory doesn't cause OOMs, especially not in a DX11 application where the VRAM doesn't get shadowed into VAS like it does in DX9. The other night I was tuning BF4 settings while watching GPU-Z and when it went over the VRAM limit it just started doing a ton of stuttering and really slow/non-responsive FPS. The OOM error only comes from running out of process VAS.

 

Thanks for the reply. I'll have to dig further then. I've had FSX and P3D1 running perfectly for years, so it's a mystery as to why P3D2 crumbles... I'm gonna go for a ride in P3D1.4 and see the VAS and VRAM usage I get there. The only thing I've changed on my computer setup is enabeling Aero, but that seems to work OK for others, so I'm back to 2006 - trying to fine tune FSX for an underpowered computer

 

 

 

You 580 is not the problem, my friend. You're guessing. It responds well to bufferpool management, and never once did I get an OOM while using DX10 (which is the early version (sic) of DX11) and running at 5 gig. The secret to FSX is understanding the architecture, and managing the whole PC - not just tweaking FSX - and that includes stopping the search engine (#4 in the list of running processes) It's no good crying over OOM's, and blaming Microsoft when all you need to do is read what is written in the forums day after day. Manage your expectations: Learn as much as you possibly can about the PC, about the differences between DX9 and DX10; why use a 580 instead of a 560Ti - or even a 560: what is it that makes the 480, 580 and the 680, such good cards. Study, study, study.

 

It's not by accident that some folks don't have OOM's, CTD, BlueScreens, hesitations.

 

Yep, I still have things to learn after using PCs for 25 years. I think I'm above average in both FSX and PC knowledge, but there are limits to how much I'm gonna bother studying. I use flight sims to fly, and don't have much interest in all that tweaking stuff. My PC runs fine, and as I said, no OOMs with FSX or P3D1.4 with lots of heavy addons. 

 

My PC is not a dedicated flight sim machine, so I need some of those other processes running for other programs to keep my photo database search times down. And since FSX and P3D1.4 runs fine I'm sticking to my old guns for now with no need to disable windows processes, firewalls and malware programs.  But at least I can exclude my GTX580 from the list of suspects

 

Still, I'm gonna play around in P3D2 and enjoy that HDR lighting for as long as itlets me

WarpD I agree with you on the 4096px, but we agree that a 4GB is easily consumed by a level of scenery complexity that is beyond the scope of the ESP architecture when it was programmed (for the systems demands of back then...) Modern simulation / world engines use a completely different architecture...

 

Hi Michel,

 

You're much too focused on the whole 32-bit issue. What is most beneficial about Prepar3d v2 and the introduction of DX11, is that full usage of available VRAM can now be made. In layman's terms this means that the OOM risk has decreased dramatically in that the memory on the GPU is now able to offload some of the memory previously used in system RAM.

 

Just tonight I flew around FSDT's CYVR and got super smooth frame rates and no hint of any OOMs with autogen and LOD maxed. A video of my flight in Full HD is available here:

 

http://tinyurl.com/nalbbua

 

In terms of fluidity and performance Prepar3D v2 is a massive improvement over FSX and Prepar3D v1.4.

 

Cheers,

 

Jerome

You are using OSM in those shots, so that doesn't really contradict his assertion. 

 

The purpose was to counteract the impression that scenery capabilities are limited and that it's "a bunch of crap" :smile:

 

OSM is nice if the area is covered well

 

Europe, where I mostly fly, is covered very, very well. USA is covered somewhat less than Europe, but still very well. Moreover, worldwide coverage is increasing steady and fast.

 

you have the HD space for it's large file sizes

 

Currently, using worldwide OSM (OSM combined with autogen is default scenery, actually) takes in total about 80 GB. It's gonna increase a little with the next update and the latest OSM data. Certainly a lot of space, but not much of a problem with 2TB HD's being the norm nowadays.

 

are willing to take the time to do it

 

OSM (combined with autogen) is default scenery. Next update will contain the latest updated OSM data, so what you see in the screenshots, basically will be default at the next update.

 

and you are ok with very limited coverage. 

 

As said, Europe is very well covered, USA and most developed countries have a good coverage. Certainly "very limited coverage" does not apply. Most importantly, the coverage is steadily increasing at a fast rate:

 

http://wiki.openstreetmap.org/wiki/Stats#Node.2C_way_and_relation_creation

Plus, in X-Plane 10 using FREE photo scenery gives an even better outcome...

 

I am using free European OSM + Autogen (as mentioned by Murmur) + photoscenery, and soon the photoscenery will get it's mesh updated to V2.

 

Please don't try to compare X-Plane 10 to P3Dv2.  As mentioned at another post on this forum, I just got P3Dv2, contrarily to what I was willing to do, and I am very satisfied with my first tests.

But, at the same time I have FSX + DX10 fixer too, and use it to run the PMDGs and the Aerosoft AXE.  X-Plane 10 for the best GA experience and also glider flying.

 

It's, at least for me, a win-win-win! Not to mention ELITE v8.6, and so I should probably write win-win-win-win... Only my credit card loses :-/

 

BTW: see here an excellent example of the combination, in X-Plane 10, of mesh v2, photoscenery and OSM+ autogen ( all FOR FREE!!!)

 

http://forum.avsim.net/topic/426768-x-plane-10-hd-mesh-scenery-v2-released/page-4#entry2863474

 

If this is crap, please tell me where your trashcan is... I'll probably find there a lot of good stuff and recycle it :-)

Absolutely not true.... about X-Plane 10... I'm sorry to have to say...

Agree, if xplane 10 had the same amount of addon support as fsx did ,it would have taken over fsx months ago. come on guys , since the inception of fsx we are still buying a 32 bit platform worth $199 with still ongoing oom,s issues and it's only been out a few days now , and as  far as I can see p3dv2 is just another version of fsx with some added cockpit candy ,sorry but I will stick with fsx for now. Xplane 10 will shine and be the primary ENTERTAINMENT 64 BIT platform when big companies like PMDG rolls out their brand new aircraft onto the scene and other reputable companies will follow suite. Xplane is the way of the future.

Can you please take your rants to the X-Plane forum and let us who like P3D try to work out the VAS issues before this thread goes completely off topic.

Hi Michel,

 

You're much too focused on the whole 32-bit issue. What is most beneficial about Prepar3d v2 and the introduction of DX11, is that full usage of available VRAM can now be made. In layman's terms this means that the OOM risk has decreased dramatically in that the memory on the GPU is now able to offload some of the memory previously used in system RAM.

 

Just tonight I flew around FSDT's CYVR and got super smooth frame rates and no hint of any OOMs with autogen and LOD maxed. A video of my flight in Full HD is available here:

 

http://tinyurl.com/nalbbua

 

In terms of fluidity and performance Prepar3D v2 is a massive improvement over FSX and Prepar3D v1.4.

 

Cheers,

 

Jerome

Nice video, could you share us your system specs? and also the addons used, this will give us a better idea of the capabilities

Nice video, could you share us your system specs? and also the addons used, this will give us a better idea of the capabilities

Thanks. I have an i7-3930K and GTX Titan. The add-ons used were FS Dreamteam's CYVR and a beta version of the soon to be released Milviz Bell 407.

 

You can see my Prepar3D v2 settings in some of my settings screenshots here:

 

http://tinyurl.com/oormqpw

 

and

 

http://tinyurl.com/pn7hybw

 

As I wrote before, the performance is fantastic, even with high settings.

 

Cheers,

 

Jerome