OTOY Forums

aoktar wrote:

blackcat321 wrote:I found that as long as there is a shader with C4d layers in the scene, octane will crash

It's not surprising, it's not stable. Try to don't use C4D shaders as much as possible. You can do the same with octane nodes or osl scripts.

blackcat321 wrote:

aoktar wrote:

blackcat321 wrote:I found that as long as there is a shader with C4d layers in the scene, octane will crash

It's not surprising, it's not stable. Try to don't use C4D shaders as much as possible. You can do the same with octane nodes or osl scripts.

I mean, there is only a C4d shader in the scene. The material doesn't give the object, but it still crashes

y81r wrote:Hello Ahmet,
I haven't worked with 2020 for a long time.
I found the node editor button in the lightTag below next to the help icon.
When I work with Nodes in the Light Node Editor and close and reopen the Editor, all nodes are gone.
NodeEditor for lights are a very welcome feature.
Did I miss something?

Something else, Redshift support xpExplosiaFX directly without VDB export, is this also planned for Octane?

Thanks!
Yassin

EDIT: Win10, c4d r21, 2x GTX1080 ti

linograndiotoy wrote:Be sure to keep RTX off in this specific version.
It looks like material management gets messed up due to a current core issue if RTX is on. This will be solved soon (I just verified it alsohappens in the current internal Octane for Blender version).

Basically, when using different materials with RTX on, you'll experience having one material controlling all the others (and you can easily get Octane locked).

Again, this seems to be common to all plugin versions using 2020 RC2 (Cinema, Blender...) and is a Core issue.

For now just keep RTX off, waiting for the next fix.

y81r wrote:I made a short video, maybe I'm doing something obvious wrong.
could you take a quick look at it?

Thank you!

y81r wrote:Hello Ahmet,
I haven't worked with 2020 for a long time.
I found the node editor button in the lightTag below next to the help icon.
When I work with Nodes in the Light Node Editor and close and reopen the Editor, all nodes are gone.
NodeEditor for lights are a very welcome feature.
Did I miss something?

Something else, Redshift support xpExplosiaFX directly without VDB export, is this also planned for Octane?

Thanks!
Yassin

EDIT: Win10, c4d r21, 2x GTX1080 ti

divasoft wrote:

y81r wrote:Hello Ahmet,
I haven't worked with 2020 for a long time.
I found the node editor button in the lightTag below next to the help icon.
When I work with Nodes in the Light Node Editor and close and reopen the Editor, all nodes are gone.
NodeEditor for lights are a very welcome feature.
Did I miss something?

Something else, Redshift support xpExplosiaFX directly without VDB export, is this also planned for Octane?

Thanks!
Yassin

EDIT: Win10, c4d r21, 2x GTX1080 ti

Hi, Aoktar. I join Yassin's question. What about direct Explosia rendering?)

aoktar wrote:When I finished the current works, stability and core features are more important right now. xp support is not high priority due to behavior of xp team for me anymore

y81r wrote: When I work with Nodes in the Light Node Editor and close and reopen the Editor, all nodes are gone.