Hello,
I have recently jumped of windows in favor of linux and I installed debian trixie as i was already familiar with it. When playing Cyberpunk 2077, i started encountering issues like abysmal fps when enabeling ray tracing (i got arround 60 fps with intel xess on windows) and systematic crashes after some run time on ARC Raiders when enabling any level of global illumination.

I then decided to upgrade to the unstable debian sid release in an effort to grab the latest mesa drivers for my distributiion as it apparently got a decent amount of upgrades and fixes for intel arc gpus.

The upgrade was worth it as it fixed a lighting issue in ARC Raiders (that was present regardless if global illumination was enabled or not).

After the upgrade tho, i still run in to similar issues where cyberpunk fps tank when i enable any level of ray tracing (down to ~5fps with intel xess OR amd fsr) meanwhile the gpu usage is minimal (i know for a fact it's using the GPU because it gets full usage when ray tracing is not enabled)
Same story for ARC Raiders, crashes are still present.

Here's my gpu drivers/software stack (`vulkaninfo --summary`)

========== VULKANINFO ========== Vulkan Instance Version: 1.4.335 Instance Extensions: count = 24 ------------------------------- VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_acquire_xlib_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_headless_surface : extension revision 1 VK_EXT_surface_maintenance1 : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 5 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_portability_enumeration : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 VK_LUNARG_direct_driver_loading : extension revision 1 Instance Layers: count = 9 -------------------------- VK_LAYER_INTEL_nullhw INTEL NULL HW 1.1.73 version 1 VK_LAYER_MESA_anti_lag Open-source implementation of the VK_AMD_anti_lag extension. 1.4.303 version 1 VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1 VK_LAYER_MESA_overlay Mesa Overlay layer 1.4.303 version 1 VK_LAYER_MESA_screenshot Mesa Screenshot layer 1.4.303 version 1 VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1 VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1 Devices: ======== GPU0: apiVersion = 1.4.328 driverVersion = 25.3.3 vendorID = 0x8086 deviceID = 0xe20b deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU deviceName = Intel(R) Arc(tm) B580 Graphics (BMG G21) driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA driverName = Intel open-source Mesa driver driverInfo = Mesa 25.3.3-1 conformanceVersion = 1.4.0.0 deviceUUID = 86800be2-0000-0000-0300-000000000000 driverUUID = de9f6fec-15c8-7eeb-e66b-c2f497b065e4 GPU1: apiVersion = 1.4.328 driverVersion = 25.3.3 vendorID = 0x10005 deviceID = 0x0000 deviceType = PHYSICAL_DEVICE_TYPE_CPU deviceName = llvmpipe (LLVM 21.1.8, 256 bits) driverID = DRIVER_ID_MESA_LLVMPIPE driverName = llvmpipe driverInfo = Mesa 25.3.3-1 (LLVM 21.1.8) conformanceVersion = 1.3.1.1 deviceUUID = 6d657361-3235-2e33-2e33-2d3100000000 driverUUID = 6c6c766d-7069-7065-5555-494400000000

I have tried running multiple versions of wine/proton (proton-GE latest, proton experimental, proton hotfix), the behavior is the same on both games.

If anyone has ran into the same issue (or has any recommendations), I'm kinda desperate (it's ok tho, i can still play without RTX, it's not the worse thing)

If I can't fix it, I'll try changing distros for bleeding edge drivers and keep you guys updated, but it's strange since cyberpunk is getting a little old that I haven't found any reports of the same issue...

submitted by /u/sOmEoNe2lOvE_UWU
[link] [comments]

Pc specs: CPU 7800X3D GPU 9070XT MOBO: ASUS TUF GAMING 650M PLUS WIFI I cannot find the solution. I noticed the installation process looks different than on any YouTube video I checked. Is the process recently updated?

submitted by /u/Careful_Commercial89
[link] [comments]

Hi all!

My setup: CachyOS + KDE Plasma

I've seen the Steam method of remapping controls, but that really isn't what I'm looking for. I REALLY don't want to use Steam.

Basically I'd like to be able to remap my gamepad controls right at the OS level if possible. I'm also open to the option of if Wine itself or Heroic Games Launcher has a way of doing this.

The idea would be, I remap controls for a certain game, then save that file and can use it at a later time. I would have a folder with configs for various games.

I've seen SC-Controller but I can't get that to work for the life of me. I am new to Linux as of a couple months ago so I'm probably doing it wrong.

So again, if I can just locate a file on my drive that contains all gamepad key bindings, that would really be my preferred option anyway. Does anybody know where I can find this?

Thank you for any help at all!

-Andy

*EDIT*

I forgot to mention, just in case. I'm using a PS3 controller. Also the reason why I want to remap controls is for games that have hard-coded control configs. So programs like AntiMicroX won't work unfortunately.

submitted by /u/Paranoid_Andy
[link] [comments]

I've been trying to get SFM to run with proton for a while now and this is the farthest I've got. I found proton 4.11 works but is laggy, doesn't export properly, and has broken AO & lighting, and 7 runs as, if not more, stable but when i try to pull up the model viewer it covers it in a black box that changes how it flickers across different projects.

I am on Debian 12 w/ the 6.1.0-42-amd64 kernel & KDE plasma (with a windows 7 style put on). running a Radeon RX 6900 XT (Mesa 22.3.6) and Ryzen 9 9900X w/ 16gigs ram.

these are the launch commands and proton version I'm using in the video:

• PROTON_NO_D3D11=1 PROTON_NO_D3D10=1 %command% -gamescope -noqt -usevgui -threads 12 -mat_forceaniso 16 -sfm_resolution 1080 -w 1920 -h 1080
• proton 7.0-6

PS: sorry about how i sound in the vid i was a bit sick recording it

submitted by /u/latejacob
[link] [comments]

I am having a weird issue with Team Fortress 2. I just upgraded to a 1440p monitor and the maximum resolution in game is still 1080p. (however it still recognizes my refresh rate being 180)

I tried forcing it in the launch options but that does not work, I know Source 1 games can be disgusting on Linux due to library issues but this doesn't seem like one of those.

I am on wayland, kernel 6.18.4-arch1-1, and drivers nvidia-open 590.48.01-6.

Any help/ideas to diagnose further are appreciated

submitted by /u/NewSeaworthiness1326
[link] [comments]

Hi everyone,

I’m experiencing a critical issue on Ubuntu 24.04 that persists even after a full OS reinstall, and I’m trying to determine whether this is a Linux/NVIDIA configuration issue or something deeper.

System:

- Laptop: Lenovo LOQ 15IAX9E

- OS: Ubuntu 24.04 LTS (fresh install)

- Kernel: 6.14.x

- Desktop: GNOME 46 (Xorg)

- CPU: Intel i7-12650HX

- iGPU: Intel UHD Graphics (Alder Lake)

- dGPU: NVIDIA GeForce RTX 4050 Laptop GPU

- NVIDIA driver: 580.95.05 (proprietary)

- PRIME mode: on-demand (Optimus)

The problem:

When playing Slime Rancher (a relatively lightweight game), the system:

1. Runs normally for a short time

2. Starts heating up very quickly (fans ramp up aggressively)

3. Then suddenly powers off completely (no freeze, no reboot, just instant shutdown)

This looks like a thermal or power cutoff, not a game crash.

Important details:

- This also happened after reinstalling Ubuntu from scratch

- NVIDIA drivers, Vulkan, OpenGL, and 32-bit libraries are installed correctly

- Steam and the game run and launch normally

- The shutdown happens only under GPU/CPU load

- There is no kernel panic message on screen

What I’m trying to understand:

- Is this a known issue with NVIDIA laptops + Linux power/thermal management?

- Could the NVIDIA driver be ignoring platform power limits or fan curves?

- Is this related to ACPI, firmware, or kernel-level power management?

- Has anyone seen similar behavior on Lenovo LOQ / gaming laptops?

If any additional logs, command outputs, or system information would be helpful, please let me know. I’m not entirely sure what else is relevant for this kind of issue, but I’m happy to provide anything that might help diagnose it.

Any insight or direction would be greatly appreciated.

submitted by /u/beautiful_macaroni
[link] [comments]

So i thought I'll use lutris game launcher for everything i play but for some reason mangohud option is greyed out even though it is installed Then I tried out heroic game launcher where the game doesn't even launch Can anyone help me out why it happens or what I should do

Distro- linux mint cinnamon

submitted by /u/Candid_Age6158
[link] [comments]

I was installing cachy OS when this error popped up at the end of the installation how do i make this work

submitted by /u/Happy-Ad-4696
[link] [comments]

I've recently switched from a GTX 660 to an ASUS DUAL RX 580 OC 8GB, which I then immediately dropped Windows for Linux (didn't test windows much), and I've been having issues ever since.

