NEWSFLASH, NEWSFLASH. Last night, I had a revelation! P3D v3.0 is going to be released!   Yes, Gods son, the name was deleted (it´s a common namen here in Spain so it´s not blasphemy) told me so. 

 

Jack

the Swede in Spain

I just read in the late works of Madame Strang, soothsayer and psychic, that P3D is being cancelled as several developer are pulling out of the sim as it contrasts with their fundamental beliefs that you really should be able to blow the s..tuffing out of aircraft, buildings and make holes in the ground. :wink:

 

Of course, I say 'late' works as poor old Madame Strang is no longer with us (or is she..?   ) after being run over by a bus. Apparently she never saw it coming.

Too many 'experts' in here claiming you can only get an oom when you run out of VAS have clearly never flown xplane with 8GB of ram and lots of high quality mesh and scenery. In fact using hd mesh and extended distance detailed scenery it is recommended to have 16GB minimum to avoid this.

 

Would still be nice to get some actual v3 prepar3d news though!

 

Chris

Well I would love somebody to correct me if my information is wrong :-)

 

As I know virtual memory comes to compensate when there isn't enough physical one.... Hence adding physical memory will give you more headroom (Note Im still talking about a 64BIT platform).

 

If Im wrong please correct me...

 

You are kind of correct but kind of not. A 32-bit application like Prepar3d can only address or 'write/read' to 4GB of VAS space, not RAM. RAM can be thought of as an empty space that needs to be filled, VAS is a kind of empty reservation of space within your RAM... So we'll just call it 4GB of reserved space somewhere in your RAM and this is known as Virtual Address Space (VAS). As you play Prepar3d, your VAS reservation naturally fills up as stuff is loaded and unloaded but the hard limit is that it can never exceed the reserved 4GB of space whilst the application remains 32bit.

 

A fully loaded Prepar3d will use 4GB maximum of VAS before it runs out of space and you will see an OOM error. If you have less than 4GB of RAM for Prepar3d than it will either use your hard drive or you will OOM through memory exhaustion as there is no space left anyway. OOM by memory exhaustion is very different to simply exceeding the 4GB VAS limit, in fact as you go beyond 8GB, your RAM size becomes pretty irrelevant.

 

 

If Prepar3d was made into a 64bit application, RAM does now become important because as explained before, once your RAM or available memory elsewhere is exhausted the application will be exhausted of memory That is the only concern over RAM we can have beyond the speed really - it is also very doubtful any simulator running Prepar3d will ever need more than 16GB total RAM even if it went 64bit.

You are kind of correct but kind of not. A 32-bit application like Prepar3d can only address or 'write/read' to 4GB of VAS space, not RAM. RAM can be thought of as an empty space that needs to be filled, VAS is a kind of empty reservation of space within your RAM... So we'll just call it 4GB of reserved space somewhere in your RAM and this is known as Virtual Address Space (VAS). As you play Prepar3d, your VAS reservation naturally fills up as stuff is loaded and unloaded but the hard limit is that it can never exceed the reserved 4GB of space whilst the application remains 32bit.

 

A fully loaded Prepar3d will use 4GB maximum of VAS before it runs out of space and you will see an OOM error. If you have less than 4GB of RAM for Prepar3d than it will either use your hard drive or you will OOM through memory exhaustion as there is no space left anyway. OOM by memory exhaustion is very different to simply exceeding the 4GB VAS limit, in fact as you go beyond 8GB, your RAM size becomes pretty irrelevant.

 

 

If Prepar3d was made into a 64bit application, RAM does now become important because as explained before, once your RAM or available memory elsewhere is exhausted the application will be exhausted of memory That is the only concern over RAM we can have beyond the speed really - it is also very doubtful any simulator running Prepar3d will ever need more than 16GB total RAM even if it went 64bit.

 

 

Thanks for the detailed explanation.

 

Xplane with UHD meshes , world2xp sceneries and espicially with V10.40 which has an extended terrain loader , needs lots of memory , speaking as some one who owns it.

And in this case , as Xplane doesn't have this 32BIT VAS limitation , if memory is exhausted adding more RAM is the answer.

 

I never talked about P3D and it's VAS limitation , just about Xplane 64BIT quoting a guy that said he had an OOM their.

 

 

Anyway... back on track , it's a P3D 3.0 thread :-)

Why do you keep talking about OOMs  in Xplane in the P3D 3.0 news - it's pointless?

I had some serious OOM yesterday and as im about to stuff my chubby face with a massive slice of banoffee pie more OOM will follow OOOMMMM (silliness over) 

 

Getting back to honest basics here, Myself and Louisdecoolste were chatting about P3d and we came to the same conclusion,  V3 will be release on the 10/10/15.

 

We should have a mini competition to see who can pick the rightish date for V3 release.  Would anybody like to throw a date down.   

Moderater PLEASE!!!!!!!!!!!!!! Close this stupid thread!!!

 

 

Jack

Even 64bit applications use VAS not physical memory. I don't know where it's coming from that they don't... but they do. The amount of VAS is much larger (it varies based on OS and other factors), but can be considered to be at least 8TB in size. Since none of us can physically install 8TB of physical memory (I've never seen a motherboard that large, you??)... I'm pretty certain accessing that full 8TB is going to require the use of VAS.

 

And just to be seriously crystal clear: No application controls physical memory. They all operate in a virtual address space. For 32bit applications that virtual address is limited to 3GB. For 64bit applications, it is limited to 8TB or more (see above about OS).

 

Oh, and Mr. Jackson... if the thread bothers you, stop reading it.

Moderater PLEASE!!!!!!!!!!!!!! Close this stupid thread!!!

 

 

Jack

 

I always wondered why threads get closed in DISCUSSION forums...

 

 

For 32bit applications that virtual address is limited to 3GB.

 

You mean 4GB.

Oh, and Mr. Jackson... if the thread bothers you, stop reading it.

 

 

+1

I meant 3GB... 4GB requires the large address aware flag and not all 32-bit applications were compiled. Yes, I know there's a way to hack the application to make it 4GB aware...

Moderater PLEASE!!!!!!!!!!!!!! Close this stupid thread!!!

 

Unbridled speculation, a touch of stupidity, overly serious members, great contributors, awesome news, bad news.  It's what makes Avsim great.  Why close this thread.  It may be off track but there is some great info in it too.  Some discussions just never die because new people join the flightsim family all the time.

I meant 3GB... 4GB requires the large address aware flag and not all 32-bit applications were compiled. Yes, I know there's a way to hack the application to make it 4GB aware...

P3D uses the large address flag and FSX SP2 also uses it . There's no additional hack needed. So, for example,  P3D has a 3GB limit on a 32-bit operating system and a 4GB limit on 64-bit operatiing system.

 

See Microsoft's link https://msdn.microsoft.com/en-gb/library/windows/desktop/aa366778%28v=vs.85%29.aspx under the heading Memory and Address space Limits. 

The thread title could be changed to "P3D 3.0 non-News plus other stuff". 

 

Since this is a speculation thread, I am speculating that the P3D 3.0 release date will be based on when LM's major clients have the budget to purchase new licenses.  That would be sometime during or slightly before the new fiscal year (Oct 2015 for the US federal government and Jan 2016 for other clients), since the clients would need to include the purchase into their upcoming budget.  Also, based on the V1 and V2 release dates (01 Nov 2010 and 15 Nov 2013, respectively), I predict that the release date will be 16 November 2015.