Rather than trying to find which package in the community folder is causing the problem by testing each package one-by-one, follow the “by halves” method:
- Create two new, temporary folders. The names are unimportant, so lets’ call them “CM-Temp” & “CM-Bad”
- Move everything from your community folder into CM-Temp
- Start MSFS in normal (not safe) mode & confirm that the airport you show in your OP looks OK. Exit MSFS
- Move half your community folder packages from CM-Temp back into the community folder.
- Start MSFS. Does the airport still look OK?
If yes, Exit MSFS, then go back to step 4
If no, move the packages you just moved out of the community folder & into CM-BAD. Go to step 4
At some point, you will have no more packages remaining in CM-Temp, some in the community folder that do not affect the airport visuals, and some in CM-Bad, of which at least one package is suspect.
Move all the packages from CM-BAD into the now empty CM-Temp folder.
Repeat steps step 4 & 5
Eventually, you’ll have one or more packages that, every time you move them into the community folder, causes the blue/white checkerboard effect. You might want to contact the creator(s) of that package(s) to see if they have any updates or fixes available.
Hope this helps!