Cinema4D version 2022.1-XB1-(R3) (Experimental) 02.06.2022

[ryanaexavier]

Have you had a chance to look into the Vectron issues yet?

There's a change for compiler that doesn't let you use the positive values of distance. It looks like avoiding to see any results. Probably you need to revise the script for that. See discussion

We have some report about vectrons are not giving any output. Here's an example to show the weird problem for this. The scene is working well in Standalone 2021.1.5, but cannot see any shape with 2022.1-XB1.

You can see from the assignment to the distance in this shader that it never returns negative values:

Code: Select all

c.dist = sqrt(rr) / Dd;

A valid SDF always returns negative values in some region (this is the space that is “inside” the object). If a shader doesn’t return negative values anywhere it is not expected that it will consistently produce some object.

I appreciate the reply, however, it's a fractal. Do you have any other suggestions on a different distance estimation function that wouldn't require sqrt, but would still be "accurate"

[scaprendering]

Have you had a chance to look into the Vectron issues yet?

There's a change for compiler that doesn't let you use the positive values of distance. It looks like avoiding to see any results. Probably you need to revise the script for that. See discussion

We have some report about vectrons are not giving any output. Here's an example to show the weird problem for this. The scene is working well in Standalone 2021.1.5, but cannot see any shape with 2022.1-XB1.

You can see from the assignment to the distance in this shader that it never returns negative values:

Code: Select all

c.dist = sqrt(rr) / Dd;

A valid SDF always returns negative values in some region (this is the space that is “inside” the object). If a shader doesn’t return negative values anywhere it is not expected that it will consistently produce some object.

It looks like even example mandelbulb is not rendering correctly. To render fractals the output dist should be arbitrary I think or it will end up in a badly rendered object, or in worst cases an empty render.
Here's a screenshot from Octane standalone 2022 example Mandelbulb fractal and the same setup in 2021 C4D and 2022 C4D with exactly the same settings.
Hope this will help fixing the bug, since we can't do anything from user side.

[aoktar]

I'm not expert on fractal formulas and this because it's not about me. There's a core change and I haven't done this as you can read the my post. Could you please discus it in standalone topics.

[scaprendering]

I'm not expert on fractal formulas and this because it's not about me. There's a core change and I haven't done this as you can read the my post. Could you please discus it in standalone topics.

Yep, all good. I just was scared after your reply about changing the OSL code but it's obvious that there's something wrong in the core.

[GXGsynth]

is there any chance of getting the Scatter On Surface node/feature added to the C4D version from Standalone? It exists in Blender so theoretically possible? it seems preferable to the C4D Cloner

[GXGsynth]

2022.1 XB1 C4D seems to break all my Vectron projects that work in 2021.1.5 R3, and just doesn't want to load Vectron scripts period besides the init sphere. Also, when the compiled Vectron script has a bunch of parameters, it shrinks the code entry window which can't be resized, is that fixable?

Do you know the writing OSL or just copy/paste something? Did you check the log output to see results? Just send me your project with PM if you don't know to check.

I did some more tests and it seems like copy/pasting OSL script text into the editor in C4D and compiling does work, but that's the only way

If I try to load one of the preset scripts from the dropdown menus or have it load an external script or open an older project file, it fails

I'm not expert on fractal formulas and this because it's not about me. There's a core change and I haven't done this as you can read the my post. Could you please discus it in standalone topics.

I tested this in Standalone 2021.1.5, Standalone 2022.1 XB1, Standalone 2022.1 XB2, C4D 2021.1.5-R3 and C4D 2022.XB1-R3 and this only occurs in the C4D 2022.XB1 builds, I have no issues with any other version or standalone at all

[aoktar]

I tested this in Standalone 2021.1.5, Standalone 2022.1 XB1, Standalone 2022.1 XB2, C4D 2021.1.5-R3 and C4D 2022.XB1-R3 and this only occurs in the C4D 2022.XB1 builds, I have no issues with any other version or standalone at all

I've tested also and it occurs with Standalone too. Else of that's not possible as you say because we use same core for plugins and Standalone. There's revisions as we wrote and guys are looking for to fix the new issues.

[Kalua]

The plugin is working nice so far.
One question: when are we having an updated "Ray Switch" node?
XB1 standalone already presents "Add an input for photon rays to the ray switch node, and support raytype("photon") in OSL". I can't seem to find photon on C4D plugin side.
Regards,

[aoktar]

The plugin is working nice so far.
One question: when are we having an updated "Ray Switch" node?
XB1 standalone already presents "Add an input for photon rays to the ray switch node, and support raytype("photon") in OSL". I can't seem to find photon on C4D plugin side.
Regards,

My answer: I'm not aware of it. So I'll add that because you've reported. Thanks!

[Kalua]

The plugin is working nice so far.
One question: when are we having an updated "Ray Switch" node?
XB1 standalone already presents "Add an input for photon rays to the ray switch node, and support raytype("photon") in OSL". I can't seem to find photon on C4D plugin side.
Regards,

My answer: I'm not aware of it. So I'll add that because you've reported. Thanks!

Thanks, Aoktar. I appreciate that.
But it is on the XB1 features list: viewtopic.php?f=33&t=79602
Regards,