Material node editor is not stable...

[R_Flash]

Octane Material Node Editor in Cinema 4D is not stable. Many crashes and bugs when I try to connect some nodes. And no laws. It work correct at first, and then the same operation will result in an error and crash of Cinema. It's starting to annoy. If Otoy can`t make a stable Editor, why not use a ready platform based on XPresso Editor, as is already done in the Arnold and Redshift renders? Maybe somebody can explain?
Post of cry from the heart!

[aoktar]

I'm writing that not Otoy. People use that and don't cry about crashes. I haven't heard these.
What's your version? Do you have any better info about crashes? Bugreport.zips?

[aoktar]

why not use a ready platform based on XPresso Editor, as is already done in the Arnold and Redshift renders? Maybe somebody can explain?

It's a design choice due mix-material support. Also node editor is not doing any special handling. Just connect/disconnect nodes as you do from material editor. And store nodes under other nodes. Your problems may be about preview generation of nodes.

[R_Flash]

Aoktar, thanks for replay. I didn`t save bug report after last crash. i`ll do it next time and send you.

P.S. I have Cinema 4D R17.053 and Octane 3.03.4-R1. Videocard GeForce GTX 980

[aoktar]

Aoktar, thanks for replay. I didn`t save bug report after last crash. i`ll do it next time and send you.

Also try to send a scene which caused crash and info about latest steps. What's your version?

[R_Flash]

Aoktar, last time crashing was when I tried connect node Color Correct to Diffuse input and after that connect image Texture node to CCorrect input, and CRASHING! After that I change sequencing. I connect texture to CCorrect input and only than connect all nodes to Material Diffuse input. And magic, everithing work correct.

[aoktar]

I can't reproduce crashes since a long time. Better to send bugreport/scene/etc.. when you have any crashes. Also try to disable "update previews on drag". As i said that's built over C4D's node storage structure. Nothing is unnatural. It's not creating any special nodegraphs. Just store required parameters in material/textures. Maybe a problem about store two times the same node. But it should not happen since latest improvements.

[R_Flash]

Maybe in last updates this problem is disappeared. Last time I try not use Node Editor unless necessary. I`ll try specially make hard material for check