MSFS Las Vegas 1.3.2 misaligned localizers

[Croniac]

Hi All,
Prior to the most recent update from MS, this was not an issue. However today I find that the localizers for both runways 26 are north of the runway by about 1000 feet.

If I uninstall the FlyTampa Las Vegas package (purchased via MS Marketplace), then everything is fine. Reinstall FlyTampa and the bad localizers return.

I sure hope you can fix this soon, I fly in and out of vegas a lot and hate having this addon disabled.

Thanks.

[Er!k]

Happens with more sceneries, see https://forums.flightsimulator.com/t/il ... -iv/405441

[Croniac]

Ok, but if the base game ILS is correct, and the add-on is not, that seems to point to the add-on needing an update.

I totally understand that ASOBO may have changed something about the world. And if they did, the add-on needs a patch.

[Er!k]

Other developers already solved the issue, or a fix is underway. Hope @emilios[flytampa] will take a look!

[Croniac]

The lack of feedback from FlyTampa on this is disappointing.

[Er!k]

Yes indeed... I hope Emilios will read it and provide a fix ASAP. I have sent a mail to support...

[emilios[flytampa]]

It is not an easy fix because of the terrain editing we have done in the area, but looking into it

[davidal]

Hello,
Is there any progress in fixing this problem?
Rgds,
Daniel

Edit:

I installed KLAS v1.4 hoping that this will fix the problem but it doesn't. In addition, attempting to load KLAS 1.4 crashes it EKCH is also installed.

[emilios[flytampa]]

Part of the problem is not-fixable from our end. Custom ILS data are not being read correctly, so we will have to wait for MS/Asobo patch to fix it.
In the upcoming update of KLAS, the glideslope will be fixed to bring you in more accurately, but the misaligned localizer will likely remain. On the flip-side of that, we could also keep the default/stock ILS, which works ok, but this way the glideslope will bring you a couple hundred ft lower.

If both CPH and Vegas are up to date, there should be no CTD issues. Can you make sure both are updated, and also just before you startup the sim, delete your 'content.xml' (make a backup first).