Skip to main content

​
Cordial starts again

On 2026-09-24 Cordial started coming up as a flat grey window, signed in or not. Roblox had changed the settings document Cordial fetches at startup, and that document no longer starts the current client. Cordial now fetches the same settings document the Roblox client itself asks for. Measured on a fresh signed-out profile: the old document gave a grey window 10 times out of 10, the new one reached the Roblox landing page 10 times out of 10. Signed in, 3 of 3 launches reached Home. Your FastFlags still apply on top, as before. If this release makes things worse for you, CORDIAL_ENGINE_SETTINGS=0 in the environment puts the old document back — and please open an issue if you need it.

​
ARM64 (aarch64) builds

Cordial now builds for 64-bit ARM Linux: the Flatpak, AppImage, .deb and .rpm are published for aarch64 alongside x86_64, and Roblox is fetched for your architecture. There is no aarch64 Arch package yet, because there is no official Arch image for aarch64 to build it in. This is untested on real ARM hardware. Under emulation the client loads Roblox and gets as far as reading its settings; rendering, input and joining a game have not been seen working. If you run Cordial on an ARM machine, the maintainers would like to hear how far it gets, working or not.

​
Smaller fixes

  • Installing the Flatpak from the stable channel failed with Commit has no requested ref ... stable in ref binding metadata (#57). Fixed; this release is the first build published to stable with the fix.
  • Downloading a Roblox build in Settings → Version now shows its progress bar where you can see it, above the list rather than below it.
  • Deno installed with Homebrew or with deno.com’s installer is found even when it is not on the launcher’s PATH. Inside the Flatpak, the plugin error now points at Settings → Plugins → Download instead of a package you cannot install there.
  • Shorter text in the Roblox Build dialog and Settings → Version.
  • A cordial-bin AUR package that installs the prebuilt release, thanks to #60.

​
What is still broken

The signed-in startup freeze is not fixed. An early measurement looked as if this release’s settings change had removed it; later runs the same day froze 3 times in 10. If the client freezes on startup for you, the tracker still wants to hear about it. The client can still grey out when a text box takes focus, in chat or a game’s own text box (#53, #54). This is a different problem from the grey screen on launch, and it is not fixed. It has not been reproduced on a test machine; reports so far come from Hyprland. On first click, a text box’s cursor can land in the wrong place. Later clicks are right. A game’s DF FastFlags, such as DFIntTaskSchedulerTargetFps, can reset partway through a session, because the Roblox client refreshes those from Roblox’s servers on its own schedule. Still open from earlier releases: a crash after a second launch (#44), a freeze and crash leaving fullscreen (#39), a crash on first touch with a touchscreen (#36), a crash on launch on some machines (#35), no window on COSMIC, KWin or wlroots compositors (#38), a hang on exit (#52), pointer drift during camera drags on Hyprland (#56), and a rare crash just after startup (#63). VR is not supported.