https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/190615-21may22-pmdg-737-700-developers-update-pending-changes-in-the-cooker

My chosen highlights below... good that PMDG is driving fixes in MSFS that's coming in SU10:

- Flashing artifacts on the displays: ... We re-floated this to Asobo and the good news is that one very enterprising developer (Thank you, Eric!) reported back the following day that the source of the problem had been identified as a problem in the GDI+/NANO layer of the sim has been fixed internally at Asobo. The fix will roll out to customers concurrent with SU10. There really isn't much you can do to trigger it or prevent it- it seems to be something that either happens or doesn't... But- they found it.

- Pause in all forms seems not to play well with the 737: We have also elevated to Asobo something else from our September list of "stuff" we reported and that is "how the airplane behaves when the user exits to a menu or pauses." When in pause, the sim doesn't currently communicate to C++/WASM based projects that it is in pause. The airplane's core logic continues to think that the airplane is flying happily along, but it cannot understand why the position has stopped changing or why the airplane is not responding to control commands- so it keeps trying. This can lead to horrendously convoluted results when you unpause the thing. 
We have been asking for some time for the ability to detect that the sim is in pause- and we were informed early this week that it is being investigated. We thought we'd hear results by end of the week, but I suspect they simply forgot so I'll jangle the line early next week in hopes that this fix will also appear in SU10.

-Pop-Ups of Displays: We have mentioned a few times that the C++ methods required to make the displays in the 737 "pop up" have been locked out of availability, thus preventing us from having the displays pop up as we have done in all of our products going back to 2008. Mathijs and Hans, or good friends at Aerosoft, reached out to lets us know we may have missed a notation in an update cycle of the SDK a while back that provides a provision to make this possible. We don't know for certain if it works yet, as we haven't had a chance to implement their recommendations- but I expect we will get to testing it on Mon/Tue next week and will report results. We use a different display drawing method than Aerosoft, but based on what I know technically, I don't think this will be problematic.
BTW: You frequently hear me talk about how much back-chat goes on between developers and how one aspect of the developer community that I really enjoy is how much we all try to help one another un-stick problems in order to benefit the community. We have worked with Aerosoft since the year 2000 and Mathijs and Hans are both good friends to PMDG and to the dev community as a whole. It is always nice knowing another developer has your back and will ring you up to offer good advice if they see you knock your knee on something.

- A Ton of Other Items: We have a change list that already surpasses 70 items that have been changed for the upcoming update. These include a range of things from code corrections, documentation corrections, model fixes, texture improvements, clickspot tweaks and more.

- The 737-600 and 737-800: Both are moving through development on schedule.. . We expect to have review images of the 600 shortly!

 

Edited May 21, 20224 yr by lwt1971

Just wondering here. If FBW and Fenix can have pop-up windows in their aircraft, why cannot PMDG? 

My one big gripe with this aircraft, which I’m otherwise enjoying, is the inability to calibrate the throttle axis to include reverse thrust.  

This would be my only MSFS airliner that lacks that ability.

4 minutes ago, hvw said:

Just wondering here. If FBW and Fenix can have pop-up windows in their aircraft, why cannot PMDG? 

Due to a different code path PMDG had to take with the MSFS SDK ... i.e. they have a huge existing codebase in C++ so they had to go the WASM route with the SDK.  They are also doing this to keep the aircraft completely "internal" to MSFS so it can also be made available on the marketplace. Whereas Fenix's A320 is PC-only and they do systems external to the sim in a program (.exe) running outside the sim, so are not contrained by some limitations that currently existing in the MSFS C++/WASM codepath such as pop-outs, internet connection i.e. for simbrief, etc (mind you MSFS have said they'll fix these in coming SU and SDK updates)

Edited May 21, 20224 yr by lwt1971

10 minutes ago, hvw said:

Just wondering here. If FBW and Fenix can have pop-up windows in their aircraft, why cannot PMDG? 

Fenix was made from the ground up for MSFS.  PMDG are using an existing C++ codebase originally created for other sims, which means they have to do things differently unless they want to rewrite it.

