Skip to main content

​
What you can do now

  • A touchscreen no longer crashes Cordial. Touching the game used to end the client at once (#36). Tested here with a simulated touchscreen, since none was available: taps reach the game and the client stays up. Not yet confirmed on a real one.
  • Text boxes work in fullscreen, and with Title bar set to Hidden. The editor used to never appear there, and leaving fullscreen left the title bar missing and the game at fullscreen size (#53, #39). The cost is a one-pixel black line at the bottom of the window in those two modes, which keeps the compositor drawing Cordial’s own window. CORDIAL_VISIBILITY_ANCHOR=off turns it off. Measured on sway and on GNOME’s Mutter 50.5; not on KDE or Hyprland.
  • Settings → General shows what applies now. While a game runs, a Running now group lists which settings change the running game at once and which wait for the next launch.
  • The launcher and the game talk over Cordial’s runtime protocol (cordial.runtime/1, the one the cordial-protocol crate implements). Settings reach a running game the same way as before. Close the launcher window and the game keeps running; open Cordial again and it reconnects to it.
  • Text boxes use the right Source Sans weight. Boxes set to SourceSans, SourceSansBold or SourceSansLight were drawn in Builder Sans regular.
  • NixOS: Cordial’s checks find Vulkan drivers in /run/opengl-driver, so they stop warning that none is installed.
  • Stutter reports are measurable. The [cordial] health: line printed every 30 seconds now carries frame-gap percentiles (p50, p95, p99). Keep the mouse moving while you read them: Roblox drops to one frame a second when it gets no input.

​
What is still broken

The signed-in startup freeze. Roblox can stop drawing on the loading screen after sign-in. The launcher restarts a client stuck that way, up to twice. Movement keys can be dead after joining a game. W/A/S/D do nothing until the character respawns. Move the mouse while the place loads and it does not happen. A fix that does this automatically is written and has not passed its test yet. #29 If the launcher process itself is killed, the game goes with it. Closing the launcher window is fine; killing its process is not, because the game’s output still runs through it. On the Nintendo Switch, games crash a few seconds in, when the camera turns, inside what looks like the graphics driver. #85 The rest of the list in the 0.24.0 notes still applies.