AndyM
-
Posts
151 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Downloads
Posts posted by AndyM
-
-
I'm not seeing this. Maybe worth clearing out the cache and scenery indexes
-
Is your IniManager up to date? Maybe uninstalling and installing the IniManager from the latest executable. This is what I see ...
-
On 1/2/2026 at 9:06 PM, jeffc said:
I was there last week and I can tell you most certainly even at terminal 5b as well that is not the logo it is the new one with no serif font
Ah, okay, the pictures I have are from 2023, so they have obviously changed since then.
-
Just checked and it seems fine on my .7 version. Logo seems fine to me also.
-
Probably because the scenery was designed for 2020, and I don't think Ini are putting much support in to 2020 products anymore.
-
Yes, I'm also seeing this.
-
Thanks for the info. Do you have a link to the post please? I don't think it's a recent driver issue. It happened on my 3090 with drivers 566.36 from last December. I may try an earlier drver when I get time.
-
Here is Stand 564 with just the TLOD settings changed from 200 to 400. I only have the 777 and EGLL installed. My PC is basically new, 9950X3D with 5080 FE and 64GB ram. So something is not right, not sure if it's MSFS LOD system or something in the scenery files not loading properly on the higher TLOD settings.
-
1
-
-
I don't have many 2024 airports, but I couldn't get it to happen at Flightbeams Portland v2, so not sure what the issue is. I've not seen anyone else report this sort of issue though, maybe most people are at TLOD 200?
-
What is your TLOD? I have this problem with a TLOD at 400, I reduced it to 200 and it's gone. When I first spawn in, they are not there, then if I switch quickly between FREE CAM and RESUME a number of times I get the glitches. Someone suggested that the graphics card might be on it's way out. I've just purchased a brand new 5080 and it's the same. Not sure if it's a problem with some airports and the way the developer had built it, or a MSFS issue.
Graphic / Texture glitches in 2024 - Microsoft Flight Simulator (2020/2024) - The AVSIM Community
-
46 minutes ago, pbrad74 said:
That would be a shame because so many people are still using 2020 because of the problems in 2024.
Me included.
-
1
-
-
I'm guessing that support for 2020 products going forward is going to be limited to none, as it is doesn't make financial sense to them. I have a bunch of 2020 addons, and don't want to now spend another small fortune on 2024 addons. Going forward I'm not buying any more full priced 2020/2024 addons, only ones that have an upgrade price, or wait for the sales if I really want it.
-
On 4/23/2025 at 10:46 AM, Eddie said:
Hello,
Please try clearing your scenery indexes:
To do that locate your folder by following the path below:
MSFS 2020MSFS 2024
Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.
Let me know if this resolves your issue.Any news from the Devs on this issue?
-
1
-
-
I'm also seeing this.
-
6 hours ago, IniSteve said:
Yes. Despite the guidnace from FSDT we have found that GSX is not always respecting the filter for 2020 vs 2024 in cfg files.
Until it's fixed on their end, you'll need to switch profiles per sim if using the same airport.The problem I had was that there appeard to be 2 Ini GSX files for 2020, and a third for 2024 in the GSX folder. Uninstalling the 2020 one through the Ini Manager still left one in there which gave me the conflict.
-
Although I uninstalled the 2020 Ini GSX profile through the Ini Manager, there was still another Ini profile in the GSX folder. I manually deleted it and it seems fine now. I just have to keep uninstalling and reinstalling the Ini profiles in 2020 and 2024 depending on what sim I'm using now though, as I still use 2020 around 90% of the time.
-
Not sure what is going on here, I have the IniBuilds GSX profile installed (I have also deleted and reinstalled it to see if that fixes it) and the VDGS text isn't being displayed correctly. I don't have the GSX profile installed in 2020 either. Any ideas?
-
A few things to try. Firstly, have you disabled/removed the default Asobo EGLL? You could try deleting the Scenery Indexes, these will get rebuilt the next time MSFS loads. The other thing is regarding GSX, have you selected 'Exclude 3rdparty' in the GSX options?
-
I also noticed a distinct difference in the ground textures in the area, not sure if they are supposed to be like that, or another problem?
-
1 hour ago, Eddie said:
Hello,
Please try clearing your scenery indexes.
To do that locate your folder by following the path below:
MSFS 2020MSFS 2024
Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.Let me know if this resolves your issue 🙂
Didn't work unfortunately, still there.
-
I'm also seeing it, photogrammetry is ON.
-
It loads no problem for me, certainly no longer than any other 3rd party airport.
-
I am assuming that you are using MSFS 2024 with the IniBuilds version of EGLL 2024? If so, this is done In Marketplace, select My Library, then search for EGLL, and then select the default EGLL and then disable it.
How to enable and disable content in the simulator – Microsoft Flight Simulator Support
-
I didn't think there were static aircraft in the scenery, you have probably got traffic enabled in the MSFS options.
-
1
-
Pink cars - EGLL
in Support
Posted
I have all the updates, but they are all streamed. I've also disabled the stock airports that would clash with the ini addons. I use Addon Linker and only load the airports that I'm curently using for that particular flight. I also had the premium 2020 so have that content available, but not downloaded.
So, the only things that are physically downloaded and in my community folder when I'm playing are the airports I will be using for a particular flight, the aircraft that I will be flying, Justflight Fstraffic and GSX Pro.