Hello, everyone! I have come across this issue where my .blend won’t render. I tried to fix the issue myself by enabling simplify to reduce the texture size because I thought that reducing the texture would ease my RAM, and that did not work. I also tried rendering the scene with fewer assets and still, it didn’t render. Finally, I tried rendering on a render farm (Fox Renderfarm) and it STILL didn’t render. Can somebody help me with this?
By the way, I don’t have a dedicated GPU with VRAM, so I use my CPU to render. I also tried rendering on Fox Renderfarm with CPU rendering.
One more thing: I should clarify that when I render it won’t show any calculation of the lighting, meshes, or materials. Blender will instead wait, then crash.
So that’s something where we can only give guidance on how to find the problem, since there are a few possibilities…
My bet is that some objects got a modifier or something similar with different settings on viewport and render. Then when you render something fills the ram and blender crash.
You can either explore the scene and try to find the culprits ( could be several objects) , or try to selectively eliminate possibilities.
I’d first make a backup of your file since the goal is to make a giant mess out of it …
First remove all the textures, if they are all in the same folder you rename that folder.
Then do a test render, we made sure it’s not a texture issue.
Then put all object in a collection and make sure it’s completely desactivated at render and viewport. Try to do a render and see if it doesn’t crash.
If it crash , try again but remove all object from the scene.
If it works, then we know that 99% of the chances are that it’s an object.
Then bring back objects in the scene, you can do every 5 or 10 objects, or half of them, depending on if it crash or not you know in which group is the issue.
And from there hopefully you’ll be able to narrow down the issue.
If all that doesn’t work we’ll try something else, but most of the time that’s enough !
Thank you, @sozap! Turns out it was just one object: it was the daybed. Also, I do find it to be a little crazy, but when I also rendered this on the render farm it was over-capacitating their RAM too (the render farm had 64GB of RAM). Once again, @sozap, thanks so much!
P.S. I have been trying to solve this issue for a month until you helped.
Cool ! I’m glad it worked ! This method to debug a scene saved my life more than once !
Yes most of the time when you look into optimizations it turns out that only a few unexpected objects are taking like half the memory / performances or worses.
I don’t exacly know what problem was in the daybed, but for instance subdivision can grow quite fast.
it’s not noticeable if you subdivide only once most of the time, but on high density mesh, going from subdiv 1 to subdiv 3 can be just enough to crash blender.
