OTOY Forums

Kalua wrote:I have been reshading some assets with some better practices and I noticed this bug that persits since V2. It's not critical but I let you know just in case.
So here you go:
A MIX shader with 2 materials that use same textures for diffuse, bump, etc (all duplicated). I decided to unify the textures in order to make it more efficient. Here is when this small bug takes place:
The renoded shader doesn't recognize the new node in it's preview window - although the final MIX preview works fine and the Live view renders just fine. To fix it you must create a new node and relink both materials inputs.
Like I said before, it's not critical but it comes a long way it persists - even though I don't use MIX shaders anymore ,with some exceptions.
Thanks for the great work!

frankmci wrote:

Kalua wrote:I have been reshading some assets with some better practices and I noticed this bug that persits since V2. It's not critical but I let you know just in case.
So here you go:
A MIX shader with 2 materials that use same textures for diffuse, bump, etc (all duplicated). I decided to unify the textures in order to make it more efficient. Here is when this small bug takes place:
The renoded shader doesn't recognize the new node in it's preview window - although the final MIX preview works fine and the Live view renders just fine. To fix it you must create a new node and relink both materials inputs.
Like I said before, it's not critical but it comes a long way it persists - even though I don't use MIX shaders anymore ,with some exceptions.
Thanks for the great work!

I think I had a conversation with Ahmet a few years ago about a related issue. As I recall, he told me it is an internal limitation with the way C4D thinks about materials and their sub-components. Essentially, C4D assumes each node in the shader only has one "true" parent material and makes some assumptions and shortcuts based on that. While you can connect nodes to multiple "parent" materials, it's often only the first material that will be properly updated when a shared child node is changed. Things generally still render properly, but you may not get the feedback you expect without forcing a refresh.

Maybe once Octane's and C4D's new node based shaders are more tightly integrated, this issue can be resolved.

CrusaderArts wrote:Hi,

Seems like Toon Materials have a problem with this release.

I keep getting these errors when making a toon material:

Code: Select all

Started logging on 08.10.19 13:17:07

OctaneRender Enterprise 2019.1.1 (6000101)

CUDA error 700 on device 0: an illegal memory access was encountered
  -> kernel synchronization failed
device 0: preview failed
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 0: an illegal memory access was encountered
  -> failed to deallocate device memory
CUDA error 700 on device 0: an illegal memory access was encountered
  -> could not get memory info
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to unload module
CUDA error 700 on device 1: an illegal memory access was encountered
  -> failed to create link

Is this a known issue?

NVN wrote:lol stable????

i used it 3 times with round egdes aktivated and it crashed always immediately ...
looks more than as a alpha

tomsvfx wrote:There seems to be a bug where reising Octane LiveViewer windows while rendering crashed c4d and freezes Windows UI (cant do anything with mouse, but can open start menu or task amanger with shortcuts and kill C4D task)