Been looking on past forums, git issues for any fixes but not much progress

System information :

6.18.2-1-cachyos (or 6.12.63-1-cachyos-lts) linux kernels

local/lib32-mesa 1:25.3.3-4
local/lib32-opencl-mesa 1:25.3.3-4
local/lib32-vulkan-mesa-implicit-layers 1:25.3.3-4
local/mesa 1:25.3.3-4
local/mesa-utils 9.0.0-7
local/opencl-mesa 1:25.3.3-4
local/vulkan-mesa-implicit-layers 1:25.3.3-4

i7 3770

ASUS H61M-K (latest BIOS ver.)
12gb DDR3
ASUS RX 580 DUAL OC 8GB
Aerocool 80+ BRONZE 500W KCAS

To keep things stable (and also to make do until I can acquire quality thermal paste), I am using LACT to underclock the RX 580 from 1360Mhz to 1060Mhz max, VRAM at 1750Mhz, power limit to 130W and power profile set to Manual and 3D_FULL_SCREEN (my research said it could help), this setup lets me complete the Unigine Heaven benchmark at 1080p HIGH without crashes or overheating.

here's the journalctl output during one of the crashes (screen freezes, turns purple and green, and then straight purple until hard shutdown), this was while playing a video on chrome, also happened sometimes when running the unigine heaven benchmark:

