xpadneo VS dxvk

In the other distros I've tried (ubuntu / pop os) I usually solve the problem by installing xpadneo using the official method that can be found here. But this doesn't seem to be working in this case. I've already tried using gnome bluetooth settings, blueman and bluetoothctl.

That was more than a year ago though and it seems some people are working on linux drivers. xpadneo is probably a good starting point: https://github.com/atar-axis/xpadneo

If that doesn't work either, I would try making an issue on their github and asking there: https://github.com/atar-axis/xpadneo/issues

2) install https://github.com/atar-axis/xpadneo

This very same controller has worked on this very same physical computer in the past, but under Ubuntu using the xpadneo driver (https://github.com/atar-axis/xpadneo/). One day, for no reason as near as I can tell, it simply stopped working and showed the exact same symptoms as above (controller works for phone, not for PC, doesn't show up in bluetooth list. Other bluetooth devices work fine with the PC). This triggered my distro-hop to Endeavour just to discover the exact same issue.

You can try this custom mapping from xpadneo: https://github.com/atar-axis/xpadneo/blob/master/docs/SDL.md

Someone is trying to game on them, or at least run DirectX apps in Linux, based on this PR: https://github.com/doitsujin/dxvk/pull/3795

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.

Kid named DXVK :

DXVK versions after 2.0 require Vulkan 1.3 support, which may not be available on your GPU. Try using an older build, such as this one.

Give DXVK a try https://github.com/doitsujin/dxvk/releases, use 32bit d3d9.dll

What to download:https://github.com/doitsujin/dxvk/releases/tag/v2.3