So, I am working on a relatively complex scene (by my standards) and I can no longer get cycles to do an F12 render without crashing. Oddly, it works fine when doing a preview render.
The scene apparently has 4MM+ faces… so… that’s a lot I guess.
I’m fairly sure that there is no difference in geometry or subdivisions between preview and render right now. This is a problem because I’m only maybe 1/2 - 2/3 done adding objects, and I also want to use more subdivisions…
Anyone know what the issue probably is? I only have 3GB of ram, fwiw.
I guess you may be out of ram - I know there is a limit with GPU rendering with Cycles (the amount you have on your gfx card). Cycles will either not render and just produce a blank screen, or like I’ve heard from other users blender crashes.
The preview render uses less memory aparently, something to do with things like subds set lower in preview and the actual preview window being smaller usually than the full screen render. Least that’s what I’ve found. personally I do think that the preview still renders quicker anyway.
If you’re rendering with CPU, I’m not totally sure - could be similar.
Yes, I do render with CPU. It’s weird because there isn’t much (or any, I think) difference between my preview and render settings except for some curves objects. I guess I could try that. I am basically trying to figure out if this is a limit of my system, or a bug.
