Hello @BlueGoliath, there are various issue reports to track the specific issues you've mentioned and it's better to discuss those issues separately on the existing issue reports.
Yes, there are Valve developers doing ongoing work to support Steam on Linux.
There is not a single report about CS2's Vulkan performance or the inability to launch legacy CS:GO.
So you have multiple issue trackers and people apparently randomly post to whichever they are aware of, like this:
https://github.com/ValveSoftware/csgo-osx-linux/issues/3552
My bad I guess? Not like it really matters, both issues are over 2 weeks, and few comments from Valve. The VRAM issue has been a problem for months IIRC. I don't know if you can really call that "support".
Can I just refund my prime status like 32-bit Windows and Linux users can? I don't have any confidence that these issues are going to get fixed in any reasonable amount of time.
Nothing extracted yet.
Are you?
Steam's new desktop client still has memory leak problems many months after release.
This GitHub is full of bug reports that never seem to actually get addressed by anyone at Valve except one person in charge of janitorial work.
Now CS2 gets released and it both runs double digit percentage points worse than the Windows DX11 renderer and doesn't have the ability to switch to the legacy CS:GO version like the Windows version can because someone decided to use a shell script instead of the normal Steam app launching mechanism.
Hilariously, A Valve employee left a comment with an absolute path containing their username in said launch script:
/home/plagman/src/valve/Steam/main/client/ubuntu12_32/steam-runtime/pinned_libs_64/libcurl.so.4: versionCURL_OPENSSL_4' not found (required by /usr/lib/libdebuginfod.so.1)`You have people who both use Linux and know Vulkan(what CS2 now uses on Linux, IIRC). Why is Linux's CS2 port so bad?
Why is the support so abysmal? Has Valve decided to put Linux support on life support or what?