My CS2 has this error and I don't know what to do, I've tried everything. I was able to play before, I don't know what happened. I've checked drivers and rarely does the game open, most of the time the error occurs.

Hi, just curious about this question. Let's say a gamedev making a Windows game wanted to make sure that their game also works perfectly with Proton/Wine.

Is this something they can "decide" to do, and then implement their code in a particular way, avoiding particular things, etc?

Or is there no alternative other than "write it like a normal windows game and then do a bunch of testing in proton and see what breaks" ?

Whenever I boot my Debian KDE (wayland) system, the sidetone on my headset is set to 0 in alsamixer:

The headset I'm using is a Corsair void pro. The Headset 1 setting controls the volume and the Headset setting is the sidetone.

If I put both cursors at 100 which is the level I want them to be, execute sudo alsactl store, then reboot my system and look at alsamixer again, the headset setting is then set to 0. The weird thing is the headset 1 setting stays at a 100. It's like alsa-restore.service can restore Headset 1 but not Headset for some reason. Also, if I manually time in the command sudo alsactl restore , the Headset setting goes back to 100 exactly as it was saved. A similar issue also happens for my st100 headset stand but it is less big of a deal because the cursors on it seem useless anyway.

It seems like it's only the audio devices that are connected via USB that are having this issue. The ones that are connected via Jack don't seem to be impacted. Maybe the usb devices are loaded after alsa-restore.service ? 🤷‍♂️

Is there somebody here who could help me understand and solve this issue?

Im trying to play with my ps5 controller but when i connect it via bluetooth it turns on for 3 seconds then turns off, what could be going on? Ive already charged it for 20 mins but still doesnt work