sory but it is not the size of picture only that sometime is a problem... i had two packages from the same merchant... wfor two similar models (mayadolland animedoll. hint :) both texture package had roughly same size of about 2500x2500 or so. one constantly locked when rendered, the other wasn't. when i looked back in m runtime folder, i discovered that one of the texure package was very lightly compressed and the other was better compressed (yet no quality loss) in jpg. for a 2500x2500 imagesize, one of the package displayed textures of about 400kb a piece, and the other somethign like 3.5mb a piece. guess which one was locking my poser ? :) so just recompressed the textures at same size but better algorythme (used jpg new export filter from pixia 2.8, with better quality/size control.. took half quality/half size compromis esettign and checked then after ward on a sample patch of the original texture if any change could be noticable at naked eye and it wasn't :) so one advice would be: compress your texturesz wisely (not too much, but not too loose) and well, yes for parts that are not bound to be used in closeup render, may not need to make them 4000x4000... you can WORK with such file at home when making your textures, but maybe for the end user, unless he has poser 5, 1gb ram and such, some package may b e unusable without serious fix.. and usually someone bought somethign because he wnted not to do it himself, so most of the time he will be upset if he has to fix it. ps: it is no flame toward the merchant whom package i spoke of... in fact, i guess the textures were able to be sued with p5 or better computer than mine so it is my fault; yet well, many people do not have mosnter computer. mine is a gaming one and already decently goes with nowadays games. I would nto expect something like p4 to requires as much horsepower than latest games...