I hope Asobo takes this as the wake up call it should be.  Not a good look to have a recently announced partner saying that Asobo is preventing them from moving forward.  

5 hours ago, WestAir said:

 

Think the core feature is VNAV? It needs to know what the weather is to work and we don't have a weather API.

 

 

I doubt that VNAV is the problem. A real VNAV system only knows the wind speed and direction at the aircraft’s current position and altitude, and dynamically adjusts descent path as the wind changes.

Despite the lack of SDK weather functions for things like weather radar, wind speed and direction at the aircraft’s current position are available in MSFS using the standard simconnect variables that have been around since FSX. 

3 minutes ago, phmcr said:

it must have frustrated PMDG too

The level of frustration felt by all reputable and quality Devs must be as frustrating as this scenario would have been:

Person commissioning the painting of the Sistine Chapel ceiling: "Hey Michelangelo, can you paint our ceiling up there?"

Michelangelo: "Sure.....let me get my painting tools, supplies, etc."

Person commissioning the painting of the Sistine Chapel ceiling: "No...wait, we can't have all that clutter in the chapel...we need you to paint it with this:"

🤣

 

5 minutes ago, tfm said:

^ this.

Gotta love pmdg’s products but their habit of long-winded waffly announcements that carefully under-promise, which actually turn out to be long-winded waffly announcements that over-promise, is beyond parody.

This

PMDG is no longer the precursor in the Flight Sim Industry unfortunately (in comparison to FS Labs and iniBuilds for example)

Since Asobo invited Rob to the Q&A and had a nice chat. All doom talk aside, I do think Asobo with work with Robert(PMDG) and it will be fixed, what ever the problem is.

Its in both there interest to make it work.

Just now, Nyxx said:

Since Asobo invited Rob to the Q&A and had a nice chat. All doom talk aside, I do think Asobo with work with Robert(PMDG) and it will be fixed, what ever the problem is.

Its in both there interest to make it work.

More clever marketing. Those Q&A sessions remind me of press conferences with 10 downing street... 

Maybe AIG found something in the model they didn’t like…….

Can we stop beating around the bushes and let the cat out of the bag on what is not working? Dying to find out. 

4 hours ago, Tom_L said:

Yeah, I've had enough after SU5 and SU7 already! Looks like RSR has the same reservations: "I must be honest though and say that we are very concerned about continued disruptions to forward progress because of problems introduced by updates in this manner."

I think that a few developers hanging around this forum have been stating something similar to the words in italics above since the dawn of MSFS time.

Edited December 8, 20214 yr by Christopher Low

20 minutes ago, tfm said:

^ this.

Gotta love pmdg’s products but their habit of long-winded waffly announcements that carefully under-promise, which actually turn out to be long-winded waffly announcements that over-promise, is beyond parody.

For one, I find it rather nice that he speaks to us as adults and not teenagers, taking the time to explain with fully articulated sentences what he means. No 'wow ! ', no 'awesome !',  no 'you are going to be blown away !', no 'we are so excited !', the usual Redmond soup.

Edited December 8, 20214 yr by Dominique_K

25 minutes ago, JRBarrett said:

I doubt that VNAV is the problem. A real VNAV system only knows the wind speed and direction at the aircraft’s current position and altitude, and dynamically adjusts descent path as the wind changes.

Despite the lack of SDK weather functions for things like weather radar, wind speed and direction at the aircraft’s current position are available in MSFS using the standard simconnect variables that have been around since FSX. 

That's wrong, at least for modern VNAV. Why do you think you enter descent wind forecasts in the 737 and A320? They are being used for the calculation of the ToD. Of course VNAV can adjust afterwards to "real" winds, but in some cases (e.g. high cost index descents, certain speed constraints) it could be too late and the vnav path is lost/unreachable (unless manual intervention happens). This would be the worst case; the best case - but still annoying - is that it will just send you down too early/too late and you lose ~ 100 kg of fuel because your ToD wasn't accurate.

EDIT: Just to add up on this: Even if you'd do the manual rule-of-three descent you'd be using winds to add or subtract miles of your manual ToD, so why should this not matter to VNAV if you already have to do that in the old school no-VNAV method?

Edited December 8, 20214 yr by Fiorentoni

42 minutes ago, phmcr said:

The day RR announced development of the 737 for MSFS, I bought it together with a new pc. Till then I was an enthusiastic P3Dv4 pilot convinced MSFS was only for low and slow. I actually figured that all the problems he mentions now had been dealt with as we know PMDG will not lower their standards. But alas, as often as we are experiencing broken features, it must have frustrated PMDG too. Should LM publish P3Dv6 now, I think I am very tempted to get my hands on that and to install all my abandoned add-ons again, including my PMDG iron!

It would be very difficult to go back to previous platform after seeing what is capable graphics wise with moderate systems, but I’m almost tempted to re-install p3d for the majestic dash-8 and PMDG 747….Or maybe try my hand at something totally new and dive into X-plane for the time being until msfs can get things figured out…I would still use msfs but for a very specific reason mainly being GA…..As mentioned, I’m tempted, but not sure I can actually do it. 

Edited December 8, 20214 yr by flyinpilot212121

5 hours ago, Dominique_K said:

We are far from the Redmond marketing neumannish.

I'm really getting sick of seeing nonsense like this. Jorg is an optimistic guy who's job it is to sell his product but at the same time he has not been one to shy away from the reality of the issues at hand. I've seen him admit that updates were rushed out the door and I've seen him speak candidly many times about issues 3PDs are facing with the SDK. Y'all need to stop.

36 minutes ago, regis9 said:

I hope Asobo takes this as the wake up call it should be.  Not a good look to have a recently announced partner saying that Asobo is preventing them from moving forward.  

Sure they will. Expect MSFS 2022 Ultimate Edition at $54.99 (for the owners of MSFS 2020 Pro) sometimes in the middle of October 2022. This, perhaps, will be the final stable version