2 hours ago, awf said:

Or as real as it gets take a real ipad as they do, far more convenient and with a whole lot more stuff 🙂

Yeah, when I'm flying in 2D, i'll use my company iPad for plates..but in VR it's not so easy lol. Plus, a lot of sim pilots don't have access to Jepp FD Pro on their ipad.

18 hours ago, V1ROTA7E said:

BUT, it is still using the "old school" way of forcing integration. Dropping your route into a hard to find folder

Surely it is only 'hard to find' once?

3 hours ago, V1ROTA7E said:

Yeah, when I'm flying in 2D, i'll use my company iPad for plates..but in VR it's not so easy lol. Plus, a lot of sim pilots don't have access to Jepp FD Pro on their ipad.

I agree VR is a different story

Interesting discussion in the PMDG forum re: popout displays and C++/WASM limitations and RSR's posts below:
 

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/181788-no-pop-out-screens-737-700-doa-for-a-lot-of-simmers?p=182137#post182137
Asobo still has some limitations they are saddling C++/WASM projects with- and this has required us to do a massive amount of technical work the create a GDI+/Nano integration layer in order to drive displays in the 737. We have been asking them to provide additional capability in the graphic drawing and windows communication layer, and we are assured it is coming, but no timelines are offered

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/181788-no-pop-out-screens-737-700-doa-for-a-lot-of-simmers?p=182152#post182152
Yeah. What is frustrating for us is that we don't like to say "oh this is Asobos's fault" because then it just looks like we are making excuses. We have spent YEARS trying to leverage the relationship with Asobo to get attention to areas we feel are significant- and we have gotten a ton of attention to a wide swath of areas that none of you will ever know about because they got addressed.
But then there are still a few like this one... And we worked for a long time to code around some, but couldn't get around others...
We'll get them there. It may require some coordinated community leverage once we figure out the ones that have the greatest impact to the greatest number of users.
These are early days- imagine where we will be in a year!

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/181788-no-pop-out-screens-737-700-doa-for-a-lot-of-simmers?p=183287#post183287
Our hope is that by having the product on the market- the demand for such capability will become more evident to Asobo and that will naturally increase the priority given to expanding some of the limitations they placed on C++/WASM project developers.


Nothing like aircraft written from the ground up to follow MSFS dev best practices and use natively supported languages/frameworks I guess... or go the Fenix route where some parts of the aircraft code run completely externally of the sim.

Edited May 11, 20224 yr by lwt1971

I'd say we should maybe first get rid of some bugs. I hear that some people need 2 Flight Directors on for them to be able to activate CMD or CWS. If that is true, that should be fixed, as the real plane has no need for any FD to be on for CMD or CWS (A or B) to activate afaik.The FCOM says no and the P3D version accordingly does not, tested it after hearing of that.
The PMDG 737 used to be the 737 with the highest fidelity in all systems that I ever tested - I just hope such things are not creeping up in general, bc if they do, I'll stay with the P3D version; to me systems that behave as exactly as possible as in the real plane are way more important than visual and accoustical fidelity.