BTW, your crazy render 90 hour time is definitely not normal. I've done scenes with literally hundreds of lights illuminating terrains and imported objects, and had a lesser time with a much lesser machine than yours. You need to check carefully if there is anything in your scene that is causing the render engine to choke (doubled up transparent objects, etc), or if the machine is having to write to disk for virtual memory. Although 320mb of real memory is a nice amount, if your scene file is big and you have other applications open at the same time, then you could easily run out of RAM. If the processor has to use the hard disk as its working space, then everything will take a long time - Bryce renders will take forever. If your scene file is small, and the render still takes ages after a fresh reboot (no other programs or files open), then you need to look at your scene carefully. Check what materials you have set, and try deleting certain items to see if things speed up. There's nothing broken on Bryce's render engine, it just doesn't have a low quality 'setting' like Max or Poser. Bryce renders at good quality, very good quality and extremely good quality. That's nature of a true ray trace render engine. Bryce has been like this since the very early days. Users enjoyed ray tracing, with proper transparency, reflection and refraction before Max even had an incomplete ray trace third-party plugin written for it to do it. I don't mind if they add a non raytrace engine in the next version to provide a speedy option (it's highly unlikely though, due to the nature of the program); but I'd much rather they add Renderosity for even greater realism. I'll just get a faster processor!