November 28, 2025Nov 28 I can't even remember how many months it has been since Asobo broke it in one of the updates so can't believe it is "still" pink but sure enough, just passed EHAM at FL350 and the whole airport looked like it was painted by the Easter Bunny. I am guessing this is not an issue in 2024? I am fine with Asobo not updating 2020, I am more than content with present state and plan on migrating post SU4 (although I still really want ChasePlane but can't wait for them to get back from fishing 😉 ) but please don't break 2020... AI LOD is a regression in 2020, EHAM wasn't always pink in 2020, Querying an Airport via SDK standards can result in CTD with erroneous data, there is just no reason for things to be breaking in what was a rock solid and stable sim... I'm like the guy at the filling station who doesn't want the attendant to clean his windshield because it's already clean and they will just leave streaks. Please don't touch LOL. OK, /VentOff 🙂 Have a Wonderful Day -Paul Solk
November 29, 2025Nov 29 Is it only pink when you fly high above it? My quick circuits are at 6000 feet, and I have not experienced any "pink" issues at the airport. Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
November 29, 2025Nov 29 This issue may be due to the missing third line in the "texture.cfg" file for EHAM. The following is from a content creator on another platform pertaining to Cairo but may also be the case for your EHAM: Viktoren69 The issue is caused by Asobo/MS. Easy solution taken from the forum https://forums.flightsimulator.com/t/pink-textures-so-far-eham-only-default-asobo-scenery/729894/26 The problem is caused by a missing line in the “texture.cfg” file located in the airport folders (EHAM and HECA). path example: LocalCache\Packages\Official\OneStore\Asobo-airport-heca-cairo\scenery\cairo The file has only two lines, but it should have three, just like other Asobo airports. All you need to do is add the missing line: fallback.3=Scenery\modellib-texture\ModelLib The whole file should look like this: [fltsim] fallback.1=scenery\cairo\texture fallback.2=Asobo_Buildings\Texture fallback.3=Scenery\modellib-texture\ModelLib
November 29, 2025Nov 29 Ah, so Paul is talking about the MS/Asobo version of EHAM? I had assumed that he was talking about the FlyTampa version Edited November 29, 2025Nov 29 by Christopher Low Christopher Low AMD Ryzen 7 9800X3D CPU / 64GB DDR5-6000 RAM / 12GB Nvidia RTX 4070 Super GPU / Gigabyte X870E Aorus Elite Wifi 7 / 1+2TB Samsung Evo Plus M2 Nvme UK2000 Beta Tester
November 29, 2025Nov 29 maybe this can fix it https://flightsim.to/file/96557/eham-pink-textures-fix-after-su16 I9-14900K, Gigabyte B760 Aorus Elite AX, RTX 4080, 32 ram.1 tb nvme M.2 SSD, MSFS 2020 on 2 tb nvme m.2 SSD
November 29, 2025Nov 29 Author 2 hours ago, Christopher Low said: Ah, so Paul is talking about the MS/Asobo version of EHAM? I had assumed that he was talking about the FlyTampa version Yes, this is the default version that Asobo made pink after one of the SU's but I am going to try the fixes from @hansb57 and @GraMcN. thank you everyone!! Have a Wonderful Day -Paul Solk
Create an account or sign in to comment