Bryce does not use the graphics card to render. It only uses the graphics card to draw the wireframes (and OpenGL shapes, if you're using that mode). As far as I know, Bryce is not multiprocessor-aware. It is definitely not multiP-aware on a Mac, and I don't think it is on Windoze either. This means that it won't take advantage of your dual-P3 setup. Depending on your version of Windows, however, the OS is multiP-aware, so you could render in Bryce and then use another application at the same time without really reducing render time in Bryce. Those of us with single-processor setups have learned that trying to render in Bryce while surfing the web is a painful experience. Bryce renders slower than most other 3D apps. That's a fact of life. This is because it generates much more interesting textures and terrain shapes than other 3D apps. That's the trade-off. Supposedly, rendering will be sped up significantly in Bryce 5, but we have yet to see any evidence of this. Here are some things you can do to speed up rendering: - use fewer lights. Lights are a killer to rendering time. - make sure you have enough RAM. having more RAM doesn't really speed up rendering time, but having too little will slow rendering way down, because of the inefficiencies associated with virtual memory. For small renders, 128 megs is enough: for larger scene files you'll want at least 192 to be comfortable, and more than 256 if you can get it. - Imported meshes (.obj, .dxf, .3ds files) tend to dramatically slow Bryce down, especially if they have a lot of vertexes/polygons - Reflection, transparency, refraction, and bump are real time-killers. If you're concerned about render time, then limit the use of the first 3, and pay careful attention to your bump heights - more bump height = slower renders. - Volumetric materials are the #1 killer for rendering time. I'd suggest not using volumetric materials until you really know what you're doing, because they're not intuitive, it's hard to get good results with them, and they absolutely destroy render times. This goes for the Volumetric World setting in the sky lab too. That said, if you use these effects you can get some really cool renders. They just take forever. - If you're playing around in the Deep Texture editor, there are lots of things you can do to make textures render faster... most of them have to do with reducing number of octaves & frequency, and avoiding some of the costlier noise types, like Vortex Noise and some of the Voranoi noises. One thing about Bryce: most of the really good pictures running around on this site took many hours to render. Bryce is not fast. 12-hour renders are not uncommon, and I've personally had some renders that took more than 30 hours for a 800x600 still image. Animations take even longer (although usually you use a much lower image size and render quality for animations) --flick