Gamma issue with viewport rendering

[Core2000]

Am I the only one having the issue ?

We want to switch to 2025 as well, but this is only one of several issues we’re facing with it.

[maru]

Hi, I don't know why this wasn't reported, but now it is (Report ID=CC4D-1025).
For now, I can't tell if this is something we could fix or related to Corona at all, but it doesn't happen with Redshift or Standard render.
I will be sure to return here once I have any news.


Meanwhile, I would like to understand one thing, which I am sure will be also the first thing our developers ask:
How exactly is this feature more useful to you than the native Corona features such as VFB IR or Interactive Viewport? Why is it so important to use the native C4D Render Viewport? Preferably, please explain it as you would explain it to a 5-year old, or at least a non-C4D user.

Thank you in advance.

[TFit]

You're not alone, I'm having this issue as well. It's extremely frustrating. Things worked so well in C4D 2024 and earlier, and now nothing looks right.

[maru]

Same question as above: why exactly do you prefer to use the C4D interactive viewport rather than Corona's IR or Corona's interactive viewport?

[John_Do]

Hi maru,

I hope my answer will be enough to justify fixing this issue but here are few reasons :

- first it's not interactive, it's a final rendering in the viewport
- it's fast : great to quickly check some details in native res and full quality
- it's unobstrusive : there is no additional window to move (VFB IR) nor any settings to change to get the full quality from the get-go (viewport IR : the detail setting locked at 50% in any new C4D session, this thing is annoying)
- it's reliable : there is no risk of crash (VFB IR) and no lag (viewport IR)

In short it just worked as expected and it fitted nicely in my workflow. Would be nice to get it back.

[maru]

Thanks a lot!