Uncle Jeff pre combine.blend (4.2 MB)
Hey guys. The above is the entirety of my scene. I will try to simplify this but it’s a specific issue and it is likely not what you think. I have Googled this and it is not the memory/graphics card related issue that others are having. It is not a stuck “play” button. We’re talking hard crash to desktop.
The scene render works in EEVEE but not in Cycles. It crashes on “Initializing” displays in the upper left of the viewport.
If I delete “Jeff 1” (I have two “Jeff” collections) it renders. If I leave it, it crashes. If I delete SOME objects in Jeff 1, it MIGHT crash. Depends on which objects.
Okay but here is where I run into trouble. It’s not that simple.
You may think “okay, so delete an object, try to render, and repeat, until you find the culprit.” Yes, I did that, and that doesn’t work. It never renders that way. But like I said deleting every object in Jeff 1 works. If I delete the torso, arms, and arm-body connecting pieces, it was working, I think. But now it is not any more.
Also, before finding the culprit to be Jeff 1, I thought I found the “corruption” in the “stage” object, because for awhile it was rendering when I deleted it. And of course right when I go to create a new “stage” I realize it is no longer the culprit.
Sorry if this sounds crazy. It feels like I’m chasing a ghost and it’s driving me mad. I could decide to remake the entire “Jeff” but I could do that and then find something else is causing the crash.
I am on 2.90
I am on Windows 10.
I have a 2080 Super and 16gb of RAM and I’ve had MUCH larger and more complicated scenes than this before. Task Manager shows me only going up to 6.1gb of RAM used out of 16gb when the crash happens. Vram is 1.8/8.0GB.
I am rendering with GPU. CPU rendering also crashes in the same way, though.
I have crashed blender literally over 100 times trying to diagnose this. Thank god for the quick startup time.
Let me know if there is any more information you need. Thank you.