
BulletDust
u/BulletDust

Running KDE Neon 6.6.4, Proton-CachyOS works fine under Steam. However if I select Proton-CachyOS under Heroic launcher, it doesn't matter what game I run, the game simply fails to launch. If I revert back to Proton-GE-Latest the game launches and runs perfectly.
Has anyone got Proton-CachyOS working under Heroic Launcher under a distro that's not CachyOS?
I've downloaded the mod from here:
https://www.moddb.com/mods/quake-3-arena-rtx-remix-mod
I added the game to Steam as a non Steam game, enabled Proton Experimental, added the pak0.pk3 to pak8.pk3 into the baseq3 folder, the game launches and runs perfectly but there's no RTX effects - it's just normal textures.
Has anyone managed to get this working under Linux with RTX effects? Video below:
So the Black Mesa RTX Remix has been released. I've followed the instructions here:
https://github.com/xoxor4d/remix-comp-projects/releases/tag/1.0-BlackMesa
I'm launching the game under Steam, using Proton Experimental - I've essentially added run-bms-rtx.bat as a non Steam game. However when I try to launch the game, the following happens:
I'm really keen to play this game, it looks fantastic. Anyone got any ideas? I've already tried adding the launch option:
WINE_DISABLE_HARDWARE_SCHEDULING
So I'm running KDE Neon User Edition 6.4.2, and before anyone says anything - I've been running this distro since 2018 and I've encountered very few issues, even running the Nvidia proprietary drivers installed via the Launchpad PPA.
Just getting that out of the way, it's not the point of this thread.
As evidenced by this point under the KDE Neon FAQ page:
Is KDE neon 64bit only? 🔗
Yes. As computers without 64bit have become increasingly rare, we have chosen to focus our resources on higher-quality 64bit builds.
Furthermore, KDE Neon has been 64bit only since ~2016. Looking at my kernel version, I see the following:
I'm not too sure when it happened, but I noticed today that I only have AMD FSR 3 Frame Generation as opposed to DLSS Frame Generation. Anyone Nvidia users noticing the same thing or could it be a result of the need to use SteamDeck=1 in the game's launch options?
As is common knowledge now, with the latest round of updates Valve successfully broke mouse capture running CS2 as Wayland native by setting 'export SDL_VIDEO_DRIVER=wayland' under cs2.sh.
I've read people claiming a workaround exists using gamescope, I'm running Steam via flatpak as well as gamescope via flatpak using the launch option:
gamescope -W 1920 -H 1200 -f -e --expose-wayland --force-grab-cursor -- %command%
The problem is: Upon doing so the 'visible' mouse pointer sits at the top corner of the screen, while an 'invisible' mouse pointer selects menu options when not in game - As can be imagined, not really ideal at all. Furthermore, the issue of mouse capture still seems to be
A couple of days ago the latest Nvidia 565.77's dropped under the Launchpad PPA, naturally I installed them and everything seemed top be running perfectly. On a whim I decided to launch a game of Black Mesa and hack through some more levels...
...Upon launching Black Mesa, my resolution was messed up on the Crowbar Collective splash screen and the game wouldn't progress any further before dropping back to the desktop. Watching MangoHUD (thank Gawd for MangoHUD) I noticed that it was reporting the game as using llvmpipe/Mesa as opposed to the usual Nvidia drivers, fps was around 9 fps before crashing back to the desktop.
I tried other games, every other game launched fine using the Nvidia d

Just before the 24.04 release, I had a problem out of the blue updating Flatpaks via Discover. Previously Flatpaks updated just fine, now whenever I try to update Flatpaks I get the error:
While trying to apply extra data: apply_extra script failed, exit status 256
If I open terminal and perform a flatpak update all Flatpak's update without issue.
I've tried issuing a flatpak repair, the result is:
Pruning objects
Erasing .removed
As far as I can tell, at least one Flatpak is trying to run a script called apply_extra, and the script fails to retrieve the needed data - But I'm not sure just what Flatpak is causing the issue and I don't know how to resolve it.
Running KDE Neo


