ToolmakerSteve.... The people over at DAZ created models that really made poser something special. They used the wavefront objects with all the library structures that poser expected, textures, bumpmaps etc. CL knows victoria and must love what she's done for them. Take your Victoria and try to render her in firefly. What happens? Your bumpmaps are nowhere. You have to either render in the P4 engine or go about playing with converting your bumpmaps and go play in the materials room. Being that DAZ followed the poser conventions, why would CL not support a native import for any model using bumpmaps that were in the Runtime library structure? Knowing that bumpmaps are part of any good model - why on gods green earth would poser not provide a import for models (that use bumpmaps) that made them P5 ready. I didn't see anywhere that bumpmap support (as it was) was being dropped. I was taken by surprise. Its kind of silly don't you think? To provide a method of connecting to your p4 library but drop the ball on the bumpmaps? This would be the same as an upgrade to Microsoft Access that allowed you to read your tables but made you manually convert your existing queries or MS Word that provides new fonts but expects you to convert your old ones. Imagine having a word doc that you worked on for a client proposal that had 15 different fonts in it, scattered thoughout the document - you upgrade and then find out that the doc, when imported, is changed all to courier.