DPI stands for dots per inch. I could be wrong, but as I understand it, dpi is only relevant to printing. When you print a picture on paper, the printer checks the dpi setting to see how big the picture should be. A 720 pixel wide picture with a dpi setting of 72 would be printed accross 10 inches of paper for example. The setting has absolutely no effect on how big the picture will look on your screen or how much memory it will use, since both of those things depend on pixels and your picture is still 720 pixels wide. Changing the pixel dimensions of you picture is the only thing that will change how much memory is used. The quality setting will affect the hard drive footprint of the image (and the image's visual quality) but not how much memory Poser uses because, as anxcon says, Poser has to uncompress it (basically turn it into a bitmap) anyhow. I don't know whether it's really true or just a Poser urban myth, but it's said that Poser still uses the system used by a lot of older 3D apps, where textures can only be in power of 2 dimensions (256, 512, 1024, 2048 etc) so any texture between those dimensions gets treated as though it were the next size up - eg. a 257 by 10 texture would be treated as 512 by 512 because that's the smallest power of 2 square that can accomodate it. If that's true, then you'll always get the most bang for your buck by making sure the longest side of your picture is a power of 2.

View Ajax's Gallery - View Ajax's Freestuff - View Ajax's Store - Send Ajax a message