Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] Bug Reporting => Topic started by: Designerman77 on 2020-07-15, 18:55:48
-
Hi there,
does anyone know why in animations, curves in the VFB are deactivated every time a new frame is calculated?
If switched on after the animation finishes, the curves neither do seem to apply to the whole movie / all renders.
Of course one can add curves in post but I'd like them to stay active during the animation in Corona.
Thanks in advance for any tip.
-
Which versions?
Do you render directly to PV or via VFB?
What are your settings?
Or better, do you have an example to share?
Tested with latest daily on S22 - works fine, Curves stay on.
(https://i.imgur.com/oZOdOGO.gif)
-
Which versions?
Do you render directly to PV or via VFB?
What are your settings?
Or better, do you have an example to share?
Tested with latest daily on S22 - works fine, Curves stay on.
(https://i.imgur.com/oZOdOGO.gif)
Hey burnin, thanks for your reply.
I am on C4D R21. Corona 5 version.
Not eager to mess up my daily work with bugs from the V6 before it is officially released.
I had rendered to PV.
You think that could be the reason? Gonna make a short animation test render in the VFB.
-
As a note, prior to Corona 6, the PV uses a Cinema 4D native color space, which differs from the Corona VFB color space. You can only save animations from the PV, which means you get things saved with the C4D color space (meaning it can look a little different from what you see in the VFB).
In Corona 6, it's now possible to make the VFB use the C4D color space (it's a new default, even), which means anything saved from the PV will be the same as you saw in the VFB. This could be something to do with what you are seeing here - may not be that the curves are disabled, could just be that the color space is different.
-
As a note, prior to Corona 6, the PV uses a Cinema 4D native color space, which differs from the Corona VFB color space. You can only save animations from the PV, which means you get things saved with the C4D color space (meaning it can look a little different from what you see in the VFB).
In Corona 6, it's now possible to make the VFB use the C4D color space (it's a new default, even), which means anything saved from the PV will be the same as you saw in the VFB. This could be something to do with what you are seeing here - may not be that the curves are disabled, could just be that the color space is different.
Hey Tom, thanks for your tip.
Did a short test again - and yes, I can confirm that curves do not show effect in the C4D-PV, only in the VFB.
Also: if curves are switched on BEFORE hitting render on the animation, curves will also not show in the VFB either. You need to switch on the curves after animation is done.
However, seems like the effect of curves is not getting saved from the PV.
-
Can you send in a scene? It's working as expected for me with the latest daily build (from the 16th). Here's frame 30 from an animation, the curves greatly exagerrated to make sure they couldn't be missed :) The other version is turning curves off and saving from the VFB.
We'd also need to know your C4D version, OS, Corona version you tested on, etc.
-
Can you send in a scene? It's working as expected for me with the latest daily build (from the 16th). Here's frame 30 from an animation, the curves greatly exagerrated to make sure they couldn't be missed :) The other version is turning curves off and saving from the VFB.
We'd also need to know your C4D version, OS, Corona version you tested on, etc.
Hi Tom,
I am not on the daily build, since I don't want to deal with eventual bugs in it, right now during a big customer project.
Working with Corona V5 at the moment.
My software versions ( & hardware ): C4D R21, Corona V5, OS X 10.15.2, Mac pro 2019 - 16 core
Attached you find the C4D scene.
Thanks in advance!
-
In a file you shared, there's no curve set at all.
Still, it works as it should.
Once a custom curve is defined, it renders straight to PV w/o any problems. And doesn't reset even after restart.
W10, R18, CRN 5.2 here, so maybe it's just Mac...
(https://i.imgur.com/0S3ZxcP.gif)
example: Curve On vs Curve OFF
(https://i.imgur.com/tLCgc1U.jpg)
Modified scene w/ results attached.
//
& Damn, now I wish I could animate curves and all postFX, passes, lights... with/in Corona VFB. The team should really oughta make a standalone Studio Compositor version :p
-
In a file you shared, there's no curve set at all.
Still, it works as it should.
Once a custom curve is defined, it renders straight to PV w/o any problems. And doesn't reset even after restart.
W10, R18, CRN 5.2 here, so maybe it's just Mac...
(https://i.imgur.com/0S3ZxcP.gif)
example: Curve On vs Curve OFF
(https://i.imgur.com/tLCgc1U.jpg)
Modified scene w/ results attached.
//
& Damn, now I wish I could animate curves and all postFX, passes, lights... with/in Corona VFB. The team should really oughta make a standalone Studio Compositor version :p
Hey burnin,
thanks for taking the time to test & reply.
So, it seems to be an issue just on there Corona Mac-Version.
I had not attached curve settings into the C4D-scene, since I thought you would anyway apply your own curves. :)