janv. 11 17:23:28 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: Dumping IP State janv. 11 17:23:28 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: Dumping IP State Completed janv. 11 17:23:28 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: ring gfx timeout, signaled seq=249162, emitted seq=249164 janv. 11 17:23:28 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: Process information: process chrome pid 2331 thread chrome:cs0 pid 2348 janv. 11 17:23:28 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset begin! janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: failed to suspend display audio janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu: cp is busy, skip halt cp janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu: rlc is busy, skip halt rlc janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: BACO reset janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset succeeded, trying to resume janv. 11 17:23:32 cachyos-x8664 kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400300000). janv. 11 17:23:32 cachyos-x8664 kernel: [drm] VRAM is lost due to GPU reset! janv. 11 17:23:32 cachyos-x8664 kernel: [drm] UVD and UVD ENC initialized successfully. janv. 11 17:23:32 cachyos-x8664 kernel: [drm] VCE initialized successfully. janv. 11 17:23:32 cachyos-x8664 helium-browser[2279]: amdgpu: The CS has cancelled because the context is lost. This context is innocent. janv. 11 17:23:32 cachyos-x8664 kernel: amdgpu 0000:01:00.0: amdgpu: GPU reset(1) succeeded! janv. 11 17:23:32 cachyos-x8664 kernel: kfd kfd: amdgpu: skipped device 1002:67df, PCI rejects atomics 730<0 janv. 11 17:23:32 cachyos-x8664 systemd-coredump[10718]: Process 2331 (chrome) of user 1000 terminated abnormally with signal 6/ABRT, processing... janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 systemd[1]: Created slice Slice /system/systemd-coredump. janv. 11 17:23:32 cachyos-x8664 systemd[1]: Started Process Core Dump (PID 10718/UID 0). janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: A graphics reset not attributable to the current GL context occurred. janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: 0x3: GL_CONTEXT_LOST in context lost janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: BlurConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: KscreenConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: OverviewConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: ShakeCursorConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: SlideConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: SlidingPopupsConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: WindowViewConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: ZoomConfig::instance called after the first use - ignoring janv. 11 17:23:32 cachyos-x8664 kwin_wayland[1038]: Could not delete render time query because no context is current janv. 11 17:23:32 cachyos-x8664 plasmashell[1259]: QRhiGles2: Context is lost. janv. 11 17:23:32 cachyos-x8664 plasmashell[1259]: Graphics device lost, cleaning up scenegraph and releasing RHI janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: azx_get_response timeout, switching to polling mode: last cmd=0x00c72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x233:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400 janv. 11 17:23:33 cachyos-x8664 kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xc72400

