Page 2 of 11
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Sat Mar 26, 2022 8:51 pm
by SSmolak
another problem with objects loaded from R25 Asset Browser. If object loaded from library have Octane material, textures from this material are automatically copied to "tex" folder of Project in HDD. Octane doesn't use images directly from Asset Browser library database. So there are double copies of all images.
Octane texture caching is disabled.
Objects loaded from Asset Database that have standard C4D materials doesn't create such additional images and tex folder.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Sun Mar 27, 2022 10:15 am
by aoktar
SSmolak wrote:another problem with objects loaded from R25 Asset Browser. If object loaded from library have Octane material, textures from this material are automatically copied to "tex" folder of Project in HDD. Octane doesn't use images directly from Asset Browser library database. So there are double copies of all images.
Octane texture caching is disabled.
Objects loaded from Asset Database that have standard C4D materials doesn't create such additional images and tex folder.
It's an irregular medium which is not directly accessible from Octane. So It cannot use that directly from database. Because of that it's creating a physical copy of image. Keep using it like that.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Sun Mar 27, 2022 10:22 am
by aoktar
SSmolak wrote:Octane doesn't show materials from XRef objects and when they are loaded Octane status is going crazy - it blinking "check others time : ....."
It's just working well on me! Keep putting better examples to show your issue. You may doing something fixable by changing the parameters of xref to keep it in a supported form.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Sun Mar 27, 2022 2:20 pm
by SSmolak
Thank you for information. This is very bad that Octane plugin can't read images directly from C4D databases. Since Maxon introducing this new browser I making catalog of all objects and due to the new stupid system there are three copies of all images now. First orginal location in HDD, next one are in C4D database and third created by Octane plugin. Very bad situation there.
As for XRef - I tried simple object. Material, especially textures are gone. No textures at all in Octane. I will send scene.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Sun Mar 27, 2022 9:15 pm
by aoktar
SSmolak wrote:Thank you for information. This is very bad that Octane plugin can't read images directly from C4D databases. Since Maxon introducing this new browser I making catalog of all objects and due to the new stupid system there are three copies of all images now. First orginal location in HDD, next one are in C4D database and third created by Octane plugin. Very bad situation there.
As for XRef - I tried simple object. Material, especially textures are gone. No textures at all in Octane. I will send scene.
There is a possibility to convert them to texture buffers and read from memory if this is a bad case. I need to test the case again.
For Xref probably using unsupported options, they should work if you just add xRef object to load something with default options.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Mon Mar 28, 2022 6:24 pm
by SSmolak
aoktar wrote:
For Xref probably using unsupported options, they should work if you just add xRef object to load something with default options.
Ha, probably because I used Xref as object from Asset Browser library
So this is the same problem.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Mon Mar 28, 2022 7:49 pm
by aoktar
SSmolak wrote:
Ha, probably because I used Xref as object from Asset Browser library
So this is the same problem.
Sorry I don't know how can you use it like that
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Mon Mar 28, 2022 8:46 pm
by SSmolak
aoktar wrote:SSmolak wrote:
Ha, probably because I used Xref as object from Asset Browser library
So this is the same problem.
Sorry I don't know how can you use it like that
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Mon Mar 28, 2022 10:33 pm
by SSmolak
Displacement of procedural textures doesn't work as expected with baking texture node because baking not respect the same transform values and projection from main procedural node. Even if the same transform node is connected to baking texture node. It completely not follow the same direction and scale of main procedural texture.
Re: Cinema4D version 2021.1.4 (Stable 2021) 23.03.2022
Posted: Mon Mar 28, 2022 11:17 pm
by aoktar
SSmolak wrote:Displacement of procedural textures doesn't work as expected with baking texture node because baking not respect the same transform values and projection from main procedural node. Even if the same transform node is connected to baking texture node. It completely not follow the same direction and scale of main procedural texture.
I cannot see any unexpected results. There's not any problems on plugin level.