Page 1 of 1

[2.0.13] Parameterized constants are force-merged with other constants based on default value

Posted: Sun Nov 03, 2024 4:33 pm
by Theikkru
Not quite sure if outright bug or missing functionality, but feels broken: currently, it seems impossible to set the default value for a parameterized constant to any value used elsewhere in the blueprint without causing those other instances of the value to also become parameterized.
For example, consider the following setup:
4.png
4.png (607.17 KiB) Viewed 535 times
1.png
1.png (282.18 KiB) Viewed 535 times
2.png
2.png (55.5 KiB) Viewed 535 times
3.png
3.png (50.56 KiB) Viewed 535 times
Let's say I want to set the default value for the parameter 0 in the constant combinator to 1:
5.png
5.png (555.57 KiB) Viewed 535 times
As soon as I apply this change, that parameterized value is force-merged with the constant 1 in the other two combinators, effectively breaking the blueprint:
6.png
6.png (633.87 KiB) Viewed 535 times

Re: [2.0.13] Parameterized constants are force-merged with other constants based on default value

Posted: Sun Nov 03, 2024 4:41 pm
by Loewchen

Re: [2.0.13] Parameterized constants are force-merged with other constants based on default value

Posted: Sun Nov 03, 2024 5:33 pm
by Theikkru
Reposted as an idea/suggestion.