Got it. I saved as per the instructions, but when I tried opening the .pz3 file, the view screen was all white and the menu controls we disabled. I was able to import the scene however. I had to reset the lights and the camera, but at least I didn't lose 3 hours of work. This is the first thing that really p*sses me off. I'm a programmer, and to release something with this kind of warning because you expect the problem to happen is very unprofessional. I know we all wanted the patch A.S.A.P, but I'd rather they didn't include the "fix" that caused this problem. We're in effect, alpha testing for them. I get paid for this kind of work, my rate is $50 an hour. Are we going to get compensated? CL owes us for this one. Kupa, you listening? How about making the Millenium figures fully P5 complient? Or changing the registration system? I was pretty happy with P5 (still am, really), but this kind of thing gets in my craw. I love all the new features, and everything worked for me BEFORE I installed the fix. The problem happens with using displacement maps in production firefly for me. If I do a production render, even with raytracing on, and don't use displacement maps. I don't get the error. The render turned out pretty good, and I'm posting it. It would have been better with the maps. P4 renders work just fine. When you send your error code to CL, be sure to inlude your ops system and hardware configuration. It may be specific to one of these. Rant over. I won't even talk about how dorky Don is.