Hi Grayson,
thanks for the report but how should we check this or reproduce this, without knowing on which airport, on which runway and on which approach does this happen?
Also which addon/aircraft has you used and last, do you use the stock scenery or a 3rd party scenery?
This basic requirements are necessary to know, that we can try to reproduce it.
Thanks Grayson,
what is the B77W? Is this a stock aircraft, a 3rd party aircraft? Also you can confirm that you´re using the stock NZAA scenery - so no 3rd party scenery for NZAA?
Last, when you try the same with ie. the stock A320 NEO - do you have the same effect?
Hi Grayson,
but you can´t use the addon and the scenery for around 20 years - the MSFS is available only for 4 years and the addons and sceneries are not compatible. So, can you confirm, that you are using the MSFS?
Please, to avoid some more questions and to avoid some misunderstandings, please follow the link, posted by Ian - that we get really all information what we need.
First check if your registry entry is ok and fix it with following tool:
Second step (Root cause is bad scenery)
If the issue is still present, disable all add on scenery and reenable them step by step to find the bad scenery that can cause magvar issues worldwide.
No, which data do you download and install for this specific addon. Every addon has a own dataset. To compare the cycles, I must know which data I should compare with what.
So, do you download the PSS dataset, the PMDG dataset, the iFly dataset, …
Post a screenshot of your FMS Data Manager and show me the line on the Addon page, which you are using for the updates. Thank you!