Here's a way to test this. Create a small scene and do a full render on it (use premium effect AA -- I haven't checked other rendering modes. Now lets say the render took 5 minutes. Use some sort of timer and start the render, then click the screen to stop it after a minute (20 - 25 % of the full render time seems to expose the problem.) Save the scene and exit Bryce. Restart Bryce, load the same scene and resume rendering for another minute. Repeat the save/exit/resume until the scene finishes. If you don't exit Bryce after the save, you won't see the problem. Add up the total render time -- you may be surprised how much time the resume adds to the render (don't count the load/save time, just the actual rendering.) You may have to adjust the times you render to see this bug, since the cpu/video card/memory configurations wil differ. But it appears to me that if you stop the render on the last pass, when you reload Bryce and resume, it finishes the last pass and then starts another. The only way to finish is to let the computer run until that last pass completes without interruption. Now this isn't a problem if you leave your computer on and let the render finish (or resume and let it finish.) But imagine a complex scene that takes say, ten hours to render the last pass. if you can't leave the computer running for at least ten hours, you can't finish the scene.