Most people who've cracked open a Poser file know this, but I thought I'd rehash it since SOME people obviously DON'T know this. Poser files sometimes mention pathing information in them (usually, in fact). CR2s mention figureResFile, lights and props mention object paths sometimes, and anything with a texture map applied has a path. Object references should be relative to the Poser 4 installation directory, and this is where Poser looks for them and where it stores this information in a PZ3 file. For instance, a character's geometry might be in: :Runtime:Geometries:yourFigures:yourPoserCharacter.obj Textures, on the other hand, Poser looks for first in the Textures folder. This means that paths for textures, and only for textures should begin relative to the Textures folder. A proper texture path might look like this: :myTextures:myReflectionMaps:backgroundReflection.jpg A path beginning with :Runtime will work, but is not the most proper way to do this. Any path with a 'C:Program FilesMetaCreationsPoser 4...' in the beginning is just plain wrong, and is just as wrong if it says 'Curious Labs' instead of 'MetaCreations', and not ready for distribution. Likewise, any absolute Mac path, like 'Hard Drive:Applications:Poser 4:...' is also wrong (and worse, in a way, because people have different driver names more often on a Mac, whereas most people on a PC have Poser on C:, in the Program Files directory, and usually in the MetaCreations or Curious Labs subfolder. ANY poser file you buy with absolute paths should be mentioned to the seller and corrected. Any Free Stuff with this sort of path should probably also be mentioned to the owner or distributor, though it's free, so you're still getting your money's worth. Otimally, ALL texture paths should be made relative to the :Runtime:Textures folder, maning you should not see ':Runtime:Textures' in the path, because Poser already assumes that. Further, any textures should be in the :Runtime:Textures folder (although they can certainly be further down and, in fact, this is a good idea). As a further note, Macintosh files have a 32 character limit on filename and a 64 character limit on a single path string, so paths should be kept shorter than this for Mac compatibility. The closer you are to these standards, the higher quality your product is. The further you stray, the lower the quality. If, for some unexplainable reason, you're forced to break away from these standards, then whoever or whatever is responsible for this is forcing you to produce a shoddier item, and should not be allowed to get away with it. If you've purchased a product that breaks from these standards anywhere, I wholly urge you to contact the creator and/or marketplace responsible and voice dissatisfaction with this. Some people may be unaware of this, as has recently come to my attention, so I figured it was important to explain it. Tips and Tricks: Something else you might consider trying when distributing files (I only recently discovered this, so mine don't do it yet). The BUM file problem has been around for ages. Poser 4 uses BUM format files for bumpmaps, and these are huge, uncompressed files. PPP and P5 avoid this problem by creating a BUM on the fly as needed, but will still, as far as I kow, accept a BUM file. The common practice is to include the original bumpmap Poser generated its BUM from and to send this along so the purchaser or downloader can recreate their own BUM files. Al alternate idea: A BUM file is actually only a specialised 24-bit big-endian (Windows Byteorder) BMP file. It's a full-colour Windows Bitmap. If you change the extension, you can crack it open in any image editor I know of, even MS Paint. this also means that you can certainly, with some small degradation, convert it to a JPEG file and distribute it with instructions to open it, convert it back to a BMP, and then rename the extension to BUM.