1 hour ago, SimianFlu said:

Okay, I have removed the Navigraph data and the sim still won't load (only does in safe mode)

 

great job MS. Any hints? I have zillion of addons, removing them one by one is out of the question

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.

I have Navigraph data up and running in the sim, post update.  Here's how...

As I always do (and you should to!) I renamed my community folder before proceeding with the update.  All went well and I shut down the sim in order to move my community folder back in place.  BEFORE I RESTARTED, I checked the interwebs, discovered the problem with the Navigraph AIRAC and removed it using Navigraph Hub.  I then restarted the sim and loaded it fully and shut down again, went back to Navigraph Hub and re-installed the AIRAC.  I then restarted the sim and all is well.

Note that it's not clear that loading the current AIRAC from Navigraph is necessary as 2409 should be in the update.  I just feel better knowing the data is good.

FYI.

 

Scott

Edited October 1, 20241 yr by tttocs

emptied Community

Uninstalled all Navigraph stuff shown in Navigraph Hub

Started FlightSim via Steam with none of my normal "helper apps" enabled

722MB mandatory update required less than one minute to install

continued with test flight in sim - ended normally

stopped sim

reinstalled all Navigraph stuff in Hub

started FlightSim via Steam with all helper apps running (Map Enhancement / AutoFPS / Simlink / FSRealistic / FSLTL injector / PSXT and so on)

continued with test flight in sim - ended normally

stopped sim

restored Community to it's normal bloated self (about 60 addons)

started FlightSim via Steam

continued with test flight in sim - ended normally

 

Looks like Navigraph have identified the problem as an issue with the default MSFS nav data.
https://forums.flightsimulator.com/t/sim-doesnt-start-any-more-after-2024-10-01-update-remove-navigraph-airac-cycle/657041/406

I'm seeing reports that there's now an update to the update that fixes the problem but I can't confirm that yet.

-- Edit --

It doesn't look to be fixed (for me at least) so waiting for tomorrows AIRAC update it is then.

Edited October 1, 20241 yr by Matchstick

4 hours ago, MarcG said:

MS/Asobo struggle testing their own software let alone others 😂 

...like I was saying 🤪 

2 minutes ago, MarcG said:

...like I was saying 🤪 

and that's why they need proper beta testing of all their releases (and then listen to and act on what the beta testers tell them)

Edited October 1, 20241 yr by Matchstick

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.

 

Edited October 1, 20241 yr by Georgleboui

33 minutes ago, Matchstick said:

Looks like Navigraph have identified the problem as an issue with the default MSFS nav data.
https://forums.flightsimulator.com/t/sim-doesnt-start-any-more-after-2024-10-01-update-remove-navigraph-airac-cycle/657041/406

I'm seeing reports that there's now an update to the update that fixes the problem but I can't confirm that yet.

Can't wait for all the "its tested in a sandbox, Asosbo isn't responsible for 3 party errors" people to come out and apologize.  Figure I'll be waiting for a long time.  No public beta contrary to almost every other release, updated with errors, but yea we shouldn't discuss if the project PM maybe isn't cut out for the job or else we are toxic.

2 minutes ago, nrunning24 said:

Can't wait for all the "its tested in a sandbox, Asosbo isn't responsible for 3 party errors" people to come out and apologize.  Figure I'll be waiting for a long time.  No public beta contrary to almost every other release, updated with errors, but yea we shouldn't discuss if the project PM maybe isn't cut out for the job or else we are toxic.

Well Blah Blah Blah Blah. Believe it or not its not MS or Asobo's fault when 3rd party developers addons are not compatible with the new current updates, but (Hey) they keep making money off the platform with no additional cost (sans MP) but keep hope this will happen some day but believe what you want which is not reality.

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.

1 minute ago, JBDB-MD80 said:

Well Blah Blah Blah Blah. Believe it or not its not MS or Asobo's fault when 3rd party developers addons are not compatible with the new current updates, but (Hey) they keep making money off the platform with no additional cost (sans MP) but keep hope this will happen some day but believe what you want which is not reality. MS and Asobo is responsible for their in house testing only.

 

1 minute ago, JBDB-MD80 said:

Well Blah Blah Blah Blah. Believe it or not its not MS or Asobo's fault when 3rd party developers addons are not compatible with the new current updates, but (Hey) they keep making money off the platform with no additional cost (sans MP) but keep hope this will happen some day but believe what you want which is not reality.

LOL MSFS has the wrong info, but if you dont have 3rd party info that is actually correct you wont even see this error isn't the comeback you think it is.

2 minutes ago, JBDB-MD80 said:

Well Blah Blah Blah Blah. Believe it or not its not MS or Asobo's fault when 3rd party developers addons are not compatible with the new current updates, but (Hey) they keep making money off the platform with no additional cost (sans MP) but keep hope this will happen some day but believe what you want which is not reality.

The data error is on the Asobo side. They created a double-entry in the config that created an incompatibility with Navigraph. That's as simple as that. 

Again, I'm not saying the issue is that they broke something with third parties.

I'm saying the issue is that they have created a platform, and therefore need to be sympathetic in how they approach their patches. In other words - do extensive, public beta tests. That's it. 

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...

Edited October 1, 20241 yr by Flic1

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.