17 minutes ago, Flic1 said:

I have not tried the NEO since it first came out but just tried a quick flight.  Overall not bad but man, I really hope IniBuilds are using a different sound engineer for the A350.  The sounds, although better than the initial release are still out of balance at certain times of flight (ie, way too loud on approach vs how it sounds on initial climbout).  Also, the Flood lights do not seem to work...

Yeah I don't love their internal sounds.  Though on the A300, I do really like the external ones. 

5 minutes ago, Krakin said:

It really isn't Asobo's responsibility to test with third party add-ons in mind. When adjustments are made and products get broken, it is up to that dev to get their stuff fixed. What Asobo has to do is ensure that proper guidance is given via proper updates to documentation for the SDK among other things.

Agree 100%. 

But that's not the issue. The issue is that Asobo made a mistake in their data and pushed it live with this patch, breaking Navigraph. Should they test internally with all add ons? Again, no.

However, they do know that they are running a platform, an ecosystem of different add ons. And they know this, and they've accounted for it with previous SU's and the public beta program. And it's been working great.

The issue we are all raising is that their mistake is in not doing a public beta test with this patch like they've done before. Really this shouldn't have happened, and they dropped the ball here.

 

1 hour ago, Matchstick said:

The standard techinique is remove them all, see if that works. Then if it does put half back and repeat the test. That should tell you which half of the addons the problematic one is.
Keep doing that until you narrow down to the specific items (and hope it's not triggered by combinations of addons)

This is an awful lot easier with something like MSFS Addon Linker to allow you to switch addons on and off quickly.

Thankfully updating the FBW a320n solved the issue (or maybe it was just a coincidence and the navigraph data expunged from cache). Ooomph.

OR - we could go back to the "good old days" when the dinosaurs ran only the software provided by their hardware vendor.  The SE and FE (software and field engineer) told us what we could do and when we could do it.  We ALWAYS knew who to blame.

BUT - creativity was limited, the user was seldom considered, and the applications we users really wanted seldom appeared in the time frame we wanted.

All in All - I think ASOBO and their many 3rd party contributors do a fantastic job of coordinating and testing.  This overblown event was resolved in less than a day with no loss of data, security issues, or damaged hardware. 

I really think we are spoiled and impatient due to the astounding growth in sim addons and enhancements.  

Sure - it would be nice if Navigraph had a chance to test in Beta as well as the dozen or so really important vendors I use, (your important ones are probably different so we have to keep expanding the test environment... and slowing it down).  But, that may not be practical and we do know that ASOBO/MicroSoft do know what is best.

I am pleased and happy with the way the whole MSFS 2000 ecosystem has evolved and continues to evolve and improve. 

1 hour ago, Georgleboui said:

So apparently it may be fixed tomorrow when the new Asobo-supplied AIRAC gets updated. Or not.
If latter, Navigraph will push a new revision that should fix it.

All because of a dirt strip in Brazil (SNFO)  😞

EDIT: Just to add a positive note - I am excited for the 310 fixes. I've been wanting to use it for my OnAir VA for ages.

 

SNFO sounds almost like SNAFU

It's going to be something when it is finally revealed whose fault it is.

7 hours ago, Tuskin38 said:

It's not an opinion, it's fact.

Sure, in your opinion it’s a fact 🙂 .
 

Also good job to the other person with the personal attacks questioning whether I know anything about software or game dev. 

Well I’m sure he knows more than me and I don’t care to get into personal attacks. I don’t need to prove anything about my credentials to anyone for random internet points that mean nothing.  

However, I will point out that platforms routinely test against third party software. And you know which company is really well known for backwards compatibility? Yup. Microsoft. They are the single biggest proponents of backwards comp in the industry. 

Back in the day they did this - 

“In 2005, longtime Microsoft staffer and The Old New thing blogger Raymond Chen documented Microsoft's Windows 95 compatibility obsession. Chen writes that Windows 95's development manager "took his pick-up truck, drove down to the local Egghead Software store (back when Egghead still existed), and bought one copy of every single PC program in the store." Everybody was responsible for up to two programs, which they would install, run, and document for bugs. If a staffer finished two, they could come back to grab up to two more. And testers could keep whatever they finished.“

Source: https://arstechnica.com/gadgets/2022/10/windows-95-went-the-extra-mile-to-ensure-compatibility-of-simcity-other-games/

Raymond’s blog is full of interesting things like this, btw.

Edited October 2, 20241 yr by JonathanC

Also there's sum tin wong with the ILS... didn't work at TFFR (Pointe-a-pitre) with the headwind a339 nor RJBB (Osaka Kansai) with PMDG 777. The 777 was somehow guided in APP mcp mode but the app efis mode was displaying zip

 

Edited October 2, 20241 yr by SimianFlu

Haha just saw this. 
 

so.. the CTD was because MSFT left a typo in a BGL file. I’m sure this is Navigraph’s as well! 

 

16 minutes ago, SimianFlu said:

sum tin wong 

love it !!

 

I guess those having a crack at Navigraph probably need to start baking a large piece of humble pie:

 

https://www.avsim.com/forums/topic/650259-please-be-aware-todays-update-can-cause-crashes/?do=findComment&comment=5178420

7 hours ago, edpatino said:

MS/Asobo did it again, as simple as that. Thanks Navigraph for providing such a great navdata service. Now, the ball is in MS/Asobo's park.

Well after 4 years the 787 doors are still borked. So don't hold your breath 

4 hours ago, JonathanC said:

Haha just saw this. 
 

so.. the CTD was because MSFT left a typo in a BGL file. I’m sure this is Navigraph’s as well! 

 

Back in p3d days it looks LM nearly 2 years to acknowledge that bgl data was conflicting with gsx 

11 hours ago, Tuskin38 said:

They're probably too busy with 2024.

This !!

cheers 😉

So all the World Hub Updates have apparently been deleted and it's "being looked into".

So here we are again, with the crashing bug and now this, what is it? A severe lack of Quality Control.