EldritchIdiot7

joined 1 year ago
 

Hi. I'm a recent transfer from Reddit, as many are here, and have gotten into exploring Linux on Switch. Honestly, this was actually my first in-depth involvement with Linux, although I have messed with it in the past. Anyway, on to the main topic. After some ups and downs, I was able to get Steam to work via a combo of Pi-Apps (wine64 and box64) and the L4T Megascript (the steam install script by itself had some issues). While some games seem to work ok (The Talos Principle is pretty much playable at this point), it looks like x86 (32bit) games are not cooperating with DXVK; they only work with OpenGL through Steam's WINED3D launch command. Otherwise, they don't even launch, and crash immediately. This wouldn't be too much of a problem, except some 3D games look like they'd perform much better (or be outright playable in cases with unplayable games) with DXVK.

I've tried everything from installing 32bit libraries (spoiler: L4T 18.04 either does not work with them half the time due to dependency/compatibility issues, or cannot find them the other half) to updating sources and installing new software/updating drivers; nothing's worked so far. From what I can tell from the Proton logs, it looks like it has to do with i386/32bit drivers, but I can't be sure how to fix this given the before mentioned issues. I just wanted to check in to see if anyone else either had this issue or had any ideas to remedy this. That being said, anyone have an idea of how to fix this? The bulk of what's causing this seems to be summed up in these two lines from the proton log:

"Error loading needed lib libGLX_nvidia.so.0" "terminate called after throwing an instance of 'dxvk::DxvkError'"

I might as well add that I've looked in the discord, and didn't find any answers there either.

Mind you, x64 games seem to at least launch off the bat. Again, from my own research, it seems like this is related to Steam or DXVK (or both) not being able to find i386 drivers/the drivers just not being there, but I have had no luck fixing this on L4T Swithroot Ubuntu. Any assistance would be appreciated, and I can provide a full log if needed. Thanks. In the meantime, I'm gonna keep searching online to see what I can find.