Early Access 2 | CTRL + Spacebar does not open the Content Drawer

Development Cinematics & Media
,
1

Hi All,

I just installed UE5 Early Access 2 and the keyboard shortcut ctrl + spacebar is not working to open the Content Drawer. Is this a known issue? Is there a workaround? Thanks!

1 Like
2

Was pulling my hair out because of this as well… When I Ctrl space a little bar show up at the bottom but not the entire content drawer. Turns out I have to pull the top edge of the little bar up to show the content draw. Hope this helps. Cheers

1 Like
3

I’m having the same issue. When I try to remap the binding, the ctrl+space combination doesn’t even register, it only shows ctrl. Tried with two keyboard languages (English and Czech).
When I set to to ctrl+enter for example, it works fine.

1 Like
4

Hi All,
Looks like the Binary version from Launcher does not support an international keyboard other than US and UK.

This may be not recognised in Windows 10, also if you change the settings for the touch keyboard to a split keyboard, nothing works!.

You have to remember that windows 10 intercepts sequences Control +v (paste) etc so many functions cannot be mapped.

1 Like
5

I had the same problem. Turns out, if you are using microsoft powertoys, it has a peek function whose shortcut is ctrl+space which overrides all others. Just disable it or change the shortcut.

8 Likes
6

Thank you Harshsr

1 Like
7

Thank you!

1 Like
8

Yes, that worked! Thanks

1 Like
9

Installed UE5.4 Ctrl+Space Bar does not work and does not allow Space Bar to be linked.
“R” scale also does not work
There is also UE5.3.2 and UEFN - everything works there.
What could be the problem?

1 Like
10

I found a problem, it lies in the regional standards of Windows.
The same problem happened with Datasmith that year.
In the Windows settings you need to change the “Divide separator” from “,” to “.”

1 Like
11

UE5.4 ctrl+space can open the content drawer but can not close it. Can you explain more? Maybe I changed a different setting.

1 Like
12

did you find a fix ?

13

There is no fix. I tried to engine source code to fix the issue myself, but the build is too long for my PC. I decided to wait.

Update: It is fixed in the 5.5 preview.