!hzgkCxLtCOTmFXGauj:nixos.org

NixOS Gaming

397 Members
Gaming things, my hands are typing words.108 Servers

Load older messages


SenderMessageTime
8 Aug 2025
@aidalgol:matrix.orgaidalgolcorrect20:49:35
@aidalgol:matrix.orgaidalgolbut before the steam wrapper change, trying to run a second instance would just raise the existing instance's window.20:50:10
@k900:0upti.meK900 As in, the "runs two instances" behavior is wrong 20:50:21
@k900:0upti.meK900 And the expected behavior is to activate the existing one 20:50:29
@aidalgol:matrix.orgaidalgolactually, that might be an intentional change.20:50:40
@aidalgol:matrix.orgaidalgolOK, how the hell do I build a Windows executable? I need to package this thing for GOG Galaxy support in Heroic to work properly. https://github.com/imLinguin/comet/tree/main/dummy-service22:10:14
@aidalgol:matrix.orgaidalgolNone of the guides for normal cross-compilation in nixpkgs quite fit this odd scenario.22:10:54
@aidalgol:matrix.orgaidalgoli.e. https://wiki.nixos.org/wiki/Cross_Compiling and https://nix.dev/tutorials/cross-compilation.html by my reading are describing setting up a dev environment for cross compiling using nixpkgs, not packaging, say, a Windows executable for use in an x86_64-linux NixOS package.22:15:33
@aidalgol:matrix.orgaidalgol Comet's upstream releases include GalaxyCommunication-dummy.exe, but our comet-gog package does not. I think this .exe was added upstream sometime since the nixpkgs package was added. 22:18:14
@aidalgol:matrix.orgaidalgol * Comet's upstream releases include GalaxyCommunication-dummy.exe, but our comet-gog package does not because it only builds comet. I think this .exe was added upstream sometime since the nixpkgs package was added. 22:18:27
9 Aug 2025
@aidalgol:matrix.orgaidalgol SigmaSquadron: Is there anything we can do around the heroic package to get people to bother nixpkgs people first rather than going straight to upstream? This happens a lot. 02:06:48
@sigmasquadron:matrix.orgSigmaSquadronCould patch the sources so whenever we get an error message, it provides a link to Nixpkgs instead.02:22:45
@aidalgol:matrix.orgaidalgolYeah, maybe I should do that. I've been hesitant to modify the upstream source much.02:57:14
@aidalgol:matrix.orgaidalgol Regarding the Windows helper executables, I have packaged them in PR#432183, and I'm not sure the way I have done so is acceptable in nixpkgs, so I would really appreciate a review on this. 05:42:20
@aidalgol:matrix.orgaidalgolIt's a rather odd scenario because they're Windows dependencies for a Linux application, for games run under Proton.05:42:56
@k900:0upti.meK900 @aidalgol pushed to your PR 05:55:48
@k900:0upti.meK900Can you test05:55:49
@aidalgol:matrix.orgaidalgolYup, fix still works.05:59:40
@k900:0upti.meK900OK hold on I noticed a thing06:20:19
@k900:0upti.meK900Pushing a fix now06:20:21
@seapat:matrix.orgseapat set a profile picture.14:23:03
10 Aug 2025
@matthewcroughan:defenestrate.itmatthewcroughan changed their display name from matthewcroughan to matthewcroughan @ WHY2025 (DECT: 8793).11:43:22
@rein:rein.icuRein It seems that the STEAM_EXTRA_COMPAT_TOOLS_PATHS is properly set:
❯ steam-run printenv | grep STEAM
STEAM_EXTRA_COMPAT_TOOLS_PATHS=/nix/store/d9xqr8kg4a483ywfb0grl95z6i19vzp1-proton-ge-bin-GE-Proton10-10-steamcompattool/
14:37:53
@rein:rein.icuReinno idea why I don't get the compatibility tools in steam14:38:24
@rein:rein.icuReinimage.png
Download image.png
14:39:10
@rein:rein.icuReinOkay, I've deleted all files related to Steam and it suddenly works. I have no idea what was the issue tho14:45:09
@rein:rein.icuRein I've rebuild the system after that and the compatibility tools are not there anymore ;-; 14:47:50
@rein:rein.icuRein* I've rebuilt the system after that and the compatibility tools are not there anymore ;-;14:48:36
@rein:rein.icuRein It's probably something with Steam, since it worked after deleting $HOME/.local/share/Steam and $HOME/.steam 14:50:09
@witchlliee:matrix.orgEllie she/they

I'm having this warn with steam:

pressure-vessel-wrap[9433]: W: Found more than one possible libdrm data directory from provider
pressure-vessel-wrap[9433]: W: "run/opengl-driver-32/share/drirc.d" is unlikely to appear in "/run/host"
pressure-vessel-wrap[9433]: W: "run/opengl-driver/share/drirc.d" is unlikely to appear in "/run/host"
pressure-vessel-wrap[9433]: W: Found more than one possible drirc.d data directory from provider
pressure-vessel-wrap[9433]: W: "run/opengl-driver-32/share/drirc.d" is unlikely to appear in "/run/host"

Anyone knows what is this about?

15:48:29

Show newer messages


Back to Room ListRoom Version: 10