Hi, I use MDX & VS 2008 (C#), I have to display several large textures (as geographic maps, I'm creating a program like NASA world wind or google earth), my textures are large and it is my main problem, for instance I have several 6000x6000 textures, and as you know D3D cannot load these large textures (I use Loadfromfile and it gives me error on these big files), so I It is the code I use to divide my large texture into several smaller textures: for (int iLoop = 0; iLoop < areaList.Count; iLoop++) { Rectangle rect = (Rectangle)areaList[iLoop];//an array of RECTs previously filled string fileName = _filename + (iLoop).ToString() + ".BMP"; Bitmap newBmp = new Bitmap(rect.Width, rect.Height,System.Drawing.Imaging.PixelFormat.Format24bppRgb); Graphics newBmpGraphics = Graphics.FromImage(newBmp); newBmpGraphics.DrawImage(inputImg, new Rectangle(0, 0, rect.Width, rect.Height), rect, GraphicsUnit.Pixel); newBmpGraphics.Save(); newBmp.Save(fileName, System.Drawing.Imaging.ImageFormat.Bmp); } but sometimes this codes gives me error (Out of memory), so I think I cannot count on this algorithm, perhaps I should read all pixels and save them manually to smaller parts. Can I load only a specific part of these large textures into D3D memory? Can I use D3D to divide my large textures (BMP or JPEG) into smaller textures? is there any samples? thanks

thanks Steve, as I'll have several big textures, dividing them to small parts will end to several hundred textures (for instance I'll have 1000 500x500 BMP files), and it seems that loading these 1000 files into D3D memory (i.e. loading them all using TextureLoader.FromFile) will not be efficient (I think D3D cannot store so many textures at once), therefore I've decided to load only textures that I need in each scene, I think based on the distance between viewer & globe I won't need more than 10 textures at each scene, so is it logical to load( TextureLoader.FromFile)/unload (Texture = null) each time my scene changes?
I think loading/unloading fewer than 10 textures is not a serious problem for D3D, and I suppose it won't cause much FPS loss (of course I will create my small BMPs at app init and will load/unload them in runtime)

thanks