Gradient map node bug
Posted: Fri Feb 24, 2023 2:18 pm
Hi, there is 2 problems with the gradient node, find it in the 27.8, but is also present in the 27.10 version.
1. When you create a gradient map node it comes by default with only two flags, the start and the end but the node itself has 4 inputs, start, 1, 2, end.
1 and 2 being inactive and doing nothing.
If you add let's say 2 flags, it had two new inputs, 1 and 2 become active while the new 3 and 4 are inactive and useless, and so on...
2. There is a limit of 14 in the number of flags socket on the node itself, as you can see here, there is only 14 ( the 13 and 14 still being inactive and useless) socket, while the gradient as a lot more. This is a kind of extreme situation, but since we don't have a more effective way to randomly apply a large number of maps to instances it's the only solution.
Anyway it shouldn't happen, either the number flags shoulde be limited, or the number of socket should be the same.
Thanks !
1. When you create a gradient map node it comes by default with only two flags, the start and the end but the node itself has 4 inputs, start, 1, 2, end.
1 and 2 being inactive and doing nothing.
If you add let's say 2 flags, it had two new inputs, 1 and 2 become active while the new 3 and 4 are inactive and useless, and so on...
2. There is a limit of 14 in the number of flags socket on the node itself, as you can see here, there is only 14 ( the 13 and 14 still being inactive and useless) socket, while the gradient as a lot more. This is a kind of extreme situation, but since we don't have a more effective way to randomly apply a large number of maps to instances it's the only solution.
Anyway it shouldn't happen, either the number flags shoulde be limited, or the number of socket should be the same.
Thanks !