Page 3 of 3
Re: Cape Town MSFS
Posted: Wed Dec 29, 2021 8:52 pm
by SAPilot
Peter Webber wrote: Wed Dec 29, 2021 5:29 pm
SAPilot wrote: Sun Dec 26, 2021 5:41 pm
Version 1.2 - downloaded from Aerosoft
Problem with runway/taxiway/apron markings. See below
Do you use Navigraph data for MSFS? You will need to reorganise the scenery priority. This is a common cause of so called "double runways". Check out the Navivraph forum.
Yes, I use Navigraph.
If I remember corrrectly , Navigraph was removed during my testing, and still had the problem.
I had a look around the Navigraph Forum and could not find what you mentioned in your post.Would you please be so kind to post a link ?.
Thanks
Re: Cape Town MSFS
Posted: Fri Dec 31, 2021 12:29 pm
by Peter Webber
SAPilot wrote: Wed Dec 29, 2021 8:52 pm
Peter Webber wrote: Wed Dec 29, 2021 5:29 pm
SAPilot wrote: Sun Dec 26, 2021 5:41 pm
Version 1.2 - downloaded from Aerosoft
Problem with runway/taxiway/apron markings. See below
Do you use Navigraph data for MSFS? You will need to reorganise the scenery priority. This is a common cause of so called "double runways". Check out the Navivraph forum.
Yes, I use Navigraph.
If I remember corrrectly , Navigraph was removed during my testing, and still had the problem.
I had a look around the Navigraph Forum and could not find what you mentioned in your post.Would you please be so kind to post a link ?.
Thanks
https://forum.navigraph.com/t/faq-scene ... ation/4035
Re: Cape Town MSFS
Posted: Fri Dec 31, 2021 2:35 pm
by Peter Webber
Update: I'm also getting issues with runway overlay. I see double markings. It's as if the default scenery is not being excluded.
Re: Cape Town MSFS
Posted: Sat Jan 01, 2022 8:08 pm
by SAPilot
Peter Webber wrote: Fri Dec 31, 2021 2:35 pm
Update: I'm also getting issues with runway overlay. I see double markings. It's as if the default scenery is not being excluded.
Hi Peter
Does it look the same as the screenshot I posted earlier in this topic?.
Hopefully we will get some feedback/acknowledgement regarding this issue, after the festive season holidays.
Happy New Year
Re: Cape Town MSFS
Posted: Mon Jan 03, 2022 9:21 pm
by SAPilot
Peter Webber wrote: Fri Dec 31, 2021 2:35 pm
Update: I'm also getting issues with runway overlay. I see double markings. It's as if the default scenery is not being excluded.
Hi Peter
I got fed up and the scenery now uninstalled.
Why have a support forum and nobody from developer side reacts. ?.
Re: Cape Town MSFS
Posted: Mon Jan 03, 2022 9:25 pm
by SAPilot
Peter Webber wrote: Wed Dec 29, 2021 5:29 pm
SAPilot wrote: Sun Dec 26, 2021 5:41 pm
Version 1.2 - downloaded from Aerosoft
Problem with runway/taxiway/apron markings. See below
Do you use Navigraph data for MSFS? You will need to reorganise the scenery priority. This is a common cause of so called "double runways". Check out the Navivraph forum.
Done that - no change.
Re: Cape Town MSFS
Posted: Tue Jan 04, 2022 5:15 am
by Peter Webber
SAPilot wrote: Mon Jan 03, 2022 9:25 pm
Peter Webber wrote: Wed Dec 29, 2021 5:29 pm
SAPilot wrote: Sun Dec 26, 2021 5:41 pm
Version 1.2 - downloaded from Aerosoft
Problem with runway/taxiway/apron markings. See below
Do you use Navigraph data for MSFS? You will need to reorganise the scenery priority. This is a common cause of so called "double runways". Check out the Navivraph forum.
Done that - no change.
Hi...I have had the exact same issues. But I believe it is not FSDG. For myself it is caused by the "beta" MSFS Navigraph software. This is also in reply to your other post.
I have found even when "removing" Navigraph, the issues you describe with FACT are still present. Here are the steps I take:
1) Remove Navigraph using their installer.
2) Restart MSFS.
3) Shutdown MSFS
4) Delete MSFS "Content.xml"
5) Restart MSFS and let it rebuild Content.xml.
6) DO NOT re-install Navigraph.
You will then see there are no further issues.
I have stopped using Navigraph for MSFS for now. Remember it is in beta. It's causing too many issues with FSDG FACT. Simply removing it via the installer does not work. You have to delete Content.xml and allow MSFS to rebuild it. The moment I "install" Navigraph, problems are back.
Maybe FSDG can look at compatibility from their side, but for now I think the problem is with Navigraph data.