Randazzo quote from PMDG forum

 

Captains,

We have just made two videos available for you via our official PMDG Simulations youtube channel. The first is short, light hearted and to the point. The second goes into some depth and represents the first of a series of very in-depth deep-dives we are taking into the options available to you as an owner of the PMDG 737 for Microsoft Flight Simulator.
 

You can view the first video here:

https://www.youtube.com/watch?v=p90Sg7rY0WY

And the second, longer video is here:

 

https://www.youtube.com/watch?v=DFzHjHNjXhU

Since my last update, we have narrowed the list of blockers preventing release of the 737 from four down to two. One of those blockers is this obscenity that appears now and then when landing Flaps 40. On that topic, the good news is that we managed to capture it on one of our development rigs and we were able to pull a significant amount of data from the event which we fed to Asobo to see their input.

The investigation is ongoing, and I am not going to give any information on what we saw, what we think, or what the fix might entail- as at this juncture we simply don't know enough about what we have found to really say with clarity "it is caused by X."

What we do know is that it happens in one specific mode of operation, but we don't yet know why or how to prevent it.

There is a phrase I like to offer to the development team at PMDG in difficult moments: "Don't worry. We'll solve it. We always do."

We will be hard at work on it this weekend- as will our ever hardy beta team. They are frothing at the bit to help us identify and cure this issue because they want you to see this just as much as we do.

The good news is that we have every system at PMDG poised for the release. The moment are certain that we have a fix in hand, we will be in a position to make the airplane available for your use. My hope is to have you off on 737 adventures in time for next weekend- but this will depend entirely upon the results of our own efforts in the next few days.

Stay tuned. We shall keep you posted.

If you are bored in the mean-time, please do go visit our friends at Leonardo. They have created a truly wonderful MD-82 and they deserve your attention as much as any developer in the community.

 

Quote

 On that topic, the good news is that we managed to capture it on one of our development rigs and we were able to pull a significant amount of data from the event which we fed to Asobo to see their input. ... ... My hope is to have you off on 737 adventures in time for next weekend-

Even if Asobo takes a little longer to get back to PMDG on a fix, I can't see the PMDG 737 releasing in June, and it's much more likely that it will release it in May.  Unless another show stopper comes up to prevent PMDG from releasing the 737, or the fix for the flaps 40 bug takes longer than they anticipate, get ready for a May release of the PMDG 737.  This bad boy is coming to us within the next few weeks!

PS. Not sure why the OP didn't add the link to Randazzo's post, but here is the link.

Edited April 30, 20224 yr by abrams_tank

Has Adobo ever done quick fixes like this? We may be stuck until whenever the next sim update is- worst case scenario. I think that's July?

 

Anyways, crazy how everything is releasing the same week. Fully expect the Fenix A320 and FBW A380 to somehow drop tomorrow now. 

4 minutes ago, nikolajz1 said:

Has Adobo ever done quick fixes like this? We may be stuck until whenever the next sim update is- worst case scenario. I think that's July?

I think the more likely scenario is, there is something about the SDK that PMDG doesn't fully understand regarding this flaps 40 bug. So Asobo will probably tell them how to overcome the flaps 40 problem and PMDG shouldn't have to wait for the next Sim Update.  There is a small chance that the fix to the problem will require waiting for Sim Update 10, but I highly doubt it.  Either Asobo will tell PMDG how to fix the problem, or PMDG will find a workaround for the problem, these are the most likely scenarios, IMO.

Edited April 30, 20224 yr by abrams_tank

Oh no please not, that leaves me only a week to fully enjoy the Maddog! 😉

3 minutes ago, abrams_tank said:

I think the more likely scenario is, there is something about the SDK that PMDG doesn't fully understand regarding this flaps 40 bug. So Asobo will probably tell them how to overcome the flaps 40 problem and PMDG shouldn't have to wait for the next Sim Update.  There is a small chance that the fix to the problem will require waiting for Sim Update 10, but I highly doubt it.  Either Asobo will tell PMDG how to fix the problem, or PMDG will find a workaround for the problem, these are the most likely scenarios, IMO.

Its a shame dedicated beta testing didn't find this. Instead, we all had to see it unwind ignominiously on Fabio's more casual stream. The PMDG team would have been gutted!  Anyway, lets hope it is as RSR says and we are in for another complex airframe treat next weekend!! I appreciated RSR's respectful nod to the Leonado team. Good sportsmanship! Can't wait for -700. 

 

Cheers

Terry  

I didn't read this as PMDG needing anything from Asobo.  Robert just said they forwarded some data along to Asobo for their input.  I don't see that equaling PMDG needing some kind of "fix" from Asobo... it's just troubleshooting.  You ask everyone what they think. 

