Louisville does no longer work in P3D5

[kmanning]

Just do what I said, don't change anything. That is:

- use the Windows CONTROL PANEL to uninstall

- remove any leftover folders as I've explained

- do the rest exactly as I've said.

When I said "the FSDT software", I mean the whole Couatl engine that runs BOTH GSX and KSDF. If it's not working for ANY reason, BOTH won't work.

If you have other FSDT sceneries installed and GSX and they work, the problem is something else entirely, as you are still missing something specific to KSDF, which again, I verified it's installed properly when doing a full Uninstall/Reinstall in the way I indicated.

And as I've said in my previous post, adding a diagnostic log would help.

Okay. I'll try it using the Control Panel. I would add a diagnostic log but I don't know how to do that and where the log is located. What is the exact file name? I figured that post was directed to sticky1202 because you replied to his post.

Ken.

[sticky1202]

Where do I find the startup log?

Jim

[virtuali]

You enable logging in the troubleshooting section of the settings page.

[theScotsman87]

Hi all

I have been keeping up with this topic and have followed the step-by-step posted on the first page of this tread.

I am still unable to see the airport load-in after following the guidelines.

GSX is active

Addon manager is active

attached is .log file renamed as a .txt file for you convenience

many thanks for your continued support.
This certainly seems to be an unusual problem. hopefully this log file help somewhat.


=====================
Further edit
=====================

I also have FS2024 installed on same drive with GSXpro and KSDF for FS2024 also installed.

[theScotsman87]

here is screen shot

[kmanning]

I hope I did this correctly. Here's the log file.

Ken.

[kmanning]

Uninstalling the KSDF using the Control Panel and reinstalling made no difference. The same problem exist. I want to add that I did receive one error during the installation and here's what it said:


[Delete file

C:\Users\Admin\AppData\Local\Temp\vcredist_x64.exe failed

Microsoft Visual C++ 2015-2019 Redistributable (x86) - 14.27.29016

Setup Failed

One or more issues caused the setup to fail. Please fix the issues and then retry setup.
For more information see the log file.

0x80070666 - Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Program on the Control Panel.]


I did click OK when I was prompted and created a new file. I guess it probably did this because I have a later version.


Ken.

[sticky1202]

Hope this is the correct log...I had to change the ".log" to ".txt" to upload it here.

Jim

[gevan]

After following "your essential and perfect guide" on how to install your scenery (even though I already had other FSDT scenery installed in P3Dv4, v5, and MSFS2020), I proceeded to completely uninstall it and download the scenery installer again, then executed it and waited for everything to update so it would "work correctly" in our simulator...

After a few minutes of this complex procedure, which we're all incapable of performing because "we're probably doing it wrong"—because we're apparently four years old—I started my P3Dv4 simulator with Windows 10 Extended Support (because yes, Microsoft provides extended support for those of us who can't migrate to their fantastic Windows 11), selected the default aircraft (F-22 Raptor), and navigated to KSDF airport to verify that everything was working correctly and...

¡Oh, surprise!, the problem persists and wasn't solved. Speechless.

I proceeded to navigate to another FSDT airport I have: Memphis (KMEM), and magically, this scenery worked... wow, incredible. I have no words.

I'm uploading another log file with its respective screenshots of the scenery, hoping that now you can see with your own eyes, Umberto, that "we have a problem here," and it seems you're taking us for fools, whether it's you, your colleagues at the company, or all of yours together.

This will be my last log file uploaded about this scenery. I don't intend to waste any more time uploading evidence of such a disastrous way of providing a solution to a bug caused by FSDT with your rushed "updates" without prior testing.

[Blasb]

Yeah no success for me either! Can you guys at FSdreamteam please fix this issue!

[virtuali]

Thanks to those who posted the log (that's why I always ask for it), I THINK to have understood the problem: check the name of this folder:

c:\Program Files (x86)\Addon Manager\couatl\KSDF

Is the folder name "KSDF" ( upper-case, correct ), or "ksdf" ( wrong ) ? If the name in your installation is "ksdf", rename the folder to "KSDF" OR just remove it and run an update CHECK again, so it will be restored correctly.

The issue is, it's a bug of the KSDF Full installer that dates 2023 hasn't changed ever since, it can only happen after a complete uninstall not just of the scenery itself, but even the entire Addon Manager folder, and it's there since 2023 so no, it's not a "rushed" or "untested" update, it's something that has been there for more than 2 years, but couldn't possibly notice until you made a complete reinstall from scratch of everything.

We'll obviously fix the full installer, but the above solution should work.

[sticky1202]

Congratulations!! Problem fixed!!

Jim

[kmanning]

Thanks so much Umberto,

The scenery problem is fixed.

[Blasb]

Works for me now as well!