Its been my observation those googing about performance are running Titan cards?

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

 

 

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.

 

 

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.

 

 

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.

 

 

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

 

Let's just say you are painting a much too rosy picture of how OSM works in Xplane. For starters, default XP does not use OSM for building or autogen placement. The system simply isn't designed that way yet. OSM is used for vector data in default XP to place roads, rivers, etc. (again, I'm talking default, out of the box).

 

Secondly, coverage stinks in the US outside of major metropolitan areas. My hometown of 60,000 people has only two buildings marked. This is true for thousands of other cities, including many European cities. Decent coverage in Asia and Africa? Forget about it.

 

Thirdly, when you start combining the photo scenery everyone places under OSM to make it look right, it's way, way more then 80GB. 

 

I'm glad you enjoy it though. Everyone has different tastes and requirements. But it's misleading to post pictures and pretend like the whole world looks like that in XP out of the box. It's akin to an FSX user posting an Orbx region and not mentioning it.

 

Its been my observation those googing about performance are running Titan cards?

 

 

Titan, 780, 680 4GB. 

 

The top of the line cards seem to be the ticket. 

 

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

 

Wow, sorry did not know you were the author of this, pleanty of info in this story. Thanks very much

So what's a "good" amount of VAS usage? With OPUS,REX and a good addon. 2.5-3 should be good no?

 

Sent from my Nexus 4 using Tapatalk

 

 

Let's just say you are painting a much too rosy picture of how OSM works in Xplane. For starters, default XP does not use OSM for building or autogen placement. The system simply isn't designed that way yet. OSM is used for vector data in default XP to place roads, rivers, etc. (again, I'm talking default, out of the box).

 

As said, my post was mainly to counteract the claims about the capabilities of X-P scenery and the impression that it's "a bunch of crap".

 

Secondly, coverage stinks in the US outside of major metropolitan areas. My hometown of 60,000 people has only two buildings marked. This is true for thousands of other cities, including many European cities. Decent coverage in Asia and Africa? Forget about it.

 

Even in those places where there are no buildings, OSM roads are used and then there is the default autogen based on data such as population density etc. Not saying that it will be good everywhere though. However the new HD mesh v2 (+latest OSM) covers the whole North America and Europe, where a lot of flight simmers spent most of their time. As said, the good thing about OSM is its coverage is increasing at a steady pace.

 

Thirdly, when you start combining the photo scenery everyone places under OSM to make it look right, it's way, way more then 80GB.

 

Photo scenery was not used in any of my pics. You can see OSM looks very good without it.

 

But it's misleading to post pictures and pretend like the whole world looks like that in XP out of the box.

 

You're right, that's a necessary clarification. However just using a freeware add-on, most of Europe and North America (where although, as you said, the OSM coverage is still less for now) can look more or less like that.

 

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.

 

I absolutely agree with you simmerhead! However, if an user mentions another product not belonging to this forum, I feel it's legit for me to reply to him about that product. :smile:

I'm afraid that I have to agree with "Murmur" in this instance. On the other hand, let's please steer the discussion back to the actual topic of the thread before I have to do more than simply follow the conversation... :lol:

I finally got my first OOM!! I had to try HARD though..

 

Orbx PNW / REX 4096 DXT5 Clouds / Carenado Stationair / High detail radius / Max auto-gen / 10% road  traffic and made a bee-line towards Mt Olympus from KHQM

 

 

 

I finally got my first OOM!! I had to try HARD though..

 

Ha and you just begged for that one. 4096 textures and everything max. 

 

I think what LM was trying to accomplish in the interim of 64 bit plans, was to get the memory released properly and in a timely manner. Flying from New York to Seattle should not be compounding up. It may seem so when you get to Seattle, but Seattle is also quite intensive area given all the mountains and shorelines not to mention city and traffic data. 

My understanding was that DX11 uses near the full amount of VRAM you have in conjuction with the VAS limit. Unlike DX9 which couldnt, and DX10 which was only able to use a little bit of it. 

 

Its not a solution like 64bit, but it hopefully buys us some time to do it this way. The other saving grace may be in all these "hooks"  that LM has provided so that heavy aircraft or sceneries could be loaded externally outside the p3d VAS. Im no programmer, its just my understanding of how it works. But then again ive been wrong many times before. lol 

 

On a side note, Please dont make this p3d/fsx vs xpx thread. There is plenty of those, and they get unnecessarily ugly. 

...The only known Memory leak we shipped with was sounds leaking if no speakers or headphones are plugged in but as a 32 bit app we can only use 3.5 GB of memory so it can be an issue at high settings. (Especially if you have any large add-ones). Out of memory error handling improvements will be part of the 2.1 release.

Beau Hollis

Rendering System Lead - Prepar3D® Team

 

link

Not sure if this program works on the scenery library in P3D, but one way to help alleviate the load on FSX and lessen the probability of an OOM in FSX is to use a program called "SceneryConfigEditor" to easily disable addon scenery you do not fly over.  You can even create custom "playlists" of scenery.cfg files, say, Europe only, Asia only, or you can always go into the tool before your flight and only enable the two airports you are flying between.   You are going to put much less strain on VAS usage if you are careful about the scenery you load into the sim.