Howdy,Recently downloaded Gyula Kalcs

None of the textures he modified have autogen files associated with them by default.He did create autogen files for one texture set, "Evergreen Conifer Forest And Field" for Region B. If you want to remove them for testing purposes look in ...\FS9\Scenery\World\Texture for 025b2an1.agn through 025b2an7.agnCan you post a screenshot showing us what you see?regards,Joe

Hey Joe,Yes, had already decided to remove the *25b* autogen in order to test. It solves some of the problem, however the "footprints"are still evident (just not as prolific as when the *25b*.agn were active).Refer the attached screenshot ...

Can you give more of a close up? With lat/lon showing (Shift+Z)?What happens if you move the autogen slider all the way to the left?regards,Joe

S041 24 54.2042; E172 06 44.6683Autogen: Extremely Dense (in fact, using TERRAIN_AUTOGEN_DENSITY=30 tweak, but "footprints" still show at default DENSITY=5); Scenery Complexity: Extremely Dense

This is an issue with the landclass file and has nothing to do with the texture set.I tested using the freeware Red Baron mesh and lanclass, using the default textures and I also have that white spot in the exact same place.I narrowed that ground texture down to 019b2su7.bmp.FWIW, here is a screenshot of that texture, as seen in ImageTool, with FS9 open in the background. I have added a few arrows showing pixels common between FS and the texture. Note the lack of that big white spot.This leads me to believe the landclass file has a glitch in it calling what looks like a snow texture for those pixels.Long story, short, there is nothing I am aware of that we can do to change this, short of not using the landclass.I suppose one could de-compile the lanclass file and find the offending entry and change it. I do not know how to do this, and if you wanted to learn you might post this in the scenery design forum or here - http://www.fsdeveloper.com/ .Hope this helps.regards,Joe

Hi Joe,Many, many thanks for the exhaustive and thorough testing of my little problem.Yes, I too had come to a similar conclusion the overlying LandClass was the "culprit" in this instance. I'll contact Christian (the simming community in NZ is very close) and see what he has to suggest.Once again, thanks for the time and effort tracking this down.

FWIW: I run GE Pro and have no such artifacts...FWIW #2: Google Earth is getting pretty good, too, these days!