1.1.9 - Smoother joins, input methods, Appimage fix

Joining games no longer freezes, input methods work, and fixed Appimages!

Graphics:

• Fixed the freeze of up to 12 seconds on the home screen after pressing Play (up to 22 seconds on X11). The Vulkan driver now presents to a surface of its own, the way it does on Android, so the old frame is let go the moment a game starts
• The home screen stays on screen while a game loads, instead of a black screen in between. Stud's own startup no longer flashes black either
• A GPU crash no longer takes Stud down with it: the game recovers and carries on, instead of the render host crashing while the driver reports the lost device
• Fixed a render host crash when the graphics driver refuses a descriptor set the game asked for
• Stud loads the Vulkan driver once, through volk, instead of opening it a second time just to create the window's surface

Keyboard and chat:

• Input methods work in text boxes: fcitx5, IBus and others can compose Chinese, Japanese, Korean and more into chat and search, on Wayland (text-input-v3) and on X11 (XIM). The text being composed is shown in the box, and the candidate window opens at the caret
• The input method is only active while a text box is focused, so it never eats the keys you play with, even if you left it in a composing mode. Password boxes keep it out entirely

The app:

• Fixed the home screen freezing after leaving a game. Stud now resumes the home screen the way the real app does when you come back from one
• Fixed the home screen running at 1 FPS for about 10 seconds after launch. Reading your saved login no longer holds up the engine's graphics while it starts
• With Discord presence on, joining a game no longer waits on the lookup of its name and thumbnail
• The engine is told what connection you are actually on (WiFi or not), in the app's own terms, instead of always "WIFI"

Stud:

• The AppImage bundles its own glibc, so it runs on older distributions again (tested down to Debian 12).

Known bugs:

• On NVIDIA, a freeze of a few seconds may happen, rarely, mid-game. Stud recovers from it on its own, and it is still being investigated.
• MangoHud 0.8.3-rc1 crashes Stud if you stop its logging while its HUD is visible (a MangoHud bug, flightlessmango/MangoHud#2053). Hide the HUD before stopping logging or update to MangoHud 0.8.4 (Available in nobara-44's copr, for fedora folks)

Warning

Stud is still a work in progress: it boots, logs in, renders the real app and joins real games, and it also breaks in ways nobody has measured yet. A log from a machine that isn't ours is the most useful thing you can send (the tray's Export logs puts a session in one file)