I take it that since I have asked twice with no reply, there is no way to recover from the error, that the previous files are now hopelessly corrupt, and that I may as well delete them because I'll never get them right again.
Is that correct?
I've read the threads you referenced, but still don't see this issue addressed: how can driver problems cause permanent file corruption without that file being loaded?
While I understand the issues regarding textures being misapplied -- e.g.,, to the sky instead of to the object (and I find it really odd that this wasn't addressed a long time ago -- "Change the sky texture? Are you sure you want to do that?" -- God knows, there are enough other little nags like that, what's one more?) this is not that issue. This texture was already in place, and I did not attempt to apply a new one. Rather, it spontaneously corrupted itself, not just for that instance, but for every future instance of application whether taken from the palette or the original library, and meanwhile appearing correctly on the palette.
Indeed, I was "inside the house". when the sky/ground evil happened. I was "in another room" when the wall corruption occurred. Only when I looked through a window, did I notice that the sky had gone nuts.Only when I entered the first room did I see that the wallpaper had gone crazy.
I read LMC's explanation about video drivers, and understand it. I don't agree with his reasoning because video mistakes can persist for a long time indeed and that wouldn't be acceptable to anyone, but the occasion of redrawing the whole screen, (the equivalent of getting a video "A" frame) however that comes about, seems like it ought to sort the problem he describes.
It doesn't.
It appears instead that there is a mistake which can occur in the rendering, and which once made, is thereafter written in stone: the wall/sky/ground/whatever will now forever reiterate that same rendering mistake and never get it right, even by accident. Rebooting or resetting ought to clear it, but does not. Murphy doesn't merely run riot, he stages a coup d'etat and has himself elected dictator for life.
This is why I believe that something beyond the driver must be at the root of this issue.
I have lowered the graphics acceleration and essentially started over. Two weeks down the drain. I do hope this will at least not happen again.