Change:
<del> { stdenv, steamArch, fetchurl, }: </del> <ins> { stdenv, fetchurl }: </ins> stdenv.mkDerivation rec {

Discussion:
This commit breaks all my 3d games in Steam. They start, they react, but graphics is terribly broken - nothing can be seen other than pink color all over sreen with some artifacts. Reverting this commit fixes the issue. I have Intel integrated card 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Commit steam: switch to the newer steam-runtime packaging Valve has started releasing tarballs of the steam runtime. It seems a lot easier to download and extract a single tarball than to download a buncha debs, extract them, and splat em around a bit. Let's just use the runtime they build. It's a buncha random binary packages anyway. Also, the download url for their debs broke, so there's that too.
Ping.
I have seen graphics issues on an AMD card (5700XT) as well. Thanks for the hint about reverting the commit.
Thanks for the ping! I'll dig into this a little this weekend and see if I can understand what's going on, and if I can't figure it out fairly quickly, we can revert that.
I can't reproduce this, so it's going to be tricky to debug by myself. I've got an nvidia card in my machine. However, it's easy to build the runtime directory from before and after that change and diff it, which is what I should have done in that PR (oops). There's a lot of differences that look quite suspicious. In fact, it looks like I messed up and grabbed the wrong upstream runtime tarball entirely. The main difference is that previously, there was , and the new runtime... yeah, it doesn't have a directory at all. I'm surprised it worked at all. If switching to the correct runtime tarball fixes it with no additional work, that would be great. As above, I can't repro these issues locally, so I'll need help to see if that fixes it. A commit switching to what I think is the right artifact is here: After that change, there's far fewer differences between the old working setup and the new runtime folder. The main one that looks like it may be of note is: However, other than those, it's a lot more similar!

To test that commit locally, you can close steam and then run the following: I'm not certain that'll fix it. If it doesn't, I'll make a PR to revert my previous change, and then figure out how to properly use valve's packaged runtime separately. Can one of you check if the above commit does fix the issue you're running into? If not, more detailed information would help me dig into this further, most notably whether there's any debug output if you run the game from a terminal (I think lets you do that?)
I did what you asked and it WORKS!!!
Thanks for testing that, I opened a PR with the change over in .
Can confirm this works with my AMD card as well. Thanks a lot!
Thanks ! This fixes Steam games on my Intel GPU as well!
I also have this bug on my AMD 2400G (so an APU). This only happened in Source games such as CSGO or TF2. fixed this bug.
Although building steam from repo works perfectly. For some reason, steam is still broken for me on nixos-unstable. My looks something like this: Output from :
Just to double check, you're sure there's not some other version in your path (i.e. from or such in the past)? The nix channel commit you're on () should include all relevant changes there, so it seems mostly likely there's either a different version in your path, or something weird going on.
Yeah, sorry. The issue was with . I've somehow completely forgot to check if steam was installed there.
often comes up in issues and confuses people.