November 2, 2021 at 5:02 pm
Hello, I have encountered an issue when attempting to create new Node based materials through C4D’s built in node material system. Whenever I attempt to use any function based nodes, instead of returning the usual matrix of procedural color (1st image, taken in R21) (discovered when attempting to use a noise node) instead they return a solid color (image 2, taken inside built in Noise node view.) I have managed to recreate this problem in a fresh installation, a downgraded version, and even the newest updated R25 version, but this problem does not persist in my old R21 installation, where the feature works properly.
The output is neither properly previewed nor properly represented in the rendered material. Instead it is persistently a solid color, across every F:X type node. Please let me know if I am missing something, as I am new to working with Node based materials. Like I said, this problem persists even with a fresh install of the program with default preferences. Let me know if anyone that works with the new C4D node materials has had this problem or has any potential solutions.
Thanks for your help,
November 2, 2021 at 7:07 pm
November 10, 2021 at 9:45 pm
Sorry for the bump, but I am still having this issue and would like to know if anyone has some insights.
November 11, 2021 at 6:10 am
Do you have the project to play with?
I’m going to take a stab at what it might be and it may help you along. (I couldn’t open the images for some reason so they remain small thumbnails in the post – too small to see what’s going on)
The first is that the node system is still in beta and those growing pains may include some of the more parametric material nodes. With that “excuse” out of the way….
Things like noises are no long colors in the true sense in the node editor, they are now considered Floats (16 or 32 bit data). So often you will have to covert a float to a color or visa versa to get anything meaningful. Some of the procedurals are vector based so even though they look like colors (the RGB pixel telling cinema which way to point the vector) they are, again, not a true color and while you can convert these to floats or colors they won’t really make any sense when you do so. Then in some cases you can use a float noise but you will only get the red channel say. This will still work as intended because the engine just takes the values out of that one channel and ignores what you perceive as a color.
So try a conversion node between your procedurals and your input and see if that helps. If not send the project along and we’ll take a look.
November 14, 2021 at 12:52 am
I don’t have any project in particular where I use this, but I have created a test project where the issue is recreated on my installation. The attached image shows what I see in the node editor for the uber material in the attached project. The issue is that the Noise node is not functioning. It does not preview properly, and it does not show in the final render of the object with the material applied. I have this issue with similar nodes as well, however there are too many to list, so the noise node is included as an example (I assume that whatever is breaking the noise node is also breaking the others.)
I am suspicious that this issue is with my installation or system configuration, and not with my actual project. If someone could try loading this into their R25 version and see if the noise works or not, that would narrow it down to whether or not it is a system issue.
Recently, I have also encountered an issue where some of the nodes that *do* work periodically do not. When I import the nodes from another project where they are working into one where they are not, they resume functioning, as if the program “remembers” how they work. I have replicated this so far with just the Image node.
November 14, 2021 at 1:23 am
Yep there’s something up there. The basic noise works fine but even on a clean new file on my R25 the noise node produces nothing. There is an update to R25, are you using that one? (I am not yet).
I’ll keep poking it and let you know what I find.
November 14, 2021 at 1:26 am
I am using R25.010 currently, however I was able to recreate the issue in a fresh install on R25.015.
Log in to reply.