Blueprint details and sub-level details behave inconsistently \ 蓝图细节和子级别细节表现不一致

Development Pipeline & Plugins
, ,
1

蓝图细节和子级别细节表现不一致

如视频BP.mp4，当子级别的参数回车之后，会导致取消选择，从而需要借助鼠标再次点击，在频繁调试参数的时候很麻烦

预期：和BP细节层级逻辑对齐，不需要借助鼠标就可以频繁灵活的修改数值

Blueprint details and sub-level details behave inconsistently

As shown in the video BP.mp4, pressing Enter after modifying sub-level parameters deselects the field, requiring an additional mouse click to continue. This becomes cumbersome during frequent parameter adjustments.

Expected behavior: Align with the logic of the main BP details panel, allowing flexible numerical modifications without relying on mouse input.

2

Hi there,

Thank you for reporting this inconsistency. I have tested this on my end and can confirm this behaviour is reproducible, but there are workarounds.

This behaviour appears to only occur on components added to a blueprint class through the blueprint editor, and then editing the value on an instance that is placed in the level.

This does not happen when:

  • The component is added to a class natively in C++, and then the value is edited on an instance in the level.
  • The component is added to an instance after it has been added to a level.
  • In the blueprint class editor viewport, when editing the default value.

My recommendation at this stage would be to move the component to C++ if possible, which should resolve this issue for you. With that being said, I am happy to elevate this to the Epic team to see if this is something they wish to address in the future.

Let me know if this workaround is suitable for you.

Thanks,

Thomas

3

Thank you! I’m not a programmer, so I can’t use C++, and therefore I’m more looking forward to an official fix from Epic.

4

Hi there,

Thank you for letting me know. In that case, I will file this as a bug report to the Epic team.

I will be in touch again when I have a public tracking link available. Just as a heads up, this may be in a few weeks when the Epic team return from their summer break.

Thanks again,

Thomas

5

Hi there,

Here is the public bug-tracking link for this report. Going forward, this link will provide the most up-to-date information about this issue. If you have any additional information you would like to provide about this issue, please feel free to get back in touch.

Thank you again for your report.

Regards,

Thomas