Cinema 4D version 4.02.1-R3 (Obsolete stable)

[TonyBoy]

No updated plugin for C4D V15. But 401.1-R2 along with Nvidea 417.71 is still a good ride.

This means I must stay with Nvidea 417.71 as long as I want to use Octane (I have no need or intention to upgrade C4D as I am merely a hobbiest). Thanks Ahmet for your efforts on behalf of all Version 15 users.

[adamfilip]

with R4 im finding its breaking and switching texture links.. I had to revert back to R3
So i apply one texture and another shows up

[aoktar]

with R4 im finding its breaking and switching texture links.. I had to revert back to R3
So i apply one texture and another shows up

Sorry what do you mean exactly? There's not any difference for this topic in between two versions.

[thanulee]

Hi, reply from Maxon support about relinking textures:
"Try it please by removing the Octane plugin.
If the Problem now gone, please report it directly to OTOY because we can't give you direct support for thirdparty plugins."
So they claim is not their issue and it only happens with octane.

And eventually they replied this:"

Due to the fact you need a to Cinema 4D R20 adapted Octane Exchange Version, the developer has to change some code.
So I think the Otoy developer have to get in touch with our development to clarify this.
Sadly we can't give you any useful help at this point. "

[SRCOBB]

Is anybody having issues with Octane assigning the WRONG materials to objects with this latest version? It keeps happening to me.
I have the correct materials applied, but Octane continuously renders a different material from the project..
Or I will add a material, and Octane will do nothing at all.
OSX 10.13.6 C4D R20.057 Octane 4.02.01-R4

[natemac00]

Is anybody having issues with Octane assigning the WRONG materials to objects with this latest version? It keeps happening to me.
I have the correct materials applied, but Octane continuously renders a different material from the project..
Or I will add a material, and Octane will do nothing at all.
OSX 10.13.6 C4D R20.057 Octane 4.02.01-R4

We had an issue where it would apply to the wrong object and nothing would be applied to the correct object.
I just duplicated the object and material and it fixed it.
I figured it was me and just something weird going on, but I can confirm that as well.
It’s hard to reproduce though, it’s only happen once to me and a coworker once.

[SLIMESUNDAY]

Is anybody having issues with Octane assigning the WRONG materials to objects with this latest version? It keeps happening to me.
I have the correct materials applied, but Octane continuously renders a different material from the project..
Or I will add a material, and Octane will do nothing at all.
OSX 10.13.6 C4D R20.057 Octane 4.02.01-R4

Man, i'm having a very similar issue. In one case, I opened up a folder that contained the textures for one of my materials. Textures from a different material folder somehow jumped and got placed into that folder without me doing anything. I never moved those textures there, so it was bizarre. In other cases, my displacement materials were ending up on objects that I did not assign the material to. Had to revert back to v3 as well.

[aoktar]

Is anybody having issues with Octane assigning the WRONG materials to objects with this latest version? It keeps happening to me.
I have the correct materials applied, but Octane continuously renders a different material from the project..
Or I will add a material, and Octane will do nothing at all.
OSX 10.13.6 C4D R20.057 Octane 4.02.01-R4

We had an issue where it would apply to the wrong object and nothing would be applied to the correct object.
I just duplicated the object and material and it fixed it.
I figured it was me and just something weird going on, but I can confirm that as well.
It’s hard to reproduce though, it’s only happen once to me and a coworker once.

R20.057?

[SRCOBB]

yes. R20.057
It's really doing it a lot, just putting the wrong materials on random things..

[aoktar]

yes. R20.057
It's really doing it a lot, just putting the wrong materials on random things..

I'm reverting back to old sdk(R20.028) for new build. I'll investigate the new R20.057 later.