FACT MSFS V1.2 release.
Posted: Wed Dec 29, 2021 12:57 pm
Good day. I have been notified of an update for FACT for MSFS to v1.2. Been looking around for a changelog. Could you give any information on the fixes? Regards.
Finest Flight Simulation Products
https://forum.flightsimdevelopmentgroup.com/
https://forum.flightsimdevelopmentgroup.com/viewtopic.php?f=3&t=3336
Good dayhorst18519 wrote: ↑Thu Dec 30, 2021 3:24 pmYou can always find the latest versions and changes here:
https://fsdg-online.com/Version-History ... :_:16.html
Well, there is a till a problem with slopes in this version 1.2. Check Runway 16 / 34.horst18519 wrote: ↑Mon Jan 03, 2022 3:10 pmThe new version mostly consisted of adjusting the terrain (removing slopes between apron and runway) and floating objects.
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.SAPilot wrote: ↑Mon Jan 03, 2022 9:16 pmWell, there is a till a problem with slopes in this version 1.2. Check Runway 16 / 34.horst18519 wrote: ↑Mon Jan 03, 2022 3:10 pmThe new version mostly consisted of adjusting the terrain (removing slopes between apron and runway) and floating objects.
I have now uninstalled this scenery package - too many errors which were reported last year and recently and either not fixed or acknowledged.
Sorry, not the way to treat a customer.
You have lost a customer and I will not post here anymore about all the issues with MSFS 2020 FACT Scenery package.
Thanks for the tips. Did it exactly as you described above.Peter Webber wrote: ↑Tue Jan 04, 2022 5:12 amHi...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.SAPilot wrote: ↑Mon Jan 03, 2022 9:16 pmWell, there is a till a problem with slopes in this version 1.2. Check Runway 16 / 34.horst18519 wrote: ↑Mon Jan 03, 2022 3:10 pmThe new version mostly consisted of adjusting the terrain (removing slopes between apron and runway) and floating objects.
I have now uninstalled this scenery package - too many errors which were reported last year and recently and either not fixed or acknowledged.
Sorry, not the way to treat a customer.
You have lost a customer and I will not post here anymore about all the issues with MSFS 2020 FACT Scenery package.
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.
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.
Regards.
I have identified the issue! Listen up Horst! It has nothing to do with Navigraph. When we first install FSDG Cape Town, it removes the ASOBO entry for FACT in the Content.xml file. So when we first fire up the sim, all is good. Now when we restart the sim at a later stage, MSFS re-populates the Content.xml file with ASOBO FACT! So now we have both FSDG AND ASOBO in the Content.xml. This is the conflict. I think FSDG need to simply change the ASOBO entry to "FALSE", and not to remove it. Otherwise MSFS just re-adds it! I hope FSDG get this message.SAPilot wrote: ↑Tue Jan 04, 2022 7:06 amThanks for the tips. Did it exactly as you described above.Peter Webber wrote: ↑Tue Jan 04, 2022 5:12 amHi...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.SAPilot wrote: ↑Mon Jan 03, 2022 9:16 pm
Well, there is a till a problem with slopes in this version 1.2. Check Runway 16 / 34.
I have now uninstalled this scenery package - too many errors which were reported last year and recently and either not fixed or acknowledged.
Sorry, not the way to treat a customer.
You have lost a customer and I will not post here anymore about all the issues with MSFS 2020 FACT Scenery package.
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.
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.
Regards.
Still a no-go for me.
What is strange is that when after the rebuild of Content.xml [with Navigraph removed] it looks fine.
But, If I shutdown the sim and restart - the problem is back. See below.
Now this even more strange. I don't see the behavior you describe above. The entry remains there when I install FSDG FACT :Peter Webber wrote: ↑Tue Jan 04, 2022 10:20 amI have identified the issue! Listen up Horst! It has nothing to do with Navigraph. When we first install FSDG Cape Town, it removes the ASOBO entry for FACT in the Content.xml file. So when we first fire up the sim, all is good. Now when we restart the sim at a later stage, MSFS re-populates the Content.xml file with ASOBO FACT! So now we have both FSDG AND ASOBO in the Content.xml. This is the conflict. I think FSDG need to simply change the ASOBO entry to "FALSE", and not to remove it. Otherwise MSFS just re-adds it! I hope FSDG get this message.SAPilot wrote: ↑Tue Jan 04, 2022 7:06 amThanks for the tips. Did it exactly as you described above.Peter Webber wrote: ↑Tue Jan 04, 2022 5:12 am
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.
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.
Regards.
Still a no-go for me.
What is strange is that when after the rebuild of Content.xml [with Navigraph removed] it looks fine.
But, If I shutdown the sim and restart - the problem is back. See below.
What about the windsock - wrong direction - issue ?horst18519 wrote: ↑Tue Jan 04, 2022 5:57 pmAll I can say is that there doesn't seem to be an issue with our scenery as we cannot replicate that problem on our test systems.
I thought the tips above (navigraph,...) would help fix the problem.
This duplication of scenery and overlapping of scenery is a well know issue. Horst, are you using a version of MSFS which does not contain ASOBO FACT, i.e. Standard version only? If so, you will not see the scenery conflict. To SA Pilot, here is the solution:SAPilot wrote: ↑Tue Jan 04, 2022 6:09 pmWhat about the windsock - wrong direction - issue ?horst18519 wrote: ↑Tue Jan 04, 2022 5:57 pmAll I can say is that there doesn't seem to be an issue with our scenery as we cannot replicate that problem on our test systems.
I thought the tips above (navigraph,...) would help fix the problem.
What about the ILS Frequencies ?
- see other thread for screenshots.
Are all the above not a problem on your test system ?