There's not a reason to ruin your work, what you mean? It just changes current kernel to info kernel and I can be stay in this mode if crashes. But it will not ruin anything in scene else of this. Please give sample to show how it stucks in this mode.divasoft wrote:I also noticed that in some cases octane cannot exit solo mode material. Nothing helps. We have to restore scenes from a backup. And if there is no copy, then the whole work will be ruined.
Cinema4D version 2020.1.5-R4 (Obsolete stable) 17.10.2020
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
It's not reproductable, can you do? So send me a sample scene to checkdivasoft wrote:Hi Ahmet, i found a new bug, please take a look.
https://yadi.sk/i/BUeetDn2PRDkIw
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
No timing, both will take some time to implementVVG wrote: 1.When will Neutron (node-based sys) be supported R23?
2.When will C4D XB 2020.2 ?
thanks
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
- AaronWestwood
- Posts: 141
- Joined: Sun Feb 26, 2017 3:01 pm
Just wondering as I dont have the newer version. Have we got the option back on the scroll wheel to show color/luminance info?
3D Environment Artist
http://www.artstation.com/aaronwestwood
2 x 4090 // 13900KS // 96GB 5600mHz DDR5 // Windows 11
http://www.artstation.com/aaronwestwood
2 x 4090 // 13900KS // 96GB 5600mHz DDR5 // Windows 11
Hi, Aoktar
Since I upgraded to the latest Nvidia Studio driver 456.38 (requirement to 2020.2), Octane 2020.1.5 R3 started giving errors wich calls out the log window and closes Cinema 4D. So far erros are triggerd by different actions like: sliding "MAX tile Samples", sliding "parallel samples", opening the node editor or draging nodes.
PS: I haven't upgrade to R4. I will do it this afternoon. I report you back in case the errors persits.
Since I upgraded to the latest Nvidia Studio driver 456.38 (requirement to 2020.2), Octane 2020.1.5 R3 started giving errors wich calls out the log window and closes Cinema 4D. So far erros are triggerd by different actions like: sliding "MAX tile Samples", sliding "parallel samples", opening the node editor or draging nodes.
PS: I haven't upgrade to R4. I will do it this afternoon. I report you back in case the errors persits.
- Attachments
C4D 2025.1.1 Octane 2025.1 Build 0104, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
Hi Kalua, please downgrade to previous stable driver. There will not newer sdk for 2020.1.x series. Using R4 will not help due to built on same sdk.
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 Kalua, I have 456.38 Studio driver installed from some time now, and everything is working smoothly here with both 2020.1.5, and 2020.2-XB
Note that 456.38 is available in both Game Ready and Studio version.
If you don’t have Maxwell GPUs installed, please make sure to perform a clean installation of 456.38 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3533/en-us
To perform a clean installation, please follow these steps:

The previous version was 452.06 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3247/en-us
There is also a new version 456.71 of Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 6049/en-us
ciao Beppe

Note that 456.38 is available in both Game Ready and Studio version.
If you don’t have Maxwell GPUs installed, please make sure to perform a clean installation of 456.38 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3533/en-us
To perform a clean installation, please follow these steps:

The previous version was 452.06 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3247/en-us
There is also a new version 456.71 of Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 6049/en-us
ciao Beppe
Thank you, Beppe.bepeg4d wrote:Hi Kalua, I have 456.38 Studio driver installed from some time now, and everything is working smoothly here with both 2020.1.5, and 2020.2-XB![]()
Note that 456.38 is available in both Game Ready and Studio version.
If you don’t have Maxwell GPUs installed, please make sure to perform a clean installation of 456.38 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3533/en-us
To perform a clean installation, please follow these steps:
The previous version was 452.06 Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 3247/en-us
There is also a new version 456.71 of Nvidia Studio driver:
https://www.nvidia.com/download/driverR ... 6049/en-us
ciao Beppe
I will run a clean driver install.
C4D 2025.1.1 Octane 2025.1 Build 0104, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
Hi, Aoktar
Something else I noticed since 2020.1.5-R3 (as far as I can tell):
I created this glossy material with material layer (metallic), and it turns out the metallic layer gets this anysotropic effect although it's set to none.
On the other hand, a blend shader with equivalent settings (no material layered) get the correct result.
Is it a bug?
PS: Anysotropic effect goes away the moment I disconnect the material layer's bump. Even when bump connectted set to 0, Anysotropic effect appears, so it's not a bump scale issue.
Something else I noticed since 2020.1.5-R3 (as far as I can tell):
I created this glossy material with material layer (metallic), and it turns out the metallic layer gets this anysotropic effect although it's set to none.
On the other hand, a blend shader with equivalent settings (no material layered) get the correct result.
Is it a bug?
PS: Anysotropic effect goes away the moment I disconnect the material layer's bump. Even when bump connectted set to 0, Anysotropic effect appears, so it's not a bump scale issue.
- Attachments
-
- Nodes of the metallic material layer
- Screenshot 2020-10-21 094454.jpg (8.71 KiB) Viewed 3158 times
C4D 2025.1.1 Octane 2025.1 Build 0104, <<2 X 3090 + NVlink>>, Windows 10, X399, AMD TR 1950X, 128 GB RAM, NVIDIA SD 552.22
https://www.behance.net/PaperArchitect
https://www.behance.net/PaperArchitect
- jayroth2020
- Posts: 487
- Joined: Mon May 04, 2020 7:30 pm
Do you see the same result in Standalone?
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D