We have fix'ed a display bug that very little see.

We have fix'ed tiny model/texture bug very little see

Pop up that will kill FPS coming

Best to use hard pause its the Esc key in msfs anyway.

A wall of text for very little.............................

Robert and his Hype....

Edited May 21, 20224 yr by Nyxx

All I can say is PMDG is starting to consistently bring smiles to their competitor's faces. 

17 minutes ago, Scottoest said:

Fenix was made from the ground up for MSFS.  PMDG are using an existing C++ codebase originally created for other sims, which means they have to do things differently unless they want to rewrite it.

Which they should have done 🙂 

Let's not be disengineous here folks :) Yes RSR is wordy but I'll wager that for all the 737 customers these updates are useful. Proper pause being implemented in SU10 is goodness not just for PMDG but for all aircrafts.

I realize that some have this weird hatred towards PMDG, and probably feel personally wronged due to whatever history... but the fact of the matter is, they put out high quality birds for MSFS that are widely and wildly popular, and the 737-700 is a dang fine product.  Not sure why this tribalism has to happen where one has to be partial to one dev or another, how about enjoying all of them, and if you don't care for one or the other then coming on threads to declare that is... well, thanks for letting us know :S

And PMDG I imagine is consistently bringing smiles to their own faces as they look at their sales figures.

Edited May 21, 20224 yr by lwt1971

I have encountered this pause problem. Acc to this post this problem will be possibly corrected by asobo at su 10. 

1 hour ago, regis9 said:

inability to calibrate the throttle axis to include reverse thrust.  

The B737 doesn't employee reverse thrust on its thrust levers like the Airbus. If you look closely you can see it's a separate assembly that sits on top of the thrust levers. Unless one has the complex hardware to emulate that kind of instrumentation, one can assign the reverse thrust hold function to a separate button and then use the thrust lever to control the thrust.

It's widely discussed both here and in the PMDG forums. Works like a charm.

Sure but given most people don’t have 737 specific hardware, and my throttle (Virtualfly TQ6) doesn’t have any buttons on it to make the thrust reverse button option easily doable (I don’t want to be looking for a keyboard button while I’m trying to steering the plane down the runway), it really should be an option PMDG provides for usability.  Again, they’re really the outlier for payware (and the freeware FBW Airbus).  I used FSUIPC in P3D to do this myself but it doesn’t appear that setting throttle axes in FSUIPC works with this aircraft in MSFS.

I hope this isn’t one of those things they’re going to be unnecessarily stubborn about because they don’t think it’s needed, or accurate in a way that doesn’t matter for a home based sim.

Edited May 21, 20224 yr by regis9

anyone else have a problem steering the nose wheel it won't seem to turn

1 hour ago, ashepherd316 said:

anyone else have a problem steering the nose wheel it won't seem to turn

make sure aircraft has electric power and hydraulics

2 hours ago, lwt1971 said:

Let's not be disingenuous here folks

 but the fact of the matter is, they put out high quality birds for MSFS that are widely and wildly popular,

and the 737-700 is a dang fine product. 

Wow, that is a pretty bold statement.

 

Unfortunately, those high-quality birds for MSFS have so many bugs ported from FSX era to P3D and you can see them right on their forum.

Unfortunately, DC6 and the 737-700 suffer from many bugs, far from being "a dang fine product".

 

If you are referring to eye candy visuals I'm with you.

 

Especially the 737 with so many issues I would categorize an early beta version compared to other developers that also ported over their products in much better shape.

Throughout their release history, they always rushed releasing products with so many issues and jumped to others with minimal or no fix.

Absolutely there are people that enjoy the product as it is, but, for a hardcore PC sim pilot with good knowledge about the airplane or a real pilot when you see the problems it's not sitting too well with the purchase and the expectations based on past reputation.

This might bring smiles to their faces but many customers are not happy at all, quite disappointed about the state of this release, again, see their forum and you will see that people are not quite disingenuous