May 24, 20224 yr 1 hour ago, lwt1971 said: Lol sure ok then... More rightfully, all your points are the reality of *your* situation. Seems like you'd be best served to not bother with PMDG's products at all and wait for some other dev to develop some Boeings? No matter how much time you waste time on these threads distilling all your talking points about PMDG it's not going move the needle an inch for all those of us who do see the actual "reality of the situation" 🙂 I guess it's all about how one wants to look at it. If we want to ignore facts, let it be. But when the difference is as it is and undeniable maybe is time to acknowledge that probably it might be an issue. My dissatisfaction (and others) is that before their products were very good and top-notch, lately, unfortunately, a constant rush to release something with a way too many issues compared to their past practices. This is a sad "reality of the situation" if one chooses to accept it and think that is OK. For sure it can be an excellent product, but, when cutting corners it shows and people will eventually start making decisions no matter what I say or others try to find all kinds of excuses. 747 Captain for the last 39 years, and still learning.
May 24, 20224 yr 12 minutes ago, Trovis said: Anyone who isn't a pilot can observe certain things on a real 737 through youtube and realize that it's very different. Can you give a few examples of this? (I'm asking out of my own, personal interest as a simmer and an aviation enthusiast, not because I don't believe you or because I'm trying to deny anything.)
May 24, 20224 yr Author Well I guess this thread served its purpose to pass on an update from PMDG, and now we're in the constant bloviation stage by some who seem rather invested in telling us how PMDG have failed and wronged them, and how RSR's personality irks them... and as amusing as that is, 'tis time to move on.Mods: if you're reading this, as the thread starter I'd like to request to close this one out if you're agreeable to it. Len 1980s: Sublogic FS II on C64 ---> 1990s: Flight Unlimited I/II, MSFS 95/98 ---> 2000s/2010s: FS/X, P3D, XP ---> 2020+: MSFS Current system: i9 13900K, RTX 4090, 64GB DDR5 4800 RAM, 4TB NVMe SSD
May 24, 20224 yr 6 minutes ago, lwt1971 said: Well I guess this thread served its purpose to pass on an update from PMDG, and now we're in the constant bloviation stage by some who seem rather invested in telling us how PMDG have failed and wronged them, and how RSR's personality irks them... and as amusing as that is, 'tis time to move on.Mods: if you're reading this, as the thread starter I'd like to request to close this one out if you're agreeable to it. Very interesting. So we cannot share opinions and have to close any thread when we are civilized and just express concerns? Is this PMDG forum or is AVSIM where we can disagree respectfully? 747 Captain for the last 39 years, and still learning.
May 24, 20224 yr 4 minutes ago, lwt1971 said: Well I guess this thread served its purpose to pass on an update from PMDG, and now we're in the constant bloviation stage by some who seem rather invested in telling us how PMDG have failed and wronged them, and how RSR's personality irks them... and as amusing as that is, 'tis time to move on.Mods: if you're reading this, as the thread starter I'd like to request to close this one out if you're agreeable to it. I reckon if the conversation is still going, let it run its course. PMDG's place in the world is obviously a topic of interest right now. I know you're a fan of the company, and some people here are less impressed than you by it, but I don't think that means this fireside chat needs to be censored. Oz Sim Rig: MSI RTX3090 Suprim, an old, partly-melted Intel 9900K @ 5GHz+, Honeycomb Alpha, Thrustmaster TPR Rudder, Warthog HOTAS, Reverb G2, Prosim 737 cockpit. Currently flying: MSFS: PMDG 737-700, Fenix A320, Leonardo MD-82, MIlviz C310, Flysimware C414AW, DC Concorde, Carenado C337. Prepar3d v5: PMDG 737/747/777. "There are three simple rules for making a smooth landing. Unfortunately, no one knows what they are."
May 24, 20224 yr 1 minute ago, LRBS said: Is this PMDG forum or is AVSIM where we can disagree respectfully? Disagreeing respectfully also involves letting people discuss their thoughts without constantly accusing them of finding excuses just because the opinion differs, by the way.
May 24, 20224 yr Author 25 minutes ago, OzWhitey said: PMDG's place in the world is obviously a topic of interest right now. I know you're a fan of the company, and some people here are less impressed than you by it, but I don't think that means this fireside chat needs to be censored. Well, if the thread remains open have at it in telling whoever cares to listen as to how not impressed by PMDG you are 🙂 ... I'm a realist and also understand what PMDG's development processes are, the paths they're then confined to due to that, the business + technical decisions they've made to come up with this 737 release strategy based on an existing codebase which they practically cannot afford to rewrite from the ground up, etc.. and thankfully I seem to be not too bothered by RSR's verbage or communication methods or other personality traits. If that makes me a "fan" then that's what I am. As for PMDG's place in the world, I suspect they'll continue to laugh all the way to the bank for the next few months as the sales of the 737 series continue to rack up, and then the 777 and 747. Edited May 24, 20224 yr by lwt1971 Len 1980s: Sublogic FS II on C64 ---> 1990s: Flight Unlimited I/II, MSFS 95/98 ---> 2000s/2010s: FS/X, P3D, XP ---> 2020+: MSFS Current system: i9 13900K, RTX 4090, 64GB DDR5 4800 RAM, 4TB NVMe SSD
May 24, 20224 yr 1 hour ago, threegreen said: Can you give a few examples of this? (I'm asking out of my own, personal interest as a simmer and an aviation enthusiast, not because I don't believe you or because I'm trying to deny anything.) Absolutely! For example, if you are on a turbulent approach, with speed variation, and you have the need for constant pitch, power and trim adjustments, the plane starts to "ride" (pitch up, pitch down, up, down...) with each attitude adjustment. It bothers me too much. Another example: even in a smooth approach, the response to the trim command is very slow, causing the need to use trim to increase considerably, which is very different from real life. This can also be seen in youtube videos. This slow response ends up completely unbalancing the plane's pitch/power ratio.
May 24, 20224 yr 41 minutes ago, Trovis said: Absolutely! For example, if you are on a turbulent approach, with speed variation, and you have the need for constant pitch, power and trim adjustments, the plane starts to "ride" (pitch up, pitch down, up, down...) with each attitude adjustment. It bothers me too much. Another example: even in a smooth approach, the response to the trim command is very slow, causing the need to use trim to increase considerably, which is very different from real life. This can also be seen in youtube videos. This slow response ends up completely unbalancing the plane's pitch/power ratio. Exactly, plus just other two quick ones. On a 30 degrees HDG to intercept an ILS @ 180 KTS as is in real life the airplane will not wonder as much as 0,5 nm left/right of course and hunt to intercept the LOC. In a PRM APP scenario with these type of deviations you will be qualified as an intruder by ATC and the other airplane will be instructed to go around. Low altitudes intercepts in VNAV during SIDS sometimes will bust as much as 200FT. There are so many to be listed, unfortunately. Hopefully they will fix them. 747 Captain for the last 39 years, and still learning.
May 28, 20224 yr On 5/21/2022 at 6:25 PM, somiller said: make sure aircraft has electric power and hydraulics i have i even put the panel state on take off and still can't move it Alexander Shepherd
July 31, 20223 yr On 5/21/2022 at 6:28 AM, lwt1971 said: 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! This thread is pretty old - so maybe no one checking. But if the Pause at TOD isn't working correctly in allowing the AC to resume after pause, it must be disabled until a fix is available. Was 5 hours into a flight at TOD pause, and I had to exit the flight and start over. Since this problem has been around for quite a while and has not been fixed PMDG has the responsibility to disable this feature.
August 1, 20223 yr No, they shouldn't disable it. Some of us use it all the time. I just don't let it stay paused for very long, so it works fine for me. i9-10850K, ASUS TUF GAMING Z490-PLUS (WI-FI), 32GB G.SKILL DDR4-3603 / PC4-28800, GIGABYTE RTX5080 16GB WF OC 3 FAN running 3440x1440
August 1, 20223 yr 16 hours ago, Fiddler said: This thread is pretty old - so maybe no one checking. But if the Pause at TOD isn't working correctly in allowing the AC to resume after pause, it must be disabled until a fix is available. Was 5 hours into a flight at TOD pause, and I had to exit the flight and start over. Since this problem has been around for quite a while and has not been fixed PMDG has the responsibility to disable this feature. Its actually been a user-defined option to disable since day-one: If The common temp work-around until Asobo fixes the dumbest pause behavior ever created in a sim (IMO), is if you know you're going to be away hours past when your flight hits TOD, pause it before you leave and open the settings and get to the load scenario screen where the Window's modal dialog box is open. This will actually pause the whole sim, fuel flow, weather and all....in the sim. When you return, your aircraft will be fine, full of fuel, and not aerodynamically imbalanced because Asobo thought it would be a great idea to pause the position of the plane, but leave every other parameter around it running in real time. Perhaps they never considered the true value of pause at TOD because they never really researched how long-haul simmers typically fly in the sim, they only envisioned x-boxer's taking the 747 or 787 and seeing if they could fly it inverted under the Golden Gate Bridge, not a simmer actually simulating a 14 hour flight in them? 🤔 Regards, Steve DraGet my paints for MSFS planes at flightsim.to here, and iFly 737s hereDownload my FSX, P3D paints at Avsim by clicking here
August 24, 20223 yr Thanks for the info Steve. Yeah I guess what I meant was that if the Pause at TOD function isn't going to work properly in the MSFS2020 environment why provide that function for people to trip over. So you said "open the settings and get to the load scenario screen where the Window's modal dialog box is open." I'm not sure what that means. Are you saying hit the Escape key to activate the Options windows, then hit the space bar to activate the Load/Save Function Menu and then just let it sit there?
Archived
This topic is now archived and is closed to further replies.