much of the research I found points to a kernel/mesa regression. I would love to hear your insights/potential fixes/workarounds.

submitted by /u/FluffySpike
[link] [comments]

I just wanted chimera connor in the game. I'm VERY new to modding, never successfully modded ANYTHING before.

Note: The game itself (Detroit Become Human) works just fine. I just cannot for the life of me find out how to replace the default Connor model with the Chimera Connor mod (which I already have downloaded).

Sorry if this is the wrong community to post it to. Just wondering if anyone has modded Detroit on a Steam Deck before and has any tips for a beginner on how to do so?

submitted by /u/Ok_Guess520
[link] [comments]

Hey everyone! Switched from Windows to CachyOS back in September. Been loving it so far, my old laptop feels new again, and plays games better than it ever did with Windows. One annoying issue I've had so far, though, is with the OG Resident Evil games from GOG running under Heroic. I CANNOT get the games to recognize my controller's d-pad. Not matter what I do, or what controller I use, it only uses the analogue stick. Tank controls with analogue sticks are . . . not good. I've tried multiple controllers (Stadia, Retro Fighters Defender, Switch Pro, Xbox Elite Series 2, 8 Bit Do Ultimate 2), and no matter what, it doesn't see the d-pad. I've tried adding them to Steam and using Steam Input, but they stop recognizing the controller entirely when I try that. Any suggestions? I'm pretty new to gaming on Linux, but not by any means new to computers, and I've used Debian distros for not gaming stuff before, so any venturing into the weeds is fine with me. For reference, this is my laptop:
Dell G7 7588

Core i7-8700k

GTX 1060 Max-Q 6GB

16GB DDR4

I'm running two SSDs, one NVMe and one SATA, for a total of 3tb storage.

My primary controller is my Google Stadia connected via Bluetooth.

If any more details are required, please let me know. Thanks in advance for any advice!

Oh, one more thing, I got RE1 to work fine using the rebirth mod. If I need to do that with 2 and 3, that's fine, but I don't know if I need to do anything different.

submitted by /u/cbkummer
[link] [comments]

The steam UI simply blacks out, I can still access and click on things, but it's having trouble displaying. Any advice?

submitted by /u/ash_mnro
[link] [comments]

It shows the IDTech Launcher logo in the task bar but crashes and shows a Bugsplat bug report page. I also tried different Proton version but that didn't change anything. Thank you

submitted by /u/Low_Bottle_7641
[link] [comments]

Hi Linux Gamers,

Can you share your best tips on how to get problem-free wireless connections between Xbox controllers and my (Ubuntu 24) PC?

I am looking to play local co-op with up to four connected controllers.

I can connect via Bluetooth, but the controllers keep losing connection for some reason. Wired connection is fine.

I’m okay with buying hardware/software if it works. I’ve looked at Xbox Wireless Adapters for PC, but most of the posts mentioning these are a couple of years old. If this is still the best way forward, can you recommend a specific product?

Thanks is advance.

submitted by /u/Absjalon
[link] [comments]

Everytime the conversation of gaming on Linux is brought up, Valve is always glazed (and with good reason) for making the steam deck and in consequence making a lot of game devs having to make it compatible for it, and even if not, Valve is very important for the creation and development of Proton which almost completely remove the incompatibility of windows games with Linux

