P3D not having 64bit may not turn out to be a big issue afterall for P3D. They developed an interface called ISimconnect. With it aircraft developers, can build their flight models and systems external to the sim using this interface to connect directly to the core of the sim. Since these would be external apps running in their own  4GB VAS similar to the way GSX, or ASE does today, there would be minimal impact if any of VAS on the core sim app. Thereby greatly reducing the chance f running out of VAS, since much of it comes from the system detail of these complex aircraft models, which could now be offloaded into their own VAS space.   

I kinda doubt this is how it actually works. Things will still need to be grouped under the P3D "process" and will share the same VAS limit the sim itself does. We do a ton of things outside of the normal FSX bounds already but they still need to be linked to the sim's process to function.

For me, flight simulators are entertainment packages. If a majority of users were really honest with themselves, I'd wager its the same for them as well.

 

Well, I can only really speak for myself ... but let me tell you duderino, that flight-simulation is my way of inflicting excruciating pain upon my self .. and I'm not a masochist.

For me it is a type of spiritual penance .. something to be endured to burn away the sins of my past .. a form of self flagellation for being a bad, bad man in a previous life.

I dread starting up the PC and break into a sweat whenever I hear the whirr of a CPU fan. I have endured this torture for many, many years and can barely bear the notion that I have still many years to go, the fates willing.

The pain escalates in direct proportion to the fidelity of the modelling and the detail in the 3D graphics. :blink: Well designed turboprops kill me for at least a week.

 

Not entertainment .. spiritual penance .. doesn't nearly everyone else treat flight simming this way? Or have I been operating under a delusion?

I kinda doubt this is how it actually works. Things will still need to be grouped under the P3D "process" and will share the same VAS limit the sim itself does. We do a ton of things outside of the normal FSX bounds already but they still need to be linked to the sim's process to function.

Thanks Ryan, I'm sure you're right, as you would have more inside knowledge. I was just going by what I read in a couple of the recent interviews  with  Wes Bard of P3D. It sounded like he was referring to external apps. That said, if it's not external, I think there may be a VAS issue when addons are added to the mix. People are reporting pretty high VAS usage, with default aircraft/scenery One reported 2.4GB at KSFO with the default King Air in Process Exporer, That's with DX11 which shouldn't be shadow copying VRAM. I use 1.4GB with the same situation and aircraft in FSX. with max scenery settings. Add complex scenery like OrBx, and detailed complex system aircraft, and we may start seeing OOM's return. In fact one user reported a OOM today on the forums with P3D V2.

Gents, I've removed a number of posts touching on the P3D EULA/Licensing issue.  We're not going there...here or in any other AVSIM forum.  L-M has publicly published the licensing criteria, and if you need a clarification you can ask them on their forum.  Any more rehashing of that topic is verboten here.

 

http://forum.avsim.net/topic/422890-lockheed-eula-discussions/

 

Regards