Max texture size limits the size of the texture map sent to the render engine. It probably takes a bit more cpu than if you loaded an already resized texture, but it takes much less than feeding in a 4000 px texture. (You know, "Loading Textures") All those different sized textures will be taking up drive space too. It's going to take a lot longer to load the texture up in an image editor and resave it at a reduced resolution. Setting up a partition isn't going to do any thing for speed that defragmenting wouldn't do. It might would keep things organized though and you could quickly defrag that partition. "Turning on texture filtering will give you awful visible seams..." It depends on your texture and figure. Some times it helps nasty seams look better. I find that if the texture is cut too close the the edge of the map it will make the seam worse. If the texture extends beyond the template a bit it usually makes the seam smoother. (Hint: Flood fill the white part of the V3 maps with a nice skin tone. ) On the V3 body map DAZ (Who knows why!) decided to trace all the way around the texture with a dark outline. That outline has gotta go! flood fill it with a color closer to the rest of the map. That's why V3's seams look horrible. Nerd3D