Install vkBasalt
Which one you need depends on how Cordial was installed. A host package is invisible to a Flatpak build.- Fedora
- Arch
- Flatpak
distrobox, or layer it with rpm-ostree.Change the effects
The first time you turn the switch on, Cordial writes<profile>/vkBasalt.conf in that profile’s data directory with sharpening and anti-aliasing at vkBasalt’s documented defaults. Cordial never rewrites this file again. Edit the effects list, the sharpening strength or anything else vkBasalt supports and your changes stay. Once vkBasalt is detected, the settings row names the exact path for your profile.
The full key reference is vkBasalt’s own: vkBasalt.json.in.
Toggle the effect on and off
The generated config setstoggleKey = Scroll_Lock, not vkBasalt’s own Home. Home is a Roblox chat key (it jumps to the start of a line), and vkBasalt does not care which window has focus, so Home would toggle the effect every time you typed a message.
On Cordial’s default Wayland backend the toggle key does nothing. vkBasalt reads a real X11 keyboard and only when
$DISPLAY is set, and a Wayland session sets WAYLAND_DISPLAY instead. The generated config sets enableOnLaunch = True for this reason: the effect is on from the start and stays on. The key works on Cordial’s X11 backend, or when XWayland is running alongside a Wayland session.What is checked and what is not
- The layer loads. With
ENABLE_VKBASALT=1andVKBASALT_LOG_LEVEL=info, the Vulkan loader insertsVK_LAYER_VKBASALT_post_processingand vkBasalt logs the config Cordial generated. - The effect is visible on the landing screen, where edges are visibly sharper. The difference is modest on that mostly flat screen, and it was not checked against in-game 3D content.
- Cost: on the landing screen, CPU for the whole client went from about 6.7% with shaders off to 7.0 to 7.1% with them on. That is one screen and one input pattern, not a claim that vkBasalt costs nothing.
- Untested: AMD and NVIDIA GPUs. Everything above ran on the Mesa driver.