Wrong Range Node in Search Menu in 27.7

[AlexeyAdamitsky]

When adding the Range node with Add → Search... and search for Range node, it'll give you this node.



This node doesn't work when you're trying to connect color texture to its sockets. I think it's a legacy node.

Adding the range node with when navigating to Add → Textures → Operators → Range gives you the proper node.



Please fix the search function to give the correct node. I prefer the search for faster workflow.

Also, please make the sliders for Input Min/Max and Output Min/Max to work in the soft range of -1 to 1. Currently, it's -10000 to 10000. It's extremely difficult to control values within such huge range when you need to work mostly withing a narrow range of -1 to 1.

[jobigoud]

I think it's a legacy node.

The two nodes were introduced recently. Some nodes have the same name as they perform the same function but only differ in the type they support or apply to.
Hopefully the plugin search function can show all the matching entries.

[AlexeyAdamitsky]

I think it's a legacy node.

The two nodes were introduced recently. Some nodes have the same name as they perform the same function but only differ in the type they support or apply to.
Hopefully the plugin search function can show all the matching entries.

So, there are supposed to be two Range nodes? One for float values and one for vector values?

[jobigoud]

Yes there are two Range nodes, one for individual floats and one for textures. There is not one for vectors (float triplets). You will also find there are two "Binary math operation" and "Unary math operation".
This is on purpose, these nodes are very different since one runs on the GPU and the other on the CPU. And output type in Octane is strict. But if you need converting from float to texture you can use the nodes under Octane texture > Converters.

[AlexeyAdamitsky]

Yes there are two Range nodes, one for individual floats and one for textures. There is not one for vectors (float triplets). You will also find there are two "Binary math operation" and "Unary math operation".
This is on purpose, these nodes are very different since one runs on the GPU and the other on the CPU. And output type in Octane is strict. But if you need converting from float to texture, you can use the nodes under Octane texture > Converters.

Ahh, I see. It would be nice if Octane was more flexible with socket types like Cycles or Arnold. Otherwise, we'll need the same function node for different types of data. Which will bloat the nodes list. Which already is rather big.

Still search gives the Range node for the float data type. But in the Add menu I can find the Range node only for the texture data type. I think the naming of the nodes should be expanded like: Float Range, Color Range (or RGB Range). Not very elegant solution, but I don't see the better way, yet.