   Bizarre texture artifacts?
  Here's a shot from my terrain editor (DX8 Fixed function, MFC):It shows 3 different textures being used. The green and grey pebbly textures work as expected, but the 3rd texture is being very strange. You can see that at the bottom of the image, it's rendered OK, but as you move upwards purple lines start to appear. By the top right, the texture has entirely been replaced by that unknown pattern.As I move the camera about, the way this effect appears changes, but the other textures never get this problem.What could be the reason? I used this code and resources maybe 3 years back and did not get any issues. Can it really be an issue with the texture? I can post the texture files if it's helpful.Here's a more extreme example, note the purple/black lines get more and more extreme, while other textures are not suffering:EDIT: here is the same map actually used in-game. The game does not use the same rendering engine as the editor, but it is using the same technologies and a similar method[Edited by - d000hg on September 9, 2008 2:22:52 AM]
  It looks like the mipmaps are messed up how are you loading/creating them? If possible disable mipmaps and always use the top-level texture and see if the effect goes away. If you're loading a DXT file with mipmaps then open it up and check that they've been updated correctly from the last time you exported it.   ;  You may also find that enabling anisotropic filtering (and setting D3DSAMP_MAXANISOTROPY to an appropriate value) will help, on cards that support it.See http://msdn.microsoft.com/en-us/library/bb172264(VS.85).aspx for details.   ;  I was using DDS files for my textures; it turned out I also had BMP versions. I tried them and the problem went away! So somehow the DDS mip-map data must have been broken, which is weird since they used to be fine. Since I created the DDS using the tool that came with the DX8.1 SDK, about 3 years ago, is it possible that modern cards don't use DDS in quite the same way?   ;  IIRC the nVidia DDS viewer lets you see the mipmaps (there's a mildly obscure menu option and/or key binding for it). I'd see if you can peek inside the file first. Since it's only happening for one texture it seems likely that it's a data problem rather than a code problem.If the DDS file looks ok, then perhaps see if it differs from the other (working) DDS files in any way - dimensions, colour depth or colour format might cause it to trip some code bug that doesn't affect your other textures.   