Starting today, March 5, 2021, strange things happen within my FS2020. I am flying the FBW Airbus A32NX. When entering data by mouse clicks in the FMCU after a few mouse clicks FS2020 hangs. No input whatsoever (neither mouse, keyboard or joystick) is being accepted, the thing is just stone-dead. I have tried all FBW Airbuses and with everyone of the three the same happens. The hangs happen randomly, but most of the time when I am in the PERF page.
Strangely enough (or perhaps not) this does not happen when I use the stock A320NEO.
After emptying my Community folder and re-entering my add-ons (Aerosoft’s EDDK, EDLP, ENVA and ORBX’s ENAL), all worked well again. After (re)installing Navigraph navdata the above issue happened again.
My apologies for posting in this section, the “New Topic” entry in MSFS Beta was greyed out.
Hi Hans,
sorry, but this is not a navdata issue, it´s more a sim issue or better a scenery-issue I guess (or possible a combination of scenery issue and FBW, I don´t know).
You wrote you have “reinstalled” the Navigraph navdata - how?
Second, please can follow exact these steps and can you try it again:
It´s important to do really exactly these steps. It´s not “dangerous” for your sim, but the scenery file will be re-organized. This method with “cleaning” and “re-importing” the community folder is only to find out, if there is an addon which makes troubles in the sim or not. But it doesn´t clean/resort your scenery-file.
So please follow exactly these steps above and try it again …
I reinstalled the data by removing them via the navigraph navdata installer and then importing them again via the same installer.
After reading your reply I uninstalled the installer, downloaded the latest version and installed it. After that I fired up MSFS2020, positioned myself on a rwy and entered data in the FMCU of the FBW A32NX. Unfortunately I still am running into this issue.
Earlier this afternoon I uninstalled all the sceneries that sat in my community folder (see above). Reinstalled “fresh” versions of them and the described issue was not encountered. I then imported Navigraph nav data and I ran into this anomaly again. Hence my conclusion that the navdata caused, in one way or another, the FS2020 to hang.
What else can I do but removing navdata to avoid these hangs?
Hi Hans,
thank you … but in this case, it´s a FBW A320 issue … do you use the stable version, or any dev version? I use the stable version and this version works correctly …
Cheers,
Richard
It is getting weirder and weirder. The described issue only happens when I use an EDDK-LICJ flightplan, generated by SImbrief. Other flightplans I used didn’t cause any problem. You may want to try it, here’s the FP:
Hi. I noticed this error last night and spent most of the night and a chunk of this afternoon tracking down the issue.
The issue seems to be a conflict in the flight planning between the Navigraph data and the info in the current AIRAC cycle in the stock MSFS. My route was from LSGG-LIRF. When I use the A320NX, Navigraph, and the Simbrief import it hangs the sim.
When I use the stock aircraft and enter every waypoint I get errors that waypoints/airways aren’t found.
I didn’t do such a thorough investigation as you did, I just gave up when Richard said that it was a failure not to be connected to Navigraph. I circumnavigate the problem by not planning a flight to LICJ :
There is a bug in FBW in that it doesn’t gracefully handle the error. So, two bugs, really. One in FBW and one between Navigraph data and MSFS data not playing nicely together at the moment.
Hi,
to clarify something:
When our AIRAC update is installed correctly (via the Navigraph-Installer beta 23), there are NO, really NO stock data will be used any longer. So, I don´t know exactly what “between Navigraph data and MSFS data not playing nicely together” mean - they don´t play together. When you use the Navigraph data, you use ONLY the Navigraph data and nothing more.
When you use the internal flight planning and you have our package installed, you use ONLY our data. The stock data are disabled.
Please can you upload the Simbrief file, which you try to import it in the sim, that we can try to reproduce it?
Richard, attached you’ll find the Simbrief file that caused the problem for me. Just import the plan, fill out the necessary data in the MCDU’s INIT fields then go to PERF, enter 1 for flap settings and then enter for example 55 for temperature in the field right below the flap settings one. (Sorry, I don’t know the correct nomenclature by the top of my head, I am not at my FS2020 computer right now). In my case it will not be possible to enter any data in the “temperature” field.
Ok Hans, I´m still not sure, why you mean, that this is a data issue rather a FBW issue but anyway, I have also tested your additional notes, no hanging and I can set the flex temp without any problems:
No need to be sorry . But you know what? With the latest version of FBW’s A32NX Dev Mod I now, too, don’t have the reported problem anymore. I take it, that FBW have changed something that now makes entering the flight plan in question without any problem. All’s working fine for me again. Thanks a lot for your cooperation.
![86 2[1].jpg](https://europe1.discourse-cdn.com/flex013/uploads/navigraph1/original/2X/4/481cb75d234cd6baf612d21f02c91ba83e18b2d9.jpeg){kind=small}
… You know where do you find us