Cool. One thing I forgot to mention is that there are certain workarounds for it, at least in Vue. Since the .mtl file is actually a simple text file, you can use a text editior to manually alter the paths, and if Vue knows specifically where to search, it will find them. That can be fairly tedious though. What I do, is I have a folder in which I place ALL my textures that I use for everything Poser-related, and then my .obj exports are exported to there, so there is never any chance for Vue to fail to find a texture. Of course, you download Poser characters, or whatever, and initially the textures D have to be somewhere specific as determined by any Read Me's, but if you move the texture to a new location, reload it on to the Poser character, and then re-save it, Poser will always search the new path for that texture. I have next to nothing in my Poser directory, as far as textures go, actually. It took a good while for me to set it up that way, but now whenever I get something new, it's only a matter of a few minutes' additional work, and like I said, there will be no chance that Vue or Bryce will fail to find it. Newbie-ness excused. :) Render on! --Mike