Viewport-renders and F12-renders are completely different

[justavisitor]

@justavisitor why don't you upgrade to latest version? It works as it supposed to work. No differences in renders.

I've previously lost a lot of work because I had to upgrade to a version that no longer supported my files, and I'm not making that mistake again.

I'm on Blender 2.76b, I don't think it's that old, is it?

[J.C]

I was thinking of upgrading to Octane version 2.25 - 9.13 which works fine and is based on Blender 2.76. This is the most stable version I worked on. I will switch to v3 after a finished project.

[justavisitor]

I was thinking of upgrading to Octane version 2.25 - 9.13 which works fine and is based on Blender 2.76. This is the most stable version I worked on. I will switch to v3 after a finished project.

I don't doubt it's more stable, it's just that I'm in the middle of a huge project, and it would probably take me quite a while to figure out if any crucial functions had changed. So I'm afraid I'm stuck with this version the next 6-7 months.

[J.C]

Yes, sure. It would be too risky to upgrade software in the middle of a project.

[justavisitor]

Yes, sure. It would be too risky to upgrade software in the middle of a project.

J.C, if you see this - could you please tell me if the Octane Imager settings (such as Saturation) have any influence on F12-renders in your OctaneBlender version?

In my version (which doesn't have the Octane Imager check box), they don't. They only affect Viewport renders.

If they don't affect your final images either, is there then some other way to adjust Saturation in the final render? Or do you have to do that in Premiere or FCP?

I'll upgrade if these settings do affect your F12 renders.

EDIT: Just to clarify - your version does have the Octane Imager Check Box, right?

EDIT 2: I saw you mentioned in another thread that Shadow Visibility doesn't work in the latest version - have you noticed any other bugs?