Page 1 of 1

[Kovarex] [2.0.31] Crash setting signal while placing parameterized blueprint (Util.cpp:95)

Posted: Sun Jan 19, 2025 5:38 pm
by elmbald
Found when reporting viewtopic.php?f=7&t=126134

What did I do: placed a parameterized blueprint, then before setting or accepting any parameters, double clicked off to the side of the Parameter UI (in my case just one tile to the right of where the blueprint was set to place initially). This opened up a different parameter UI, which I set without issue, bringing the original Paramater UI back into focus. When testing in the "Testing" Scenario, this occurred on clicking the signal rather than on clicking to confirm the signal.
After setting first blueprint part
After setting first blueprint part
01-19-2025, 12-11-45.png (90.04 KiB) Viewed 348 times
just before crash, clicking the green checkmark in 'select a signal' causes it.
just before crash, clicking the green checkmark in 'select a signal' causes it.
01-19-2025, 12-13-35.png (808.21 KiB) Viewed 348 times
Crash Message
Crash Message
01-19-2025, 12-14-32.png (19.73 KiB) Viewed 348 times
What happened: Placing a second parameterized blueprint from the stack causes the game to crash when setting the parameter.

What would I expect to happen: either disable stacking of parameterized blueprints, or for this behavior to not cause a crash.

Does this always happen? When following the reproduction steps, this will always happen, Specifically on setting the signal, values do not cause any issues

BP used to reproduce:
0eNqFUdtKxDAQ/ZVlntNlWzcLDfjiFwiKLyJL2kYN5FKTdLGU/Lsz3W1FRSUvkzkzc86cmaAxg+qDdgnEBLr1LoJ4nCDqFycN5Zy0CgQQkqRLRetto51MPkBmoF2n3kGU+YmBckknrc4D5s94dINtVMAC9tcgBr2P2OsdMeK8oirLLWcwgjjsthyJsC0Fb46NepUnjT1YGFVLPfFrjOSLKgbP2iQVvmcvUnoZMEC82KGEt0EalIx554PF5YnUUg1JFHA9JwZyCtfFl2npdcaZI409TdYdrCx3s5Wbe0IYIb8QoyGuW034X03ObOW72MyWQED5Q8CDxFMDadZJWcx/np6BkY3Cc8ONjLrd3C76EDnharMmfqjqfV1zvudVfVXm/AHrrL+t

Re: [Kovarex] [2.0.31] Crash setting signal while placing parameterized blueprint (Util.cpp:95)

Posted: Mon Apr 14, 2025 12:27 pm
by kovarex
Hello, thanks for the bug report, it has been fixed for the next release.