maybe   Thanks to all

On 12/6/2020 at 8:00 AM, Ray Proudfoot said:

I purchased Louisville as I wanted an airport between the East coast and Chicago. Only a tenner so a bargain. Didn’t realise until I loaded it that it’s a UPS hub but at least there are a few pax gates.

Was rather less impressed that the installer decided to check all my FSDT airports and GSX and then updated the lot. I wish it wouldn’t do that or at least give me the option. I don’t feel I have control of my system. It then rechecked all my registrations and made backups of my reg files which I already had.

I’ve been holding back from updating GSX as I’ve had problems with P3D v3.4 and CTDs at certain positions which was only resolved by uninstalling GSX and reinstalling. Fingers crossed they don’t reoccur.

 

Running the latest GSX here with P3Dv3.4.22.19868 and no issues.

I have most of them now only buying made for V5 airports, not interested in large airports for MSFS.

5 hours ago, udidwht said:

Running the latest GSX here with P3Dv3.4.22.19868 and no issues.

Perhaps because you had installed updates when prompted. I hadn't. Perhaps that's why it went through the whole process when I installed Louisville.

On 12/6/2020 at 8:47 PM, Aharon said:

I tried FSDT KMEM and klax that I bought from last year. NOTHING WORKS.

I have 12 years of experience of installing FSX sceneries from all payware companies such as Aerosoft, FlyTampa, etc etc BUT nothing from FSDT sceneries work in FSX. It keeps telling me that Norton Anti Virus is blocking it even though I followed their instructions to add FSDT Add-on Manager to exclusion list.

Spent 1 or 2 hours trying to get it working.  Gave up

I can understand your frustration as I have been in the same situation a number of times over the years where all my FSDT scenery stops working for one reason or another and I too often felt like giving up on it. However on each occasion, often after a frustrating hour or two, I managed to get them up and running again, which was a relief as I have bought all their available airports for FSX.

I last had a problem like this about 6 months ago and resolved it, if I remember correctly, by uninstalling all the FSDT airports and reinstalling them. However the key was to also uninstall any old versions of addon manager on your system and then use the latest installer to reinstall the scenery. The reason I had the problem was that I still had an old version of the addon manager installed. If you follow the advice from Umberto on the following thread in the FSDT support forum you should get it working: http://www.fsdreamteam.com/forum/index.php?topic=20958.0

Hopefully this will help you to get this great scenery back!

Bill
 

Edited December 17, 20205 yr by scianoir

15 hours ago, scianoir said:

I last had a problem like this about 6 months ago and resolved it, if I remember correctly, by uninstalling all the FSDT airports and reinstalling them. However the key was to also uninstall any old versions of addon manager on your system and then use the latest installer to reinstall the scenery. The reason I had the problem was that I still had an old version of the addon manager installed.

@scianoirThanks for your kind suggestions but the problem is that I was installing my very first FSDT scenery for first time into my system therefore there was no old version of add on manager or whatever FSDT had in my system. It was first time installation.  

Also, if I am paying $$$$, the scenery installation process should be painless and easy like my airport scenery purchases past 12 years from all other famous software companies such as Aerosoft, Flightbeam, UK2000, Blueprint, Orbx, Tropical Sims, etc etc.

Regards,

Aharon

Regards,

Aharon

Edited December 17, 20205 yr by Aharon

OK, one last thing you might like to try to see if you can get them running - I notice that you mentioned that you bought KLAX and KMEM last year so it might be worth redownloading them to get the latest installer and try again with that. But, again, make sure you have uninstalled everything from any previous FSDT installation attempt before you install any new versions.

Bill

Thanks, @scianoir

I think it has something to do with Norton anti virus protection.  FSDT should have included step by step instructions in the installation notes or on the sticky post in the FSDT forums on how to get the Norton product accept and allow FSDT products.  I do not see such instructions.

Or my pc simply does not like FSDT products or FSX does not like FSDT products..........

Regards,

Aharon

3 hours ago, Aharon said:

Thanks, @scianoir

I think it has something to do with Norton anti virus protection.  FSDT should have included step by step instructions in the installation notes or on the sticky post in the FSDT forums on how to get the Norton product accept and allow FSDT products.  I do not see such instructions.

Or my pc simply does not like FSDT products or FSX does not like FSDT products..........

Regards,

Aharon

All you need to do is to right click the Norton icon in your task bar and then click on "Disable Auto-Protect". Works for me every time.

Happy Holidays!

Totally agree about Norton.  I finally learned after a few years to just disable Norton's.  Norton can be a problem with other software as well.  I usually disable antivirus and firewall.  Usually will set time limit for disable. 

That is NOT going to solve the problem because you cannot disable Norton EVERY time you fly into or out of any FSDT scenery hence my suggestion that FSDT should include specific step by step instructions how to program and set Norton to accept any FSDT products.

 

Nowhere we ever suggested to "disable" the antivirus. Countless of times on our forum, when somebody asked, we ALWAYS said to:

- Add the whole Addon Manager folder to the antivirus EXCLUSIONS, no need to disable it.

- Run the FSDT Live Update again, to be sure the files mistakenly blocked by the bugged antivirus that cannot recognize the specific industry standard digital signature we put in all our executables to prevent false positives will hopefully not blocked again, which shouldn't happen if you add the folder to the A/V exclusions and the A/V is not so bugged to not respect its own Exclusions.

In general, when something doesn't work, it's almost invariably the antivirus. And no, it's not an "FSDT problem": for a short while, Windows Defender was blocking MSFS 2020, causing a CTD at start. This was of course fixed by Microsoft quickly, but it happened.

Edited December 21, 20205 yr by virtuali

I have norton and had done what virtuali suggested above.  No issues for me.