Cinema 4D version 2018.1-RC1 (Test version) Tweet

[max383]

Super work

Issue discovered : Emissive on a diffuse material don't show / render when I use a mix Mat.

Works fine in 4, and works fine with specular emission inside the medium channel.

Hope it helped.

[0035]

I've found that trying to use vectron freezes C4D for me (OS X High Sierra 10.13.6). At least one other user has confirmed the same.
The program was freezing as soon as I tried to modify the vectron object in any way with the live viewer open. I then found that I could create an object, set it to mandelbub, and change the power BEFORE rendering in live viewer, then I was able to see and move around the object, but as soon as I tried to change parameters (I tried to increase the power) it froze again. Anybody else?

Yeah, it also crashes on Windows 10. I'm running it on C4D R19 with an RTX 2070, and it crashes right after I make the vectron object.

EDIT: Nevermind, it was a licensing issue, apparently

[bagel]

Not sure if it's been mentioned already, but light linking appears not to work in this version. Same c4d scene works fine in 4.01 R2.

[aoktar]

Not sure if it's been mentioned already, but light linking appears not to work in this version. Same c4d scene works fine in 4.01 R2.

it's working as I could checked. What's the problem?

[bagel]

Not sure if it's been mentioned already, but light linking appears not to work in this version. Same c4d scene works fine in 4.01 R2.

it's working as I could checked. What's the problem?

I appreciate the reply. I had to redo my scene. Seemed like something was broken in the scene file and it would no longer export to Octane for render. There was no way I could salvage it. (I'm actually not blaming Octane for this, I think something went screwy with C4D or my filesystem.) When I get to that point, I'll post my settings and results for you.

That being said, working with extremely high res VDB volumes (out of Houdini) that really aren't interacting with each other, I'm seeing boundary lines where the pyrofx containers were in houdini yet there's zero density in those areas and really shouldn't be affecting each other. I only have two volumes that are technically touching (overlapping grids) and it doesn't appear in every single frame of the animation just a handful. I did ensure that both volumes have exactly the same density and stepping settings as I know even 0 values in a grid can affect another grid if those settings are not perfectly matched. (I do a lot of volumes and fluid sim, I really like punishing myself, apparently.) btw... 2018-RC1 renders these VDBs SOOO fast!!! I'm so pleased and impressed. This kind of vdb resolution and complexity where nearly impossible or impractical in V4 let alone v3. Thank you for all you do!!!

Screenshot example from my scene:

[bagel]

Here we go! Happening again. This worked when I swapped out for the 4.01.1 R2 plugin. It does not appear to work in 2018 RC1. I turned off all of the other lights in the scene.

The light is not supposed to hit the back wall. Just the text and logo.

More critical info:

Cinema 4D R20.030
Octane C4D Plugin 2018.1-RC1
Windows 10
Pile of 1080Ti's

[aoktar]

Here we go! Happening again. This worked when I swapped out for the 4.01.1 R2 plugin. It does not appear to work in 2018 RC1. I turned off all of the other lights in the scene.

The light is not supposed to hit the back wall. Just the text and logo.

lightlinking1.png

lightlinking2.png

lightlinking3.png

More critical info:

Cinema 4D R20.030
Octane C4D Plugin 2018.1-RC1
Windows 10
Pile of 1080Ti's

First be sure that's not a mistake on your side. And pls send me a scene if you have it reproducible.

[bagel]

Sure. It'll be a little while until I can pack it and send it.

[bagel]

aoktar,

I discovered something while I was packing up my scene to send it to you.. I was using an 8k image based texture channeled into a glossy material for my back wall (the object I wanted excluded from illumination of that one light. I didn't necessarily want to include the huge png files so when I took the material off the back wall plane, light linking started to work. Is there something special we have to do to octane materials for light linking to work? I tested several times adding and removing the material with the IPR running and it would, respectively, illuminate the back wall plane when the material was added. But it seems like it's just this one material (node graph below). Other base/procedural materials work fine with light linking. Testing diffuse, glossy, universal and metallic and all work. But this glossy mat with image textures in the graph is ignored. Could it be an issue with image textures?

I'll PM you the project file. Thanks for taking a look at it.

[bagel]

It's displacement that breaks light linking. I just testing a new scene, 1 light, two objects. The second I attach an image texture to a displacement, image linking stops working.