R keybind for builds wont place unless blueprints already out

Development Programming & Scripting
,
1

I’m having an issue where the R keybind, which I use for stairs, doesnt work unless my build blueprints are already out, just clicking the R key by itself doesnt pull out stairs to build them
(me and Hazo have the same issue, he posted a few days ago)

  • R keybind for builds wont work unless blueprints already pulled out and active

  • i made sure everything else is unbound from R, it’s purely only bound to Stair

  • resetting all binds doesnt work, changing gamemodes or creative maps or restarting game or pc doesnt help or fix it

  • it’s only the R key, everything else works, and the key itself works, it still registers and works(as you can see in this message)

  • unplugging keyboard doesn’t fix

  • i know there’s been keybind issues recently, such as the editing cancels sprinting, is it related to that?

2

It does sound like something specifically tied to how the R keybind interacts with build blueprints, since everything else on your setup works fine. From what you described, it’s likely not a hardware problem but more of an input mapping or blueprint reference issue. I noticed a really similar discussion where another user reported the same behavior the R keybind wouldn’t trigger until a blueprint was already active. You might want to check it out here: https://forums.unrealengine.com/t/my-stairs-wont-place-when-i-press-r/2658091