Cinema 4D version 2018.1.3-R5 (Latest stable) - 07.10.2019 Tweet

[bepeg4d]

Hi,
please check the Camera Imager settings, and the Multi pass saving settings, they need to be coordinated.
If you are working with a Response curve different than Linear, you need to save in sRGB space.
If you have changed some parameters in the Camera Imager node, you have applied tonemapping, so you need to save the Tonemapped version.
Always use OctaneEXR with Cryptomatte.
ciao Beppe

[pixelmonk]

I got the cryptomatte to work. It was my fault. I was trying to shuffle the cryptomatte out and then tried the cryptomatte node. Bad idea. Instead, I just used the cryptomatte node from the read node. Also, I plus'd the cryptomatte alphas which removed the fringing.

[iDani]

Hi Aokter,

i have a little issue with some Instances/Multi Instances and the Display Tag. If i have a cloner with insatnces and a Display Tag on it and i blend the Cloner in with the Display Tag maybe from Frame 0 to Frame 25 on the last Frame the Instances disappear.
If i send frame 25 only to the Picturviewer than the Instances rendered correctly. I work a lot with Instances and the Display Tag and i have to rerender a lot of Frames. This happens not only in this Version. This happens in many Versions before.
I am on Windows 10 with C4D R20. I am very happy if you can fix this issue for the next versions.

Keep up you great work!
Cheers Daniel

[Raoul]

Hi, some great features in this release.
Unfortunately I'm getting a lot of freezes in Cinema with this latest version ( hadn't tried earlier versions of 2018) . Almost always when I'm adjusting materials.. node editor or just the normal material editor.
Need to force quit C4D, so don't get logs. Also nothing shows in the octane log if i have that open during the freeze.
I don't have this problem with V4 .. only with 2018.

Any thoughts?

Extra info:
Mac Pro MacOS Sierra.
C4d R19.068
gtx1080ti

Hi Raoul have you seen this topic?
viewtopic.php?f=30&t=71514

Thanks for the tIp J.C. ... I finally got the time to do some tests with this set of options but alas im still getting hard freezes.. always when a material is updating ( as seen in the bottom right of C4d where it tells you whats its up to)
Aoktar... are there any plans to investigate/fix this bug? Currently we are unable to use 2018 at all as the freezes keeping loosing us time. 4.04 works fine on all the same scenes so it shouldn't be scene related. this is a problem that happens on all scenes.
Do you have any thoughts on what the cause is?
Its a real shame as we'd really like to make use of our new licenses and the new features.

[aoktar]

Thanks for the tIp J.C. ... I finally got the time to do some tests with this set of options but alas im still getting hard freezes.. always when a material is updating ( as seen in the bottom right of C4d where it tells you whats its up to)
Aoktar... are there any plans to investigate/fix this bug? Currently we are unable to use 2018 at all as the freezes keeping loosing us time. 4.04 works fine on all the same scenes so it shouldn't be scene related. this is a problem that happens on all scenes.
Do you have any thoughts on what the cause is?
Its a real shame as we'd really like to make use of our new licenses and the new features.

It's not a reproducible issue to me. We have tried to investigate it without luck. It's not a common issue and made my thoughs that's depended to new sdk or something else. More interesting that V4 and 2018 for plugin side nearly identical and it's not happening with V4 sdk.

[3dworks]

i reported this issue some time ago for version 4.0.4.

i am having an issue with live viewer and i can reproduce this in all my complex scenes.

when a scene is loaded in C4D and i start the live viewer the first time, data will be transferrend very fast to the engine, only a few non-octane materials in the scene are converted. if i stop and restart that preview render (also after i closed and reopened the lve viewer window), and start a preview, octane will take a much longer time to send all the data to the engine. i also can see that status will report a material conversion for ALL the used materials in the scene. in many cases it goes from a few sconds to nearly a minute! is this a known bug or could it be some setting which causes this?

C4D prime R20 V20.059 mac / macpro 5,1 48G RAM, nvidia 980ti 6G VRAM, mac os 10.13.6

I didn't see this kind of behavior. Are you talking about a specific scene?

i'm experiancing it with all my scenes so far. should i send you the file? will logs help?

i now switched to this version and contiunue to have the same issue again. i've not sent any log files and scenes yet because it is very hard to reproduce on simple scenes and it is not clear what the trigger is.

in any case, the first start of live viewer is rather fast, as almost 90% of my materials are octane mterials. if i switch live viewer off an on again, usually reloading is very fast as well. but then there must be a factor which triggers the issue, maybe changing a texture or renaming / deleting materials - i'm not sure yet. after this, any reloading of the live viewer is really slow, and the plugin apparently seems to convert every single material as if would be a non octane material, that's what is indicated in the status messages at least.

nobody else ever experienced this? i will try to find out what is the trigger and will send aoktar logs and scene - once i nailed it.

[aoktar]

Activate all options of log output from settings/others and wait until same issue appeared. Then post your c4doctanelog.txt here. It will shows where is the problem.

[3dworks]

Activate all options of log output from settings/others and wait until same issue appeared. Then post your c4doctanelog.txt here. It will shows where is the problem.

ok i will do so!

[jeickholt]

Thanks for the tIp J.C. ... I finally got the time to do some tests with this set of options but alas im still getting hard freezes.. always when a material is updating ( as seen in the bottom right of C4d where it tells you whats its up to)
Aoktar... are there any plans to investigate/fix this bug? Currently we are unable to use 2018 at all as the freezes keeping loosing us time. 4.04 works fine on all the same scenes so it shouldn't be scene related. this is a problem that happens on all scenes.
Do you have any thoughts on what the cause is?
Its a real shame as we'd really like to make use of our new licenses and the new features.

I had a similar issue and fixed it by unchecking octane settings/nodes/auto load materials. You need to keep clicking 'Get Active Mat' to update the Node Editor, but it made it very stable for me.

[3dworks]

Activate all options of log output from settings/others and wait until same issue appeared. Then post your c4doctanelog.txt here. It will shows where is the problem.

ok, i could track it after working a while on the scene. when first using the live viewer time was normally fast - and the last time i re-opened the live viewer it took a really long time... see attachment. hope this helps track it down...