Constant combinator blueprint parametrization failing
Constant combinator blueprint parametrization failing
Setting them to different values works fine.
This becomes a very weird problem later if you for instance create a blueprint initially with different values and then edit it and set the params to 0 (at least two). Even if you don't get any error, some parameters just vanish after saving the blueprint and the pasted-and-built result has incorrect values. Even the non-vanished no longer show the hover help showing where they are. That is how I found it initially and isolated it to the combinator alone failing in this way.
This is IMO a bug.
Re: Constant combinator blueprint parametrization failing
Could we have at least "do not merge" checkbox next to the parameter so that it is never merged?
We could start with different values (even though it is really ugly hack) and then have it never merged after.
We could start with different values (even though it is really ugly hack) and then have it never merged after.
Re: Constant combinator blueprint parametrization failing
This is beyond the scope of a simple feature this was originally supposed to be. Parametrization mostly collects just values and does not care where are they coming from so even if they would not be merged there would be no way to tell which new value should be applied to which variable during apply stage as they are identified by their old value.
Re: Constant combinator blueprint parametrization failing
that's a pity, such a good feature for geeks and limited this wayboskid wrote: Sat Mar 01, 2025 8:45 am This is beyond the scope of a simple feature this was originally supposed to be. Parametrization mostly collects just values and does not care where are they coming from so even if they would not be merged there would be no way to tell which new value should be applied to which variable during apply stage as they are identified by their old value.

But I understand you might have other priorities and doing it right might be in conflict with making it simple

What about adding a warning then when you set more values in the parameters to the same value?
Something like "setting equal values for multiple parameters will merge these values into one parameter when you save the blueprint". So that people know where the limit is and that they will run into problems when doing so.
This would be a simple change to the GUI. What do you think about it?