"New Luau Type Solver" beta feature bugging script editor usage

When the New Luau Type Solver is active. The very top line turns blue in the editor, preventing the blue underlines from appearing, as well as preventing any autocompletes.

Only one script contains the weird blue line, while all other scripts suffer from the same loss of usage regarding blue underlines and completion.

Beta Features Enabled

  • Dragger QoL improvements
  • Gamepad Emulator
  • Improved Constraint Tool
  • New Luau Type Solver
  • New Studio Camera Controls
  • Next Gen Explorer
  • Next Gen Studio Preview
  • Studio Solid Modeling Improvements
  • Unified Lighting

Using Windows 11 Home on Dell G15 laptop with NVIDIA RTX 3060 laptop gpu. (doesn’t seem to be a hardware issue)

Reproduction Steps

  • Create a script that will create the wavy blue warning lines
  • Enable New Luau Type Solver beta feature
    image

Expected behavior

Expected Results
image

Did you hover over it and saw what it says?

Usually, a whole bar in the first line using the new solver indicates that the initial type inference did not complete successfully. But that’d be red, not blue. Oh well, I don’t use light mode, I don’t know what blue means.

It does not say anything when hovered, the entire line is highlighted no matter if it has a scripts/comments on it or not.

In default light mode blue are warnings, while red are errors

Hi @realqwerty64 can you open Script Analysis Widget and see what it shows?

What @Vanniris said it correct, usually it means the type solver hit internal unrecoverable error so ScriptEditor cannot provide any language features afterward.

To clarify a bit more clearly, an orange bar with a corresponding error in the script analysis window indicates that type inference did not complete (the error in the script analysis window should say this too). A blue bar indicates that an internal compiler error (ICE) occurred. These are both indicative of bugs in Luau that we’ll want to fix, but they do mean different things, and the latter can occur even in the old solver (though we worked hard to tackle all the sources of ICEs in the old solver before we started working on the new one).

As far as I know, the script editor in Studio has not been reporting the messages associated with ICEs for a long time, so there’s no way for you to see the corresponding error in Studio (though, frankly, it’d be inactionable for you, and is really only useful for us in fixing the problem). We have a fix in the works that should make the messages associated with ICEs accessible in Studio soon though.

1 Like

The error doesn’t seem to be appearing this morning.

I’ll update this thread if ever I encounter it again though.

1 Like