Now my question is: would this still happen without Valve doing these things? Would a equivalent of Proton still be made just by other company or as an open source project. Or would gaming in Linux still remain as a very niche thing? I'm just curious to know what y'all opinion is

submitted by /u/LittleReplacement564
[link] [comments]

submitted by /u/OutsideFace6963
[link] [comments]

Does anyone have a guide to installing mods on a skyrim install on steam? I have never been able to get Wine to work, I tried the Heroic Games Launcher method this morning but couldn't get Vortex to see my Steam Skyrim install. I really don't want to run back to windows for this but I am close.

I used to be able to mod it just fine with the Nexus Mod Manager back in the day. Now Vortex exists and same with the supposedly linux supported App but the app is worse than useless. Vortex is windows only though I had it working via Heroic Games Launcher but there is no way to point it towards my steam install because it's in its emulated windows file structure thing.

I'd kill or die for a simple guide on how to do this. Would I be better off buying skyrim on GOG so I could avoid steam and proton altogether? I wish I knew what the optimal path was as it would make it easier for me to push through to the end. I fear the heroic games launcher path is a dead end with a steam install.

Does anyone have any advice for me?

submitted by /u/PlumpCat19
[link] [comments]

For those asking what kind of games run on Linux here is a list of installed and played on Linux games with my ratings for each. This isn't comprehensive and I haven't populated all the tinker steps or Proton versions but those are easily found on ProtonDB.

Most of the recent games I have tried have run out of the box.

Of all those only Once Human is really bad. The other issues tend to be around sound and this mostly happens during loading screens and not in the game itself.

This does not include any games I run through Lutris from Epic and others.

Also don't judge, at least one of those games I was coerced into playing by my daughter.

Edit: This is my experience and some of these games may have been run on older hardware with a different Linux OS. This post is intended to be an indication of the types of games that run OK on Linux, in my experience.

My current set up.

OS: Nobara Linux 43 (KDE Plasma Desktop Edition) x86_64 Host: MS-7977 (1.0) Kernel: Linux 6.18.3-201.nobara.fc43.x86_64 Uptime: 2 hours, 8 mins Packages: 3658 (rpm), 27 (flatpak-system), 30 (flatpak-user), 10 (snap) Shell: bash 5.3.0 Display (HP E273q): 2560x1440 in 27", 60 Hz [External] * Display (HP E24i G4): 1200x1920 in 24", 60 Hz [External] DE: KDE Plasma 6.5.4 WM: KWin (Wayland) WM Theme: Breeze Theme: Breeze (NordicDarker) [Qt], Breeze [GTK3/4] Icons: Papirus-Dark [Qt], Papirus-Dark [GTK3/4] Font: Source Code Pro (10pt) [Qt], Source Code Pro (10pt) [GTK3/4] Cursor: Nordic (24px) Terminal: konsole 25.12.0 CPU: Intel(R) Core(TM) i7-7700K (8) @ 4.60 GHz GPU: AMD Radeon RX 6900 XT [Discrete] Memory: 6.25 GiB / 15.57 GiB (40%) Swap: 0 B / 25.12 GiB (0%) Disk (/): 209.45 GiB / 912.80 GiB (23%) - btrfs Disk (/home/booga/Storage): 602.66 GiB / 1.82 TiB (32%) - fuseblk Disk (/run/media/booga/744b41bc-6bf7-4822-83bc-fbb7bb803aaa): 1.04 TiB / 1.8s Disk (/run/media/booga/cbe9358a-16b5-400a-9ded-f2356b435880): 1.70 TiB / 3.64

https://preview.redd.it/6ea9g9al1qcg1.png?width=862&format=png&auto=webp&s=46ce7a60f6a34bfa0e0f24ef902ac4f903958977

submitted by /u/Bad-Booga
[link] [comments]

I wanted to share a solution to a frustrating issue I ran into with ESO on Linux, in case anyone else encounters this.

