petrichornetrainfall

Just to clarify, when mentioning problems with battle.net (in general), the issue you’re talking about is that when you click play for a game, afterwards the button shows “running” then switched back to “play” without anything popping up, correct?

If so, your issues probably aren’t related to anything on your machine except wine (as mentioned by other comments, don’t worry about drivers or vulkan or anything).

There is a known issue that when switching between wine versions, if that exact scenario occurs, you have to blow away the wine prefix.

For some games this is harmless, some save config files or saves for players in the prefix.

Instead of trying to lock drivers or mesa or vulkan to specific versions, instead lock whatever version of wine you have set for battle.net in lutrus to a static version. That includes not using proton-experiemental or proton-ge latest, but instead a set version like proton-ge10.26 (or whatever).

Disclaimer, without doing a bunch of digging, my advice will be limited.

Some questions, are you using X11 or wayland?

Are you launching battle.net through a different method than the games that do work, i.e. are all your steam games running fine but you launch battle.net through lutris or bottles or something?

How long has your install been up and running?

It looks like the vulkan that works is a slightly higher version than the amd and rad ones (the first lines from the files you posted). Vulkan should be getting pulled in by Mesa, i would check to see if you have multiple versions of Mesa installed as well.

Depending on the cutoff year (when amdgpu as a default driver got replaced with RADV) , whether your cpu has a igpu (again, didn’t look up what gen those where), you could have 2 separate AMD drivers being installed, one for your igpu, and one for your dgpu.

Also the ones that are labeled (that don’t work but do output when you run those commands) could be used and pulled in because of X11, where the “unidentifed” is being used by wayland) i could be misreading, but i belive that command around pathing is more for X11 than wayland.

TLDR: the versions should be the first line in the texts you shared. Id figure out what is pulling and installing all 3 of those as deps for you to end up with them on your machine (unlabeled probably mesa, amd and rad probably drivers), and to research id look for some tools to debug and log what happens when you run a program so you can see the paths and LIBS hit.

Looks like you probably already hit this link: https://wiki.archlinux.org/title/Vulkan

Id check out this one too: https://wiki.archlinux.org/title/AMDGPU

So a lot of documentation in general typically only covers beginner or expert levels, with almost no intermediate.

It’s always “here’s how to say hello world” or “here is how to extend our implementation at a low level”.

So it’s nice to have examples of intermediate use cases for power users who need to do more than the most basic examples, but don’t plan on submitting PRs to add or change functionality.

More info, guides, and examples are always better than less (as long as it’s accurate).

I’ll definitely have to take advantage of the hardware acceleration.

In regards to gaming, what kinds of games have you typically used this for? I’m not thinking about using this for competitive shooters or something like that where every ms counts, but what about games like a souls like where timing a parry or something matters, have you tried anything like that?

Lacking those features is perfect fine for me, I’m looking more for a remote display and input implementation anyway.

One last question, have you experimented with any compression or “enhanced” encryption for the ssh connection? If so, has that impacted the responsiveness at all?

You have no idea how grateful I am to you right now.

This has been on my personal project backlog for awhile now. I have run into so many issues and headaches with possible rdp or vnc solutions for my desired use case, especially with wayland being a must have.

I have recently fell in love with ssh and was planning on looking more into waypipe as a possible route to take as I kept seeing it recommended, but the examples and documentation i found was always “generic” or surface level and didn’t have enough of the pieces I needed to scrape together.

I’ve been putting it off due to only having surface level knowledge about all the pieces, and you merged like 10 of them in one go.

My biggest question to you is what is performance like? Like picture quality, audio delay, and latency/responsiveness around mouse and keyboard inputs? How does it compare to using something like an ipkvm, rdp, rust desktop, etc?