Cinema 4D version 2019.1.4-R2(Obsolete stable) 07.12.2019

Sat Nov 16, 2019 7:48 pm

Is it possible in this version to color the vdbs with textures? And if yes, how do we do that? thanks

Sat Nov 16, 2019 8:12 pm

thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!

+1

Sat Nov 16, 2019 11:40 pm

divasoft wrote:
thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!
+1

In my experience this issue has been there since always.

Sun Nov 17, 2019 10:27 am

Kalua wrote:
divasoft wrote:
thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!
+1
In my experience this issue has been there since always.

Yes. I did not say anything about this because Ahmet’s usual answer to this is that I’m busy with more important things.

Mon Nov 18, 2019 6:42 pm

thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!

Maybe I'm blind, how do you get it? It seems fine to me

Mon Nov 18, 2019 6:48 pm

aoktar wrote:
thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!
Maybe I'm blind, how do you get it? It seems fine to me

Here is an example: saving tonnemapped png from denoised pass.

Mon Nov 18, 2019 9:54 pm

aoktar wrote:
thanulee wrote:Testing it atm. Small detail: when i save from LV the demain pass as "png tonemapped" the gamma is wrong.
Thanks!!
Maybe I'm blind, how do you get it? It seems fine to me

if we save demain pass as "png tonemapped" we get image with linear color space instead sRGB.
In LV the pictures look the same, but if you open both in Photoshop, you will see that they look like different gamma. We need sRGB color space for all tonemapped passes.

Thu Nov 21, 2019 4:31 pm

Why is it when I save my c4d scene with the live viewer open it takes about x5 longer than when the live viewer is closed. I noticed in the bottom left when the live viewer is open and I AM saving, it runs a bunch of stuff that goes really fast, and when its closed it doesn't do that. Has only started happening with the last 2 2019 versions.... anyone else? I have autosave setup for every 5 minutes and its getting annoying, especially with larger cad scenes. But if I don't have autosave setup, c4d and octane is so unstable I crash like 10 times a day and lose hours of work....

Actually it only happens when it is rendering with the liveviewer open, not just when its opened paused.

Thu Nov 21, 2019 6:59 pm

LFedit wrote:Why is it when I save my c4d scene with the live viewer open it takes about x5 longer than when the live viewer is closed. I noticed in the bottom left when the live viewer is open and I AM saving, it runs a bunch of stuff that goes really fast, and when its closed it doesn't do that. Has only started happening with the last 2 2019 versions.... anyone else? I have autosave setup for every 5 minutes and its getting annoying, especially with larger cad scenes. But if I don't have autosave setup, c4d and octane is so unstable I crash like 10 times a day and lose hours of work....

Actually it only happens when it is rendering with the liveviewer open, not just when its opened paused.

It's not unstable if you don't use Game Ready drivers. Also I didn't see a behavior like that. Probably you have interesting case. Please send me your scene for testing.

Fri Nov 22, 2019 1:54 pm

It's not unstable if you don't use Game Ready drivers.

Keep in mind that not cards are supported by the Studio Drivers.
My Titan X Maxwell cards can only utilize the Game Ready Drivers.