I've been learning blender and the color ramp node in their version of cycles is incredibly useful, and I might say essential. The color ramp control itself is probably a complicated control to build, looking at the base controls of Poser. But adding this useful node would give incredible control to the textures we have available to us.

I don't think that is going to happen. If you search this forum, there has been a request for this particular feature. I agree it would be convenient to have it available but there might be a way to recreate it by assembling a compound node from other supportive nodes.

I seem to recall that this was brought up briefly in the recent Poser 12 Early Access webinar.

hborre posted at 4:56PM Fri, 04 December 2020 - #4406036

I don't think that is going to happen. If you search this forum, there has been a request for this particular feature. I agree it would be convenient to have it available but there might be a way to recreate it by assembling a compound node from other supportive nodes.

I don't think it will hapeen eithe, but for the life of me I can't figure out why or why they're ignoring the requests.

As I've posted before, the reason that the colour ramp and a few other Cycles nodes aren't in Poser is purely because they require UI stuff that isn't in Poser already. The dev team decided back in 2015-ish that the work needed to add those UI elements was significant and was not worth the time for a handful of nodes.

I'd suggest that anyone who would like to see this added go to the Support site via posersoftware.com and submit a ticket under Feedback. That way the dev team will know what the level of interest is and can prioritise accordingly.

I stitched together a workaround in P11. Seems to load in P12. Matches results I see in blender. Choose Constant or Linear Gradient as an input.

Share CG Link

With Gradient

With Constant

As I see what is possible in Blender, I keep getting disappointed that Poser is not keeping up with Blender options. It is good that Poser team is using the latest cycles build, but there are quite a few shader options that are unsupported.

The issue with Poser trying to put in the Color Ramp as seen in Blender is that in Poser a Node Input is limited to a single value (RGB being a special case in that there are 3 sub parts to the main value). Looking at the Nodes as saved in a PZ3 file it breaks down to

NodeInput "name of the node input"

value 0 0 1 or some other such numbers that relate to the default values of the input if no other node is hooked up

parmR NO_PRAM

parmG NO_PRAM

parmB NO_PRAM

node NO_NODE

file NO_MAP

In all the nodes I have looked at this is the same pattern. The last parameter is if an image map is attached. the node is the name of the node whos output is being fed into this nodes input. The RGB inputs would be for a color input. Looking at how Poser does thing you can't have a node with multiple values on a single input. And that is what the color ramp is. The color ramp has a variable number of points that can be defined and how much each point covers. It is variable nature of the node that Poser can't handle. And to make it so that it can would mean breaking all the other nodes so that every Python script that works with nodes won't any more. There are work arounds as sschneww has shown. All that needs to be done is to make a comparison function with as many points as you need to and then apply the new output based on the value of your input.

At least now we have a substitute to use. Good job.

Sounds as if the color ramp problem could at least be alleviated by adding a space for two additional colors. Or is that too simplistic a thought?

It might work for simple cases, however looking at images of color ramps I have seen one with 7 points. Now that may be an extreme case but it is a case and in order to have what is called a color node it would have to be able to handle that.

Seven color spaces wouldn't be bad. Just two more than I suggested. Are you saying Poser can't handle the extra color spaces?