Very happy to hear some touching to that. Enjoy it!mrom wrote:Aoktar, I cannot believe how fast the multithreades material generation is. Thank you very very much!
Cinema 4D version 2020.1-XB1-Test2 (EXPERIMENTAL) 10.12.2019
Moderators: ChrisHekman, aoktar
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
yes. confirm R 21.115divasoft wrote:I agree with wrapthereal66 and confirm volume fog object crush. Adding an volume object immediately crashes the cinema.aoktar wrote:Did you try with a new scene or a different scene?wrapthereal66 wrote:i just try like 7 time and immediatly when i create a volume fog , it crash ! :/
this is the crash report:
IMPORTANT!!! 2019.1.5 have a same bug!
Win 10x64, AMD 1950x 16C/32T, RAM 32Gb, RTX 3060x3
Octane-for-C4D(R23.110)2021.x.x, Cycles4D, Centileo. Nvidia 472.47 STUDIO
Octane-for-C4D(R23.110)2021.x.x, Cycles4D, Centileo. Nvidia 472.47 STUDIO
Fixing it without changing the build numbers, please re-download the plugin.wrapthereal66 wrote:i just try like 7 time and immediatly when i create a volume fog , it crash ! :/
this is the crash report:
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi Ahmet,
Thoroughly enjoying the great speed improvements with RTX!!! Great work
I have noticed that not all changes to the camera imager are not being rendered out. Specifically, saturation and lut strength. It works in the live viewer but not in the final render unless I'm missing something.
I have attached an image illustrating the difference.
I'm rendering with the following settings
Camera tag:
- Response: Linear
- Neutral response checked
- Gamma:2.2
Render Pass Settings
Image colour profile: Linear
Tonemap type: Linear
Render Buffer tyoe: Float (linear)
Thoroughly enjoying the great speed improvements with RTX!!! Great work
I have noticed that not all changes to the camera imager are not being rendered out. Specifically, saturation and lut strength. It works in the live viewer but not in the final render unless I'm missing something.
I have attached an image illustrating the difference.
I'm rendering with the following settings
Camera tag:
- Response: Linear
- Neutral response checked
- Gamma:2.2
Render Pass Settings
Image colour profile: Linear
Tonemap type: Linear
Render Buffer tyoe: Float (linear)
This is not a new behavior on this version.protokol wrote:Hi Ahmet,
Thoroughly enjoying the great speed improvements with RTX!!! Great work
I have noticed that not all changes to the camera imager are not being rendered out. Specifically, saturation and lut strength. It works in the live viewer but not in the final render unless I'm missing something.
I have attached an image illustrating the difference.
I'm rendering with the following settings
Camera tag:
- Response: Linear
- Neutral response checked
- Gamma:2.2
Render Pass Settings
Image colour profile: Linear
Tonemap type: Linear
Render Buffer tyoe: Float (linear)
LV is using tonemapped render buffers. In PV with your current settings you're using raw output.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Loving this release
Here is a speed comparison using the multi-core material speed up and RTX
Also as posted above, the colour difference when RTX is turned ( on left and off on the right ) Can't wait for the future of this
Here is a speed comparison using the multi-core material speed up and RTX
Code: Select all
--------------------------- EXPORT LOG ---------------------------
Multi-threaded material conversion, thread count=30
threads:0
Export materials time= 425.308 ms
Collect objects time= 14.148 ms
Mesh creation time = 53.059 ms.
VRAM used/free/max:3.645Gb/5.361Gb/11Gb Out-of-core used:0Kb RAM used:24.109Gb total:63.875Gb OpenGL free/total:0/0
Auto Save of D:\C4D_backup_autosave\test28_sand_0009.c4d@20191219_150506 successful
--------------------------- EXPORT LOG ---------------------------
Multi-threaded material conversion, thread count=30
threads:0
Export materials time= 54.528 ms
Collect objects time= 16.8 ms
Mesh creation time = 66.097 ms.
VRAM used/free/max:3.376Gb/5.638Gb/11Gb Out-of-core used:0Kb RAM used:24.922Gb total:63.875Gb OpenGL free/total:0/0
Auto Save of D:\C4D_backup_autosave\test28_sand_0009.c4d@20191219_151006 successful
Also as posted above, the colour difference when RTX is turned ( on left and off on the right ) Can't wait for the future of this

- ryanaexavier
- Posts: 20
- Joined: Fri Jul 06, 2018 8:11 am
I have noticed that materials dont seem to work on vectron objects. Do you happen to know if this should be expected to work yet?
Still, thanks a bunch for always being a master with the c4d integration.
Still, thanks a bunch for always being a master with the c4d integration.
- magadesign
- Posts: 1
- Joined: Sun Jan 06, 2019 4:41 am
I want to ask a question, why is there no obvious difference in the speed of RTX?
The driver is STUDIO's latest 441.6,
The same is true on the independent version of the test.
Sometimes RTX is slower than not.
The driver is STUDIO's latest 441.6,
The same is true on the independent version of the test.
Sometimes RTX is slower than not.
About RTX support, it is still experimental.
A lot of fixes are going to arrive with the next 202.1-XB2 SDK.
ciao Beppe
A lot of fixes are going to arrive with the next 202.1-XB2 SDK.
ciao Beppe
Really I missed that! Probably I broke it after doing some revisions for vectron, I'll fix it backryanaexavier wrote:I have noticed that materials dont seem to work on vectron objects. Do you happen to know if this should be expected to work yet?
Still, thanks a bunch for always being a master with the c4d integration.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw