cmNodes for R13

posted by Chris - 3 years ago

cmNodes for R13!

This release is essentially the same as the previous 1.5.07 build, but now with support for R13.

I am still working on new stuff as I can, and there have been some interesting developments with the VrayForC4D team (more on that later). I'm working on a variety of specular and reflection models, and I've got some more optimizations and improvements cooking.

20140511 I've received a couple of suggestions from Maxon for getting the Subsurface Scattering (SSS) shader to work with cmNodes. Both methods involve sneaking in a SSS shader to force the cache building.

The first (cmnodes_sss_workaround_01.c4d) involves adding a layer shader to an unused material channel (the Color channel in the simple example) and hiding a SSS shader in there.

The second (cmnodes_sss_workaround_02.c4d) involves putting the SSS shader in a material which is then applied "underneath" the cmNodes material.


Update for R17 - 20150909

cmNodes 1.5.89 has been built for R15 and will work with R17. This is a recompile of the previous build, so no new features or major changes.

Enjoy!

Attachments

30 Comments for “cmNodes for R13”


  • stephane

    thank you so much!!!

  • peter

    any news with the sss node working

    • Author

      Chris

      Not yet. There was a change in the R15 SDK that should get this to work, but I'm still looking for a solution for R13/R14.

    • Author

      Chris

      I've received some info from Maxon with a couple of workarounds for R13/R14. I'll edit this post and upload a couple of scene files which demonstrate the workarounds shortly.

  • Robby

    Thanks. But I get a wrong Yellow preview if I use a layer shader. Also I wish there was an option to disable the text border (stroke) on node names/titles.

    • Author

      Chris

      The "yellow preview" bug is on my list. For now you could try to recreate the layer setup with nodes, which should give a correct preview.

  • Paul

    Fantastic plugin! Cinema has been in need of something like this for quite a while. I have found what I presume is a bug though - I would like to be able to use an output from one tree as an input in another. If I drop in a cmNodesShader node, and link it to the desired output, I just get solid yellow. I can do what I want all in one tree in this particular case as its fairly simple, but I can see this would be annoying for something more complex.

    • Author

      Chris

      Thanks Paul. I do have group nodes planned which will do exactly what you're looking for.

  • zegolem

    Great plugin! Have you plans for other renderers? Especialy thinking about an octane implementation...

    • Author

      Chris

      No plans for Octane or M4D at the moment, although I have had several requests. We'll see what happens after Vray support is ready.

  • BobMan

    Waah...Thanks so much, that you did it, finaly. Happy new Year :-)

  • Tom

    Hi Chris,

    it seems like the version 1.05.08 doesn't work with C4D R16 (at least under Windows) but version 1.05.07 works.
    Maybe you should take a look into this.

    Kind regards,
    Tom

    • Author

      Chris

      Yeah, when I created the R13 build I added some basic version checking so that the R13 version wouldn't try to load in R14 or R15. I've got a new update that is almost ready which is mostly a refactoring of the code base in preparation for the migration to the R16 SDK, and an overhaul of the preview system which should improve stability. I'll try to get that update out soon.

    • Author

      Chris

      An R16 compatible version has been uploaded.

  • GMan

    Sorry if this's a stupid question, but, where can I download the R16 compatible version? I can't find the link.

    • Author

      Chris

      My fault, I should have been clearer. I've replaced the download on this page with the R16 compatible version. It's 1.5.74.

    • GMan

      Ah, there it is. I've downloaded and tested it, works great as it used to be. Thank you so much. :)

  • Lawrance

    It works pretty nice on R13 ! I am so glad, that you have make it possible to have a node based material editor inside Cinema 4D ! Still in R16 there isnt´t such editor. And i guess in the near future Maxon will not implement something like that. Therefore it´s soo cool that you have done this ! One man, who is faster than the big company :-)

  • Aleksey

    Hi Chris,

    Great tool, but my R16 crashes when i put an output node into a reflectance value =( (eg, reflection strength or Roughness)

    • Author

      Chris

      Thanks for reporting this. I'll check it out.

    • GMan

      I'd like to report an issue that when we try blending 2 blends into one, it's broken as shown in this picture http://postimg.org/image/lyy25tw31/, the result gone black or weird flat yellow in VRay. I've tested this in R16.

    • Author

      Chris

      These problems are caused by a bug in the output node, and an issue with the background preview handling. The output node has been fixed and I'm still working on the previews. I should hopefully have an update out this weekend.

    • Aleksey

      That's great news!

      waiting patiently.

      coz as it is right now, R16 is not really usable for me.

  • Author

    Chris

    I have a build which fixes the crashes, but I'm having problems with the R13 OSX build. I will upload the new build once that is worked out.

    • Author

      Chris

      Ok, a new build is up - 1.5.87. There is still an issue when the thumbnails sometimes don't update (still working on this), but the crashing should be resolved.

  • philhub

    Amazing work Chris !
    Didn't understand how a software with an expresso node editor just can't manage shaders on a nodal way.
    Now i get it, Chris is doing the work !
    Well done guy, very smart implementation with a nice Nuke perfume ;-)

  • GMan

    I didn't check cmnodes for awhile and when I'm back I found that 1.5.87 has been solved the blending issue.
    Thank you for your kind and active development, Chris. :)

  • Carlos Cortes

    Amazing Plugin !
    It is Possible to connect reflectance layers ?

    • Author

      Chris

      Thanks Carlos.

      It should be possible, but not with the Material node. Try creating an output node in your tree, and then create a cmNodeShader in the reflectance channel of a standard material. You should then be able to connect that output node to the cmNodeShader.

  • GMan

    I've found another issue with 1.5.87 on R16, if we make multiple output from Texture Node the problem will show up.
    To explain what I meant:
    1. Make a new node tree.
    2. Make a material output node and enable its color and bump node.
    3. Make a Texture node and assign any map or bitmap file to it.
    4. Link one output line to the color channel, then link another output line, from the same Texture node, to Bump channel.
    5. Assign the material to any object.
    6. Render and see the result.

    As per my experience, the result is supposed to be shown in black with the C4D standard renderer, with VRay, the weird yellow color comes up again.
    Please take a look at it.

comments are closed for this article