Skip to main content

​
Some settings now apply to a game that is already running

Changing these in Settings takes effect in the running game straight away:
  • mouse acceleration (cursor only, or cursor and camera);
  • background throttling;
  • closing Cordial when you leave a game;
  • carrying your login into links you open.
Settings that can only take effect when the game starts now say Applies at next launch under them: the title bar, GameMode, MangoHUD, shaders, audio output and the Graphics group (renderer, graphics optimisation, frame pacing, controllers). Hand edits to shell.json are picked up the same way while a game is running. The Settings window itself does not refresh when another program edits that file, and saving from it writes its own copy back, so edit one or the other, not both at once.

​
The Roblox build is shown in Settings

The updater settings show which Roblox build this Cordial installs, for example “x86_64 (this computer)”. It is information only. Running the build for the other architecture would need translation, and on the hardware tested that route falls back to software rendering, so it is not offered.

​
What is still broken

The signed-in startup freeze is not fixed. It still happens on some launches, in bursts. Resizing the window does not redraw the game until you stop dragging. A Roblox version released only for ARM64 is not shown on x86_64 machines, so the updater may not mention a newer version that exists for another architecture. The screen may still grey out when a text box takes focus in fullscreen (#53), and games that put the cursor in a text box for you may not accept typing. A game’s DF FastFlags, such as DFIntTaskSchedulerTargetFps, can reset partway through a session. Some games show the mobile (touch) interface. The cordial, cordial-bin and cordial-git packages on the AUR are not published by this project. Use the release package or the signed pacman repository instead. Still open from earlier releases:
  • 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 some COSMIC, KWin or wlroots setups (#38; it opens on KWin on a Steam Deck);
  • a hang on exit (#52);
  • pointer drift during camera drags on Hyprland (#56);
  • a rare crash just after startup (#63).
The notes for 0.17.0 to 0.21.0 list a crash after a second launch (#44) here. That was fixed in 0.16.0, and those lists were wrong to carry it forward. ARM64 builds are still untested on real hardware. VR is not supported.