Hi guys,
I tetsed the pixel lab material pack and some materials specificaly made for octane cuses a C4D error.
the crash seems to come from the octane plugin.
Do you experienced this kind of problem in the past ?
thanks
Bertrand
pixel lab material pack error in C4D octane
Moderators: ChrisHekman, aoktar
Have you posted any bugreport or missed?
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
Note that crash window file location.
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
I don't get that crash, but when I pull materials in from the preset library it causes my C4D to freeze for a very long time (depending on how many I drag in). One material can take 1-3 minutes.
Also, If I just have my materials without adding anything to the scene/objevts the Live Viewer will take extremely long to update. Sitting here just now waiting for an empty scene to finish.
Never had this problem before. I've tried uninstalling the Octane C4D plugin and then it works fine.
Also, If I just have my materials without adding anything to the scene/objevts the Live Viewer will take extremely long to update. Sitting here just now waiting for an empty scene to finish.
Never had this problem before. I've tried uninstalling the Octane C4D plugin and then it works fine.
C4D R18 / C4D R19
AMD Ryzen Threadripper 1950X — MSI X399 Gaming Pro Carbon
MSI 1080 Ti FE — 2 x PALIT 980 Ti Super Jetstream
Corsair AXi 1500W — Corsair Vengence 32GB 3000MHz LED White
AMD Ryzen Threadripper 1950X — MSI X399 Gaming Pro Carbon
MSI 1080 Ti FE — 2 x PALIT 980 Ti Super Jetstream
Corsair AXi 1500W — Corsair Vengence 32GB 3000MHz LED White
I don't know how it's set up. There may be some c4d shaders and can cause crashes or very long pre-render times. I don't absolutely advice to use them heavily. We'll provide better ways when OSL is available.Chrmez wrote:I don't get that crash, but when I pull materials in from the preset library it causes my C4D to freeze for a very long time (depending on how many I drag in). One material can take 1-3 minutes.
Also, If I just have my materials without adding anything to the scene/objevts the Live Viewer will take extremely long to update. Sitting here just now waiting for an empty scene to finish.
Never had this problem before. I've tried uninstalling the Octane C4D plugin and then it works fine.
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
- bertritude
- Posts: 143
- Joined: Sun Aug 09, 2015 4:30 pm
here's my bugreport file enclosed.
thanks to have a look please.
Bertrand
thanks to have a look please.
Bertrand
- Attachments
-
- _BugReport.txt
- bug report
- (784.17 KiB) Downloaded 224 times
Have you read my message? There is a "SLA" crash which comes from C4D sdk about rendering a C4D Layer. It happens when you have multi-core>1.
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
- bertritude
- Posts: 143
- Joined: Sun Aug 09, 2015 4:30 pm
Sorry Aoktar, I didn't underdtood...
So,with cores = 1, it will work ?
Thanks for your support.
Bertrand
So,with cores = 1, it will work ?
Thanks for your support.
Bertrand
Bertritude, This is that. C4D shaders are not evaluated as Octane shaders on render-time. They are pre-rendered before render begins and mapped as image_textures. If this guys done a material setup with C4D shaders that's not good way. Lot of performance loose. Best to use Octane nodes.
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