yuzu: update, switch to qt6, clean up, etc

[K900]

Description of changes

Testing appreciated. Vulkan updates are in staging-next.

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 23.05 Release Notes (or backporting 22.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

[K900]

staging-next merged, this should be a lot easier to test now.

[sbruder]

Thanks for picking this up!

I just tested it on two machines and it worked quite well.

With OpenGL, everything I tested worked, Vulkan crashed after a short time on Intel Arc (but worked on AMD Vega), though I don’t think that is something we can fix in nixpkgs.

While yuzu should now support Wayland, that requires qtwayland to be used as a build input, otherwise it doesn’t find the platform plugin. However, when I tried compiling it like that, with OpenGL everything had darker colours (like it had a wrong gamma value) and with Vulkan it crashed after a short time, though I’m not sure if it works for other people.
I think we should either force QT_QPA_PLATFORM to xcb again (because without qtwayland, it doesn’t start on Wayland), or build it with qtwayland (and hope that it works for most people).

Also, nice that you could find the git metadata for the early-access branch, so we can reconstruct the source exactly. Because the source in pineapple’s repository is only tested on their build pipeline, we had problems using it in the past.

[K900]

It should pick up qtwayland ambiently if you're running it in a Wayland session, though it might be worth adding to the wrapper as well.

[sbruder]

I am using sway and also tried adding qtwayland to my user packages and system packages, but in both cases, it didn’t find the plugin.

It’s possible that there is something wrong with my configuration, because I had the same problem with Anki. However, other people had the same problem which lead to the inclusion of qtwayland in the build inputs (reasoning, including references to discussions about similar problems).

[K900]

Let's just add it to the wrapper then.

[K900]

Updated to current release while I'm at it.

[K900]

Also, tested a bit more - on 680M (Rembrandt iGPU), 6700S (Navi 23 mobile) and 6800XT (Navi 21 desktop), seems fine for me in both modes, no weird crashing, no weird colors on Gamescope or Plasma.

[sbruder]

Hm, then this must have been an issue on my end. Thanks for testing it.

[K900]

Updated again since a bunch of perf fixes got merged to mainline. We should really set up an auto-updating flake for this...

[athre0z]

Works great here (NixOS, x86_64-linux). Thanks for the update!

[dmayle]

Trying to install here, if I don't manage, I'll test it once it's merged

[dmayle]

Tested as working over here, thanks for this!

[K900]

So, should I do another update and then merge this?

[K900]

Updated to latest versions, supposedly there's some more optimizations.

[baduhai]

Working beautifully for me, the updates brought some great optimisations to the game I want to play 😉.