The Problem

I suddenly lost the ability to interact with anything in Elder Scrolls Online. The 'E' prompt wouldn't appear when approaching objects, NPCs, or doors, making the game completely unplayable. This was particularly confusing because everything had been working perfectly just a few days earlier.

My Setup

I'm running CachyOS (Arch-based) with non-flatpak Steam and GE-Proton 10-25. The game had been running flawlessly for months before this issue appeared.

Troubleshooting Journey

When this first happened, I went through the usual suspects. I tested multiple Proton versions including GE-Proton 10-26, the CachyOS native Proton builds, and even Proton Experimental. I disabled all my addons thinking one might have corrupted. I verified the game files through Steam. Nothing worked.

My next thought was that a recent system update had broken something, so I dug through my pacman logs looking for problematic updates around the time the issue started. I found Mesa updates from early January and even attempted downgrading those, thinking perhaps a graphics driver regression was preventing the game from rendering UI elements properly. Still nothing.

I also tried downgrading lib32-libdrm since ESO is a 32-bit game and that library is critical for graphics interaction, but that turned out to be a red herring as well.

The Actual Culprit

The breakthrough came when I remembered something important: I had recently downloaded and activated the Public Test Server. This turned out to be the root cause.

The PTS and Live servers share configuration files within the same Proton prefix. When PTS updated or modified these shared files, it corrupted the settings that the Live server depends on, specifically the UserSettings.txt file and SavedVariables directory.

The Solution

The fix was straightforward once I'd identified the real problem. I navigated to the ESO Live configuration directory and removed the corrupted settings files, allowing the game to regenerate them from scratch:

cd ~/.steam/steam/steamapps/compatdata/306130/pfx/drive_c/users/steamuser/Documents/Elder\ Scrolls\ Online/live/ mv UserSettings.txt UserSettings.txt.backup mv SavedVariables SavedVariables.backup rm -rf ShaderCache.cooked

After launching ESO Live again, the game created fresh configuration files and everything worked perfectly. The interaction prompts returned immediately.

Key Takeaway for PTS Users

If you regularly test on PTS, be aware that it can interfere with your Live installation when they share the same Proton prefix. Before running PTS, consider backing up your UserSettings.txt file. Even better, you might want to keep PTS uninstalled when you're not actively testing, or set up separate Proton prefixes for each version.

Additional Resources

I've created a detailed troubleshooting guide with all the steps I tried and additional nuclear options if the simple fix doesn't work for you. The guide includes instructions for clearing shader caches, rebuilding Proton prefixes, and checking for various system-level conflicts. I'm happy to share it if anyone needs more comprehensive troubleshooting steps.

Hopefully this saves someone else the hours of troubleshooting I went through. The lesson here is that sometimes the most recent change you made isn't a system update, it's something you did within the application itself.

TL;DR: ESO interaction prompts disappeared after installing PTS. PTS corrupted shared config files in the Proton prefix. Fixed by deleting UserSettings.txt and SavedVariables in the live/ directory and letting ESO regenerate them.

Elder Scrolls Online - Lost Interaction Bug Fix - STEP by STEP Problem

• Lost ability to interact with objects in ESO (no 'E' prompt appearing)
• Issue occurred after downloading/activating PTS (Public Test Server)

Root Cause

PTS and Live servers share configuration files in the same Proton prefix. PTS updates can corrupt or override UserSettings.txt and SavedVariables that affect both installations.

Solution That Worked # Navigate to ESO Live config directory cd ~/.steam/steam/steamapps/compatdata/306130/pfx/drive_c/users/steamuser/Documents/Elder\ Scrolls\ Online/live/ # Back up and remove corrupted settings mv UserSettings.txt UserSettings.txt.backup mv SavedVariables SavedVariables.backup # Remove shader cache (optional but recommended) rm -rf ShaderCache.cooked

Launch ESO Live and let it regenerate fresh settings.

