Summary
Pure variable getter nodes can be disabled through multi-selection but cannot be re-enabled when selected alone
What Type of Bug are you experiencing?
UI / Tools
Steps to Reproduce
- Open a Blueprint graph in Unreal Engine 5.8.
- Add a variable getter node and another node that supports Compile Options.
- Select both nodes.
- Right-click the other node and choose Compile Options > Disable (Do Not Compile).
- Confirm that the variable getter also becomes visually disabled.
- Select only the disabled variable getter and right-click it.
- Observe that Compile Options is not available.
- Select the getter together with another node, right-click the other node, and choose Enable Compile.
- Confirm that the getter becomes enabled again.
Expected Result
A variable getter that can be disabled through multi-selection should also provide a direct way to be re-enabled when selected alone.
Alternatively, Compile Options should not affect pure getter nodes if those nodes do not support the menu individually.
Observed Result
The variable getter becomes disabled when Compile Options is applied to a multi-selection.
However, when the getter is selected by itself, the right-click menu does not contain Compile Options, so it cannot be re-enabled directly.
The getter can only be restored by selecting it together with another node that supports Compile Options and using Enable Compile from that node’s context menu.
Affects Versions
5.8
Platform(s)
Windows
Upload an image
Additional Notes
This was reproduced in Unreal Engine 5.8 inside a Blueprint function graph.
The issue appears to be a UI/UX inconsistency: pure getter nodes can inherit the disabled state from a multi-node selection, but their individual context menu does not expose a corresponding option to restore the state.
Attached screenshots show:
- The context menu when the getter and another node are selected together.
- The context menu when the getter is selected alone.