Lockheed to Answer Questions of AVSIM Members

 

In the lead up to next week’s release of their flight simulator P3D V2.0, Lockheed has agreed to answer questions from AVSIM members. Here is your opportunity to ask those questions most important to you about the soon to be released next generation of the Prepar3D simulator.

 

AVSIM has opened a topic in the P3D General Forum for users to list their questions of the Lockheed team on this forthcoming release. You can find that topic here.

 

Please ask only one question PER MESSAGE, and without editorials included. Your question is going to be voted on, so if you don't make sense or use your opportunity as a platform for BS, it will be removed and your reputation will go down accordingly.

 

As readers, please use the message Up/Down Vote Button at the bottom right of every message to record your position on the question asked. Is it important enough to ask of Lockheed, or are there more important questions that with this one opportunity, need to be asked?

 

We will close this topic on THURSDAY evening at 2359 EDT (0459 UTC).

 

QUESTIONS REGARDING THE EULA OR LOCKHEED'S LICENSING WILL BE DELETED. Those questions have been beat to death and we are not going to waste this opportunity beating them further.

This post has been promoted to an article

Edited November 19, 201312 yr by Tom Allensworth
Change in closing time and date.

What new features will third party add-on developers be able to take advantage of in P3D v2?

How far do you think you can develop the underlying engine before it becomes time to have to think about rebuilding from scratch (and by this, I mean things like the currenty extremely difficult/laborious updates to default scenery nav data/frequencies etc)?

Is there a 64-bit 'conversion' or recompilation projected anytime in the future?

First of all:

Thank you to Lockheed Martin for the opportunity to ask direct questions.

 

 

Will tessellation within P3D support displacement mapping in which a a third party developer could create terrain that is less smooth and mountains that appear jagged instead of rounded similar to how terrain and mountain rendering appears in Outerra?

Have any additional weather effects been added, namelly regarding turbulence and wind variation? What about interaction of wind with relief and thermals - are they the same as in FSX?

 

And still on this subject, is there any form of fetching Real World Weather implemented into V2?

Great news, and thanks for taking the time to chat with us.

 

Will P3D V2 support sound streaming (Direct Sound buffers keep playing sound ie: bufferDescription.GlobalFocus = true;) when the focus is changed to another application?

What modifications did the World mesh and landclass get for V2? And regarding Maps and Navaids, has any update to the World navigation and airport databases been included?

Will legacy, fs9 Port addons, such as the Leonardo maddog be supported? 

 

 

Just found out.

Do you plan on supporting Oculus Rift in V2.0?

Will V2 be  compatible  with PhotoScenery and if so, should we see any improvements in this area?

Thanks

Phil Murfin - Matlock UK

Does P3DV2 have superior memory management to FSX? The latter seems to struggle to remove scenery from memory that is no longer required, and I would like to know if this significant cause of OOMs has been resolved.

First of all, thank you for taking on P3D, for revamping it into v2, and for entertaining our questions on this forum.

 

My question - will P3D v2 provide native support for multiple control devices, with different profiles and calibrations assigned to different aircraft (e.g. a yoke for a C172 and a cyclic/collective for a helo, connected simultaneously)?  Or will it still be necessary to use a third-party utility such as FSUIPC to accomplish this?

What do Lockheed Martin propose are the key benefits to an FSX user, in upgrading or moving to the P3D 2.0 platform?

 

(As most of the current questions are closed questions, I thought an open question may be interesting).

 

Thanks. 

Has the mouse cursor bug been addressed?
(The one that causes a drop/loss in FPS when the mouse cursor is visible on screen.)