4K render result disppears

I rendered a scene in 1080p and it was fine no problem, but when I went to render the same scene in 4K (all other settings etc remained the same), it renders, but as soon as it’s finished the render disappears…

I thought it might be a Cycles X bug so tried it in CUDA, but it was the same. I’m using Blender 3.1

Any Ideas what the problem might be?

Can your GPU handle 4k? I’m guessing not

It’s a 2080 Super so I would hope so.

1 Like

Hi there, can you see your render if you change “Composite” to “View Layer” in the top right corner?

2 Likes

Hi, no I tried that. Nothing to see. I can see the render right up to the last second of it rendering, then it disappears.

I also tried going back to 1080p and it worked again, and previously had no problems rendering 4K. This is my first time trying to render 4k in Blender 3 though.

does anything change if you untick the post processing options in the output settings?

1 Like

I will try that now. When I closed Blender I did get this message interestingly…

1 Like

OK, so in fact after a restart it worked. And afterwards when I closed Blender again, I didn’t get that error message. Any ideas what that might be?

1 Like

Not sure. You could investigate some of the errors that appeared in the console but glad that it works.

1 Like

I just got off a project where I was using a clients custom baking addon, it might be that. I know very little about python though so I’m not sure how to read that error message. I’m just guessing that (bke.modifier) is bake.

Thanks for your help btw guys I appriciate it.

1 Like

Hmmm definitely not an expert in python as well but since it´s also giving an error for the directory of the tile file, might have something to do with the tile size and where your tiles are cached, since it only appears when you render high res :face_with_monocle:
but maybe it is just the baking addon :grin: interesting, let us know if you figured it out :slightly_smiling_face:

3 Likes

Hmm… OK thanks Sabrina :slight_smile:

At the moment it seems OK, but if it happens again I will try that and see if it makes a difference. It does seem like it might be a cache issue.

1 Like