Additional Troubleshooting Steps Attempted Check Recent System Updates # View updates from specific date range grep "upgraded\|installed" /var/log/pacman.log | grep -E "2026-01-(08|09|10)" Mesa/Vulkan Driver Issues # Check Mesa version history grep -E "mesa|vulkan-radeon" /var/log/pacman.log | tail -20 # Downgrade Mesa if needed sudo downgrade mesa vulkan-radeon lib32-mesa lib32-vulkan-radeon Graphics Library Issues # Downgrade lib32-libdrm (for 32-bit games) sudo downgrade lib32-libdrm Steam Input Conflicts

• Right-click ESO in Steam → Properties → Controller
• Set "Steam Input Per-Game Setting" to "Forced Off"

Nuclear Options (Last Resort)

Rebuild Proton Prefix:

killall steam mv ~/.steam/steam/steamapps/compatdata/306130 ~/eso_prefix_backup_$(date +%Y%m%d) # Launch ESO - Steam will rebuild prefix

Clear Shader Caches:

rm -rf ~/.local/share/Steam/steamapps/shadercache/306130/ rm -rf ~/.steam/steam/steamapps/compatdata/306130/shadercache/ rm -rf ~/.cache/dxvk-cache/ Prevention

If using PTS regularly:

• Consider separate Proton prefixes for Live and PTS
• Always back up UserSettings.txt before running PTS
• Uninstall PTS when not actively testing: Steam → ESO Properties → DLC → Uncheck "Public Test Server"

Notes

• ESO App ID: 306130
• Config location: compatdata/306130/pfx/drive_c/users/steamuser/Documents/Elder Scrolls Online/
• Issue date: January 2026
• Setup: CachyOS, Non-flatpak Steam, GE-Proton 10-25

DISCLAIMER

Please read this entire disclaimer before attempting any fixes described in this guide.

Use at Your Own Risk

This troubleshooting guide is provided AS-IS with no warranties or guarantees of any kind. The information contained here worked for my specific system configuration but may not work for yours, and could potentially cause issues if applied incorrectly.

Important Warnings

• ALWAYS back up your data before making any system changes or deleting configuration files
• These commands modify system files and game configurations - understand what each command does before running it
• Incorrect use of sudo or rm commands can damage your system or cause data loss
• This guide is intended for experienced Linux users who understand command-line operations

No Liability

By following this guide, you acknowledge that:

• You are solely responsible for any consequences resulting from these actions
• I am not liable for any damage, data loss, broken installations, or other issues that may occur
• You should verify all commands and file paths match your system before executing them
• If uncertain about any step, seek additional help or skip it

System Specificity

This solution worked on:

• CachyOS (Arch-based distribution)
• Non-flatpak Steam
• GE-Proton 10-25
• AMD GPU

Your mileage may vary on different distributions, Steam installations (Flatpak/Snap), Proton versions, or GPU manufacturers.

Community Contribution

This is a community-contributed troubleshooting guide shared in the spirit of helping fellow Linux ESO players. It is not endorsed by ZeniMax Online Studios, Bethesda, or any official entity. For official support, please contact ZeniMax support.

Backup Recommendations

Before attempting ANY fixes, back up:

# Back up entire ESO config directory cp -r ~/.steam/steam/steamapps/compatdata/306130/pfx/drive_c/users/steamuser/Documents/Elder\ Scrolls\ Online/ ~/ESO_backup_$(date +%Y%m%d) # Back up SavedVariables (contains all addon settings) cp -r ~/.steam/steam/steamapps/compatdata/306130/pfx/drive_c/users/steamuser/Documents/Elder\ Scrolls\ Online/live/SavedVariables ~/ESO_SavedVariables_backup_$(date +%Y%m%d) Final Note

If you're uncomfortable with Linux command-line operations, terminal commands, or don't fully understand what these commands do, please do not attempt these fixes. Consider seeking help from someone with Linux experience or contacting official support channels instead.

YOU HAVE BEEN WARNED. PROCEED AT YOUR OWN RISK.

submitted by /u/DutyProfessional67
[link] [comments]

submitted by /u/Sea-Contribution6219
[link] [comments]