Aside from the CTD if you have Navigraph AIRAC installed, just a friendly reminder to check the Content Manager after you upgrade to AAU3. There was an update to the A310 available for my installation. YMMV of course.

Oh the NeoV2 also has working terrain radar now.

Just now, Malaromane said:

Aside from the CTD if you have Navigraph AIRAC installed, just a friendly reminder to check the Content Manager after you upgrade to AAU3. There was an update to the A310 available for my installation. YMMV of course.

That's for the free enhanced package. There's also one for the Neo if you have it installed.

6 minutes ago, Abriael said:

The fact that the AAU3 was coming today was known and previously announced. There was plenty of notice

There was no beta for AAU3. The first anyone got their hands on it was today.

Just now, BrammyH said:

There was no beta for AAU3. The first anyone got their hands on it was today.

Who exactly mentioned a beta? That's entirely irrelevant to the topic at hand.

Just now, Abriael said:

Who exactly mentioned a beta? That's entirely irrelevant to the topic at hand.

You said, "The fact that the AAU3 was coming today was known and previously announced. There was plenty of notice."

To test against what, exactly? They didn't get any pre-release code either.

1 minute ago, Abriael said:

Who exactly mentioned a beta? That's entirely irrelevant to the topic at hand.

No it isn't. If we had the usual limited public beta, this may have been spotted beforehand saving all other Navigraph users the inconvenience.

4 minutes ago, BrammyH said:

You said, "The fact that the AAU3 was coming today was known and previously announced. There was plenty of notice."

To test against what, exactly? They didn't get any pre-release code either.

I mentioned a notice. Not a beta. 

3 minutes ago, bobcat999 said:

No it isn't. If we had the usual limited public beta, this may have been spotted beforehand saving all other Navigraph users the inconvenience.

It's Navigraph's responsibility to save Navigraph's users the inconvenience. You're barking at the wrong tree.

Betas are not mandatory and they're obviously done only for the biggest updates, which this one is not. 

Edited October 1, 20241 yr by Abriael

6 minutes ago, bobcat999 said:

No it isn't. If we had the usual limited public beta, this may have been spotted beforehand saving all other Navigraph users the inconvenience.

The greatest irony here is for AAU3 is according to a MSFS / Asobo post this morning he only group excluded from this drop was the beta group.  We (me and others) just received it minutes ago albeit with the knowledge about the airac, which I removed as the sim was downloading the 2.2 Fig update.

All is well right now but I already miss my airac!

-B

Edited October 1, 20241 yr by btacon

1 minute ago, Abriael said:

t's Navigraph's responsibility to save Navigraph's users the inconvenience

I am truly having a hard time with this one.

Ok. MS told us last week that AAU3 is coming out today.

They did not make pre-release code available to anyone to test.

Navigraph therefore was unable to even see this was going to be a problem until this morning.

Yet, this is Navigraph's fault? What steps are you thinking Navigraph could take with this one?

It's at least on MS they tossed this one over the fence without giving anyone a chance to test.

3 minutes ago, Abriael said:

I mentioned a notice. Not a beta. 

It's Navigraph's responsibility to save Navigraph's users the inconvenience. You're barking at the wrong tree.

Betas are not mandatory and they're obviously done only for the biggest updates, which this one is not. 

Well, without a beta to test against, they obviously can't save anyone the inconvinience. This is a minor issue, but it is fair to expect MS to test against a few dozen top addons - or have a developer-only/public beta so these kinds of things can be avoided. 

While it is not the platform's responsibility to cater to addons, it's also their responsibility to not break something without notice, leaving people scrambling to catch up. And no, simply saying "the sim may break in a few weeks, get ready" is not sufficient since it doesn't allow for any actions to be taken. 

Wow! I notice certain people are becoming absolutely staunch defenders of MS / Asobo just lately no matter what the situation.  

I suppose an expensive invite to a preview event can grip some people.

I say again, a beta would have been relevant to try to catch these situations.  That was the system we had previously and was working well.  Only one party is at blame for not running through a beta.

5 minutes ago, BrammyH said:

I am truly having a hard time with this one.

Ok. MS told us last week that AAU3 is coming out today.

They did not make pre-release code available to anyone to test.

Navigraph therefore was unable to even see this was going to be a problem until this morning.

Yet, this is Navigraph's fault? What steps are you thinking Navigraph could take with this one?

It's at least on MS they tossed this one over the fence without giving anyone a chance to test.

No one said it's Navigraph's fault. 

It's navigraph's responsibility. 

IE: an incompatibility is found, and now it's Navigraph's responsibility to either find a solution on their side or reach out for help. Their response "it's a sim problem" is highly irresponsible. 

The sim works. Navigraph does not. It's a Navigraph problem.

Again, there are thousands of add-ons for MSFS. It isn't MS or Asobo's responsibility to make sure they keep working with every update. Hence, you're barking at the wrong tree. 

4 minutes ago, JonathanC said:

Well, without a beta to test against, they obviously can't save anyone the inconvinience. This is a minor issue, but it is fair to expect MS to test against a few dozen top addons

No. It is not. Again, who decides which add-ons should be tested against? Where do you draw the line? Microsoft/Asobo have one responsibility, and it's for Microsoft Flight Simulator to work. It's the responsibility of every addon's developer to make sure that their add-ons work with the base software. 

Edited October 1, 20241 yr by Abriael

1 hour ago, Tuskin38 said:

People on the MSFS Discord are saying it’s related to the navigraph nav data 

some have said deleting and reinstalling the nav data from the Hub works

Always disable addons at the first sign of trouble! (just helped me with an issue in a different simulator last night!)

Navigraph is one of the most popular add-ons for MSFS and critical for many of the leading aircraft and other utilities.

You can blame third party developers if you want but expect to alienate a significate chunk of your user base if you release compulsory updates that break their sim.