"Device Emulation" now stuck in fullscreen resolution, and cannot escape

Bug Reports Studio Bugs
#1

System Information
Windows 11 Version 10.0.25936 Build 25936, AMD Ryzen 9 5950X 16-Core Processor, NVIDIA GeForce RTX 4090, 32GB DDR4 RAM
Studio Version
Version 0.592.0.5920587 (64bit)

Since I turned on the Device Emulator onto a custom 4K mode with “Actual Resolution” and clicked inside, I get locked into the fullscreen emulation and cannot escape (including by pressing Esc) without spamming F11 and hoping to click the “X” button. Clicking out of the window will minimize it as expected, but as soon as I click inside of the studio window again (no matter where I click, Explorer or the Game Window itself) it locks me back into fullscreen.

I managed to resolve this by setting a keybind to access the Device picker and removing the 4K device, but this was still not intuitive.

Expected behavior

I should be able to click out of the window or press the Escape key, and then click anywhere outside the Game Window to change the display mode back to “Fit to Window” or another option.

4 Likes
#2

Hey there! I’m in the same boat too (thank you for bringing attention to this!) Would you possibly be able to explain how you set up the keybind to change the setting? I managed to exit out of the emulator, however when I re-enable I’m automatically stuck in fullscreen again…!

1 Like
#3

Thanks for the report! We’ll follow up when we have an update for you.

4 Likes
#4

i just ran into this as well. a escape keybind would be nice

2 Likes
#5

Yeah I cant exit out of it either why didnt they add something where you can exit out of it

It doesnt make any sense

1 Like
#6

Had this exact issue.

Another way to resolve it is by:

  1. Pressing the windows key.
  2. If roblox is in fullscreen, press f11.
  3. Quickly drag the top bar for roblox studio so it makes it smaller.
  4. Click the desktop
  5. Quickly double click “Test” tab.
  6. If its gone back into the fullscreen state, press the windows key again.
  7. In the test tab, click “Device”.

Hopefully this works for others until roblox manages to fix it.

3 Likes
#7

Hi! This will be addressed when we revise the Studio emulator. In the meantime I’d suggest using the workaround you’ve described. Thanks again!

2 Likes