in certain cases it is also crashing c4d directly, but it cannot be reproduced 100%. in any case it is making a scene unstable. problem is that materials using a specific compression in texture are difficult to filter out, as the only way to find them seems to look into each single material node containing textures... yes, this needs to be fixed asap and it seems to be a core issue. but maybe it's wise to disable the feature dropdown inside the plugin to avoid issues until this is resolved, aoktar?nejck wrote:So its been reported before? If so then please somebody look into it... I'm not using any slaves right now but would be immensely disappointed if a feature like that is broken :\tomsvfx wrote:Its been like this from the beginning.3dworks wrote:setting texture compression to anything other than "auto" make slaves crash. very tricky to debug, but i can confirm earlier reports for this.
Cinema 4D version 2019.1.1-R3 (Stable) 09.10.2019
Moderators: ChrisHekman, aoktar
Specs: Apple MacBook Pro M1 max 64GB 2TB, MacOS 12.5 / MacPro 5,1 with NVIDIA GeForce GTX 1080 8G, MacOS 10.13.6 / Mac Pro 5,1 with AMD RX5700 8G, MacOS 12.3.1 / HP Z600 with NVIDIA 3060 RTX 12G, Windows 10 pro + Netstor GPU box, 4 x NVIDIA GTX 980ti 6G.
CUDA error 1 on device 1: invalid argument
-> failed to launch kernel(kernel56)
device 1: PMC kernel failed
CUDA error 1 on device 0: invalid argument
-> failed to launch kernel(kernel56)
device 0: PMC kernel failed
PT core works
https://drive.google.com/open?id=1Nb8jZ ... QGATeq9aOs
-> failed to launch kernel(kernel56)
device 1: PMC kernel failed
CUDA error 1 on device 0: invalid argument
-> failed to launch kernel(kernel56)
device 0: PMC kernel failed
PT core works
https://drive.google.com/open?id=1Nb8jZ ... QGATeq9aOs
I'll test it, thanks3dworks wrote:
in certain cases it is also crashing c4d directly, but it cannot be reproduced 100%. in any case it is making a scene unstable. problem is that materials using a specific compression in texture are difficult to filter out, as the only way to find them seems to look into each single material node containing textures... yes, this needs to be fixed asap and it seems to be a core issue. but maybe it's wise to disable the feature dropdown inside the plugin to avoid issues until this is resolved, 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
- aparksproject
- Posts: 6
- Joined: Sat May 20, 2017 10:52 am
Hi Aoktar,
while I am really impressed with the Vector Displacements and experimenting with it was fun.
In the end this release is not usable for me at all, because the toon shader does not work (for me). Are you aware of this and planning to fix it?
I am getting the ususal device failure like in the good old days... I updated my nVidia drivers but nothing worked so far. I haven't seen anyone mentioning it not working.
Do you have any advice?
while I am really impressed with the Vector Displacements and experimenting with it was fun.
In the end this release is not usable for me at all, because the toon shader does not work (for me). Are you aware of this and planning to fix it?
I am getting the ususal device failure like in the good old days... I updated my nVidia drivers but nothing worked so far. I haven't seen anyone mentioning it not working.
Do you have any advice?
Try to use Nvidia studio drivers. Other issue is not up to plugin part, but I'll check and report itaparksproject wrote:Hi Aoktar,
while I am really impressed with the Vector Displacements and experimenting with it was fun.
In the end this release is not usable for me at all, because the toon shader does not work (for me). Are you aware of this and planning to fix it?
I am getting the ususal device failure like in the good old days... I updated my nVidia drivers but nothing worked so far. I haven't seen anyone mentioning it not working.
Do you have any advice?
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
Thank you!aoktar wrote:I'll test it, thanks3dworks wrote:
in certain cases it is also crashing c4d directly, but it cannot be reproduced 100%. in any case it is making a scene unstable. problem is that materials using a specific compression in texture are difficult to filter out, as the only way to find them seems to look into each single material node containing textures... yes, this needs to be fixed asap and it seems to be a core issue. but maybe it's wise to disable the feature dropdown inside the plugin to avoid issues until this is resolved, aoktar?

Hi Aoktar. You recently said that you spend a lot of time making Octane a best and stable performer.
5 crushes for 10 minutes. It's my usual work process with octane.
No need test scenes. it happens in any releases, with any materials with displacement. working with octane is a process full of pain and suffering.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl
5 crushes for 10 minutes. It's my usual work process with octane.
No need test scenes. it happens in any releases, with any materials with displacement. working with octane is a process full of pain and suffering.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl
Yes correct! It's not happening on me with development builds. Here it looks like a compilation problem, have you tried with a different C4D version? What happens if you disable node previews in Settings->Nodes?divasoft wrote:Hi Aoktar. You recently said that you spend a lot of time making Octane a best and stable performer.
5 crushes for 10 minutes. It's my usual work process with octane.
No need test scenes. it happens in any releases, with any materials with displacement. working with octane is a process full of pain and suffering.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl
Note: You may have problems but that doesn't mean plugin is not stable. You looks like having some exceptional particular issues, it may be related settings or software setups. You would see hundreds of complaint otherwise.
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
Maybe, but i'm not alone in this trouble viewtopic.php?f=33&t=72386&start=80#p370150aoktar wrote:Yes correct! It's not happening on me with development builds. Here it looks like a compilation problem, have you tried with a different C4D version? What happens if you disable node previews in Settings->Nodes?divasoft wrote:Hi Aoktar. You recently said that you spend a lot of time making Octane a best and stable performer.
5 crushes for 10 minutes. It's my usual work process with octane.
No need test scenes. it happens in any releases, with any materials with displacement. working with octane is a process full of pain and suffering.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl
Note: You may have problems but that doesn't mean plugin is not stable. You looks like having some exceptional particular issues, it may be related settings or software setups. You would see hundreds of complaint otherwise.
Many users of the Russian community with whom I communicate have the same problems. I can turn off the preview, but how will I then work blindly?
Have you tried creating your own test scenes in several displacement maps 4k, 8k on complex objects (more complicated than a cube or sphere)?aoktar wrote:Yes correct! It's not happening on me with development builds. Here it looks like a compilation problem, have you tried with a different C4D version? What happens if you disable node previews in Settings->Nodes?divasoft wrote:Hi Aoktar. You recently said that you spend a lot of time making Octane a best and stable performer.
5 crushes for 10 minutes. It's my usual work process with octane.
No need test scenes. it happens in any releases, with any materials with displacement. working with octane is a process full of pain and suffering.
https://drive.google.com/open?id=1tVFU1 ... Fv44BQwJjl
Note: You may have problems but that doesn't mean plugin is not stable. You looks like having some exceptional particular issues, it may be related settings or software setups. You would see hundreds of complaint otherwise.