Search results

An observation: both native and windows build in wine sometimes pause at "Planet renderer" loading stage and hog CPU for a minute, not updating window frames (i.e. Hyprland notifies that window is not responding). And sometimes they do not and load almost instantly. Output pauses after this...

For Hyprland: windowrule = float on, match:title ^Kitten Space Agency.*$ The trick is to make the main window big enough on creation. Either float or spawning on an empty workspace works. Unfortunately, KSA windows do not have app-id or xdg tags set yet, so only a title-based rule is possible...

Yeah, linking libVulkanEx.so was probably a mistake, it's better to link system's libvulkan.so.1 into ./libvulkan.so just to satisfy current build of KSA. But KSA should search libvulkan by a versioned name. Unversioned .so names are for development and compilation, compiled applications are...

v2026.2.30.3638 is available, gzipped ) ...it does not start, can not find .NET You must install .NET to run this application. App: /home/psycho/games_lin/KSA/ksa_v2026.2.30.3638/KSA Architecture: x64 App host version: 10.0.0 .NET location: Not found The following locations were searched...

Try multiple times, it varies.

Saved data from /sys/class/drm/card1/device/devcoredump/data after GPU mooncrash, ~500K uncompressed. Is it of any use for devs?

Thanks, it gave me a clue. Perhaps the game interpreted being initially spawned in a small tile as having a small screen, all downhill from that. I wrote a borked floating rule. Spawning on an empty workspace (or writing a correct floating rule) seems to do the trick. Glitches on clouds...

On Hyprland KSA has serious scaling/mouse position issues and tries to randomly spawn dialogs into separate non-child windows, making a mess. Here, for example a configuration popped into separate window after attempting to interact with drop-down lists. This window is not a child of the main...

Neat! As @SSDeveloper said, beautifully hacky. OK, so now I have a confirmation that the glitches are KSA@AMD issues, not Wine/Debian or anything of that sort of issues. AMD is focusing on RADV, so the future is bright.

Side question, why isn't tarball compressed? Even default gzip gives 0.79 size, default xz gives 0.68, easier on traffic. BTW, ksa-linux download page has a cool style.

Hm... ksa_v2026.2.18.3622 It tried to find [lib]vulkan.so in current dir and failed, there were none in the archive (there's ksa_sign.bat lol). I linked /usr/lib/x86_64-linux-gnu/libvulkan.so.1 -> ./libvulkan.so, got this: :~/games_lin/KSA/ksa_v2026.2.18.3622$ ./KSA (KSA:3): dconf-WARNING **...

https://ksa-linux.ahwoo.com/ Oh yes! Downloading...

KSP provided an archive with binaries and data, it just worked. Although, data/binaries/configs/saves were mushed together, that isn't very nice. If KSA would support XDG hierarchies to search for data and configs, a bare minimum installation procedure would be enough (i.e. to /usr/local/...

Hell yes! History in the making! In more ways than one.

Tried wine-devel 11.2 and KSA v2026.2.4.3423. Compared to wine-staging 11.1 and KSA v2026.2.2.3396, the game loads much faster and no longer crashes when approaching the Moon. Still no terrain textures whatsoever. Edit: It was a lucky launch. All other attempts still had stuck loading with high...

Updated https://forums.ahwoo.com/threads/one-true-linux-thread-tm.144/post-1840 It's alive! ...somewhat. At least it has a chance to not crash. It launches with 2k settings and full solar system. Overall it has about 0.4 chance of startup without crashing before showing gameplay. It 100%...

The sudden shutdown seems to be due to PSU not having a margin for GPU's power spikes. KSA seems to be the only thing on my system straining it this hard. Well, while I wait a new PSU, and since the same memory error also happens on eGPU, I tried fixing it back on iGPU with installing Vulkan SDK...

Finally got TH3P4G3 Thunderbolt 4 dock and a Radeon RX 9060 XT 16Gb GPU. It seems to work out of the box, hotplugged (Debian sid, Hyprland). Anything launched with `DRI_PRIME=1` renders on it! But KSA... It started once, showing VRAM usage this time (it didn't on Intel iGPU), showed initial...

Answering my own question, and in case anyone finds it useful: TH3P4G3 Thunderbolt 4 dock and a Radeon RX 9060 XT 16Gb GPU work out of the box, hot-plugged (Debian sid, Hyprland). Any app started with `DRI_PRIME=1` renders on external GPU willy-nilly, confirmed by `gputop`.

More attempts to launch KSA on Intel iGPU convinced me that the "protected memory" crash is not due to memory. I never even attempted to start with full solar system before, but recently I did. KSA easily took up to 6G VRAM, all while other apps amounted to another 1.5G. So shared memory works...