Roblox Studio Place Not Loading When Beta Features Are Enabled

Bug Reports Studio Bugs
,
1

When opening a specific game in Roblox Studio with beta features enabled, the place fails to load correctly:

  • The skybox turns completely black.
  • The viewport does not render anything.
  • UI tabs and buttons become unresponsive.
  • Attempting to close the place leaves Studio frozen in an open state, requiring Task Manager to force quit.

Disabling all beta features resolves the issue, and the game opens and functions as expected.

Expected Behavior:

The place should load normally, including:

  • Rendering the full skybox and environment.
  • Loading all game assets (terrain, models, UI, etc.).
  • Allowing interaction with Studio tabs, buttons, and properties.
  • Letting the user close the place or Studio without needing to force quit.

Reproduction Steps:

  1. Open Roblox Studio.
  2. Enable beta features (I have every feature enabled)
  3. Open the affected game
    • The skybox remains black.
    • Tabs and interface are unresponsive.
  5. Attempt to close Studio.
  6. Studio does not close and must be terminated through Task Manager.

Images

Black screen and frozen UI

Not loading
Not loading1920Ă—1027 70.6 KB

Studio doesn’t close properly

Not Closing
Not Closing2560Ă—1369 64.8 KB

My friend also experiences the same issue

Friend
Friend2559Ă—1347 246 KB

Expected View

Expected
Expected1920Ă—1027 103 KB

System Information:

  • Operating System: Windows 11 Pro
  • Roblox Studio Version: Version 0.675.287.6750000 (64bit)
  • Graphics Card: RTX 3080 TI
  • RAM: 32GB
  • Processor: 12th Gen intel - i7

Beta Features Enabled:

  • All available beta features are enabled.

A private message is associated with this bug report

2

Hi JPSpiek,

Thank you for sending over that place file for debugging. After some digging (bi-sect the beta feature…) with the place file, it seems related to the “New Luau Type Solver” beta feature.

You can try to disable that to see if that solve the issue for you as well. I can move the ticket to the corresponding team for further investigation.

Thanks!

1 Like
3

Yes, disabling the “New Luau Type Solver” fixes the issue.

Thank you for your reply, I appreciate it!

4

Based on the description, this is likely being caused by some severe performance edge cases from type inference, which the New Type Solver is more prone to as we’re working through these issues. You can avoid the problem today by opting out of using the New Type Solver while we continue to work on these issues. In the interest of making our tickets manageable, I’m closing this as a duplicate of New Luau Type Solver - Type Solver Doesn't Activate.