My experience: I've gone as high as 95 million polys on my dual 1 gig. Still could have gone higher I'm sure I just didn't need to. I think also it has to do with the number of objects plus the poly count before you have to think about other rendering options. Djesers right though, read on. My general rule of thumb about these things in any 3d package is to remeber how 3d programs deal with materials, which can be the problem in vue (which doesn't have a poly limitation that I know of like other programs). Procedural materials = Processor cycles Bit Map Materials = Ram. If you are using a bunch of procedural materials that are slowing your renders consider exporting some of them as bit maps and re-applying them to shift over to ram. If you think you're choking on ram use more procedurals. The point is its not just polys you have to concern yourself with. Save all of your scene materials (named properly in the materials editor). Reset all you materials to various default colors to see what I mean (landscape 1 to grey , landscape 2 to green etc..). I may be wrong but I'll bet you'll run into a material or 2 that you may be able to downsize and get your scene a bit more under control. Test your materials for size also. You can get a bunch of arguments about this but if your material is roughly 110% of the approximate size it will be displayed on the screen (you gotta sort of eyeball it in) it should render properly . In other words if you have a bitmap material that is 2048x2048 pxls but will only take up 500x500 on your screen, try sizing it down. They add up fast. Good Luck Bot