VFB Forgetting Post Process settings (Part 2)

HI there, apologies if this has already been covered. I posted this 2 years ago on this very forum but I’m still having the same issue.
Link to that thread here: https://forum.corona-renderer.com/ VFB Forgetting Post Process settings

My VFB seems to keep forgetting my Post Process settings (Tone mapping, Bloom & Glare etc.)
I have set them to override in each my cameras and I’ve not touched anything in the Render Settings. But, I do change them in the VFB.

As such, I never know what I’m going to get when I send off multiple renders.
For example, I set Bloom and Glare to 15 and 8 respectively in the VFB for a particular frame. I then render the same frame again later and it’s reverted back to 20 and 2 respectively.
It’s the same with Exposure and Vignette- they seem to want to revert back to some other fixed value
So, I have to sit by the computer and babysit each frame to tweak the settings as they’re being rendered. I’ve struggled with this since v6. I’m now on v14 Update 1.

Add to this the recent Bloom & Glare issue (https://forum.corona-renderer.com/ Bloom & Glare dissapearing in some frames ) and it’s driving me insane.

Thanks in advance for your time guys.

“For example, I set Bloom and Glare to 15 and 8 respectively in the VFB for a particular frame.”

Do you mean you are trying to keyframe the values across frames? Or does this just mean “a particular camera” rather than frame?

Hi Tom, thanks for the reply.

I just mean “a particular camera”. My work is almost always for a series of stills taken from a bunch of different cameras in a scene.
Each camera has been tweaked with different Post Process settings (Tone mapping, Bloom & Glare etc.).

Awesome, thanks for confirming! Just wanted to be sure we understood the use case so we can take a look at what is going on :smiley:

Thanks again Tom, really appreciated.

If it helps, I’m running Cinema 4D 2026.1.2 on an Apple M1 Max Studio with 64Gb of ram. MacOS Sequoia 15.6.

Hi, sorry, but I currently don’t fully understand what you are doing. Could you please precisely explain it step by step? If you prefer, you can contact us with this info at https://support.chaos.com/hc/en-us/requests/new - we will respond, promise. :smiley:

Also, in the old thread you linked, I’ve found the attached info. Perhaps this is more of a workflow issue, or a feature request?

Thanks for your response Maru. Here’s my process:

Step 1: I create a scene in C4D using Corona lights, cameras and textures.
Step 2: For each camera in my scene, I use the Corona Camera Tag.
Step 3: In that tag, I adjust settings such as Simple Exposure, Contrast, Curves, Bloom & Glare etc. All check boxes are set to Override and Enable.
Step 4: In the Render settings, I select ‘Corona’. Then I don’t touch any of the settings other than Pass Limit and Noise Level in the General Settings.
Step 5: Using a Cinema 4D Stage Object, I keyframe each frame in my scene to a different camera.
Step 6: I open up the VFB and click render.
Step 6: I adjust each of the cameras Tone Mapping etc within the VFB whilst it’s rendering to lighten or darken the scene and so on.
Step 7: When I re-render later (after I’ve made changes to the geometry in the scene), many these adjustments have reset to different values. In other words- the VFB has forgotten all those adjustments I’ve made and I have to re-do them.

Basically, if I walk away from my machine, or render overnight, or use a render farm- most of my renders are either overblown, too dark, too contrasted, have to much bloom or none at all.

The solution, therefor, has been for me to:

• Render locally (at lower resolutions).
• Check and adjust each render as it appears in the VFB (While I’m meant to working on other parts of the project).

My workflow typically consists of visualising a space from about 15 to 30 camera angles.
So, that’s 1-2 hours (based on 4 minute renders) each day that I’m required to attend to these renders due to the fact that it persistently forgets my settings and can’t be trusted to deliver consistent and predictable results.

Apologies if any of this sounds a little frustrated. But, I’ve been dealing with this since v6 and I’m now on the latest version of v14. I’m losing so much time.

It’s either a bug or I’m missing something. That’s why I’m on here.

Thanks a lot, this made everything clear. We already have this reported as (Report ID=CC4D-1224). The tone mapping settings are taken from the camera that is active on the currently displayed frame. Hopefully it can be fixed soon.
Meanwhile, the workaround is to use the render queue. Everything seems to be working fine then.
I hope you can use that as a workaround and save lots of your time and nerves!

Thanks Maru, really appreciated.
I’ll give the render queue a whirl and see where it takes me.
All the best, Nick.