2 minutes ago, Stearmandriver said:

I didn't read this as PMDG needing anything from Asobo.  Robert just said they forwarded some data along to Asobo for their input.  I don't see that equaling PMDG needing some kind of "fix" from Asobo... it's just troubleshooting.  You ask everyone what they think. 

Yeah, this is possible too, based on the way Randazzo wrote that line about sending data to Asobo for their input.  Randazzo not waiting for Asobo would be consistent with his optimism that the PMDG 737 could be released by next weekend, if everything goes right. 

26 minutes ago, nikolajz1 said:

Has Adobo ever done quick fixes like this?

They once worked over the weekend to help fix an issude the PMDG DC-6 had when it launched. Rob was very grateful.

20 minutes ago, Fiorentoni said:

Oh no please not, that leaves me only a week to fully enjoy the Maddog! 😉

I'll probably just be buying the Maddog now, and just the 738 later. I actually like the timing 🙂

1 minute ago, rka said:

I'll probably just be buying the Maddog now, and just the 738 later. I actually like the timing 🙂

I probably will be dumb and buy both immediately.

39 minutes ago, abrams_tank said:

I think the more likely scenario is, there is something about the SDK that PMDG doesn't fully understand regarding this flaps 40 bug. So Asobo will probably tell them how to overcome the flaps 40 problem and PMDG shouldn't have to wait for the next Sim Update.  There is a small chance that the fix to the problem will require waiting for Sim Update 10, but I highly doubt it.  Either Asobo will tell PMDG how to fix the problem, or PMDG will find a workaround for the problem, these are the most likely scenarios, IMO.

Hopefully it will still work well if Asobo releases a Hotfix for the current performance issues. So they don’t have to start fixing broken things…

And with every SU developers might face damage repair.

 

50 minutes ago, abrams_tank said:

I think the more likely scenario is, there is something about the SDK that PMDG doesn't fully understand regarding this flaps 40 bug. So Asobo will probably tell them how to overcome the flaps 40 problem and PMDG shouldn't have to wait for the next Sim Update.  There is a small chance that the fix to the problem will require waiting for Sim Update 10, but I highly doubt it.  Either Asobo will tell PMDG how to fix the problem, or PMDG will find a workaround for the problem, these are the most likely scenarios, IMO.

I'm curious: What makes you think that it's more probable the "fault" lies with a developer that has been developing the same airplanes for almost 15 years, instead of a developer that until 2020 has been doing adventures and casual games for Disney and Pixar movies (or sometimes both combined: "Disneyland Adventures" from 2017) ?

24 minutes ago, Fiorentoni said:

I'm curious: What makes you think that it's more probable the "fault" lies with a developer that has been developing the same airplanes for almost 15 years, instead of a developer that until 2020 has been doing adventures and casual games for Disney and Pixar movies (or sometimes both combined: "Disneyland Adventures" from 2017) ?

I'd imagine because previously PMDG misunderstood a fairly simple problem that other devs had figured out a lot earlier, and it seems without the need to ask Asobo the answer. So in my opinion it's reasonable to think that PMDG as a dev that is still learning the quirks of the sim could easily misunderstand other elements of the SDK while developing an even more complex study level aircraft than their earlier work like the DC6? 

32 minutes ago, Fiorentoni said:

I'm curious: What makes you think that it's more probable the "fault" lies with a developer that has been developing the same airplanes for almost 15 years, instead of a developer that until 2020 has been doing adventures and casual games for Disney and Pixar movies (or sometimes both combined: "Disneyland Adventures" from 2017) ?

I don't know why you have to assign "fault" to one party or another.  An SDK is an SDK.  When you want to make a plane for MSFS, you need to use the SDK given to you, to achieve what you want.

If I go and develop an app for IPhone, I will be using the SDK for developing IPhones.  If I go and develop an app for Android, I will be using the SDK for Android phones. 

How about it's neither party's fault?  Perhaps PMDG doesn't understand a certain aspect of the SDK, since if you were following the development of the PMDG 737, you would know that PMDG/Randazzo misunderstood something about the SDK a few months ago, which prevented the PMDG 737 from entering the beta. Asobo had to sit down with PMDG in a meeting and explain that aspect of the SDK to PMDG, and then PMDG was able to overcome the problem and enter the beta for their 737.  In that case, I didn't attribute the fault to either party because SDKs are inherently complex, not just for MSFS, but the SDK will be complex for IPhone and Android if you are new to those SDKs too.

I don't get why you have to see the "negative" in everything.  Why you are so adamant to assign "fault" to a party.  Just relax.  I don't think anybody is at fault here, the flap 40 problem will be overcome soon enough.

 

Edited April 30, 20224 yr by abrams_tank